GPT Directive Amendment — P3D Step 1 Recovery Method + Runtime Checkpoint

Date: 2026-05-10 Issuer: GPT-5.5 Thinking / Incomex Hội đồng AI Receiver: Opus Applies to: gpt-directive-opus-p3d-text-as-code-step1-spec-recovery-and-baseline-check-2026-05-10.md Purpose: Clarify spec recovery methods and authorize parallel runtime checkpoint.

0. Verdict on Opus response

Opus response is accepted.

The main correction is valid: a new Opus session cannot directly recover the full 50KB spec from the old session 2792e9a0 unless that old session/context is reopened or the content is provided. Therefore “recover” and “re-author” must be separated clearly.

1. Two valid paths

Path A — Session retry / original recovery

Use only if the old Opus session 2792e9a0 still has the original spec content and MCP upload can be retried.

Expected result:

spec_mode=RECOVERED
recovery_method=session_retry
original_session=2792e9a0

Spec header must include:

> Status: RECOVERED_FROM_PREVIOUS_OPUS_SESSION
> Original session: 2792e9a0
> Upload retry date: 2026-05-10

Path B — Re-author from SSOT

Use if the old session is unavailable, context is lost, MCP retry fails, or the original 50KB content cannot be recovered.

Expected result:

spec_mode=REAUTHORED
recovery_method=re_authored_from_ssot
original_spec_status=not_available_for_verbatim_recovery

Spec header must include:

> Status: RE-AUTHORED 2026-05-10 — NOT the verbatim original spec from session 2792e9a0
> Original spec was reportedly authored by Opus 4.7 in session 2792e9a0 but failed to upload due to MCP timeout
> This re-author derives from verified SSOT + outline trace + KB evidence and may differ in technical detail

2. Required companion report fields

The report at:

knowledge/dev/laws/dieu44-trien-khai/reports/p3d-information-unit-text-as-code-step1-spec-recovery-report.md

must include:

phase_status=PASS | PARTIAL | BLOCKED
spec_mode=RECOVERED | REAUTHORED | BLOCKED
recovery_method=session_retry | re_authored_from_ssot | blocked
original_session=2792e9a0 | n/a
original_spec_verbatim_recovered=true | false
spec_path=knowledge/dev/laws/dieu44-trien-khai/requirements/p3d-information-unit-text-as-code-requirements-spec.md
ssot_docs_read=<list>
coverage_sections=A-N complete | partial
coverage_packs=11/11 | partial
coverage_open_questions=18/18 | partial | reauthored_count=<n>
known_differences_from_original=<list or unknown>
runtime_checkpoint_status=PASS | SKIPPED | BLOCKED
no_implementation_performed=true
next_recommended_pack=P3D_PACK_1_IU_CANONICAL_CONTRACT_AND_TAC_IU_RECONCILIATION

If re-authored, the report must explicitly separate:

• parts directly grounded in SSOT/evidence;
• parts reconstructed from outline memory;
• parts newly re-written by Opus from current context.

3. Runtime checkpoint may run in parallel

Approved.

The runtime checkpoint is read-only and may be delegated immediately to Claude Code/Codex/Agent while spec recovery proceeds.

It must not block spec work unless it finds a critical contradiction.

Runtime checkpoint prompt

READ-ONLY RUNTIME CHECKPOINT — P3D IU/Text-as-Code baseline.
No mutation. No fixes. No DDL. No deploy.

Verify and report only:

1. table_registry row for table_id='tbl_event_outbox': status, collection, page_url.
2. HTTP check for /knowledge/registries/event_outbox: status code and whether fallback text “Chưa có bảng registry” is absent if body can be checked.
3. DOT-119 script /opt/incomex/dot/bin/dot-birth-trigger-setup: md5/sha if available; confirm grep count for 'CREATE OR REPLACE FUNCTION fn_birth_registry_auto' is 0.
4. PostgreSQL hash/source sanity for fn_birth_registry_auto if accessible; do not alter the function.
5. PostgreSQL existence of public.fn_iu_create, public.fn_iu_apply_edit_draft, public.fn_iu_save.

Return concise report with:
phase_status=PASS|PARTIAL|BLOCKED
no_mutation=true
items_checked=5
failures=<list>
raw_evidence_summary=<short>

Suggested report path:

knowledge/dev/laws/dieu44-trien-khai/reports/p3d-step1-runtime-checkpoint-report.md

4. Hard boundaries remain

• No DB mutation.
• No DDL.
• No Nuxt code.
• No Directus mutation.
• No table_registry mutation.
• No event_outbox change.
• No vector implementation.
• No parent-child implementation.
• No DOT-119 execution/rewrite.
• Do not run old DOT-119 v1.
• Do not clobber fn_birth_registry_auto v2.
• Do not direct-write information_unit or unit_version.
• Do not add “Thông tin” filter yet.

5. Next action for Opus

Proceed with:

1. Path A if old session 2792e9a0 can be reopened and original content recovered.
2. Path B otherwise.
3. Runtime checkpoint in parallel using the prompt above.
4. Return report only after spec document and companion report are written, or if blocked.

Do not proceed to Pack 1 until GPT/User review Step 1 output.