GPT Directive to Opus — Execute Step 1: Re-author Spec + Runtime Checkpoint

Date: 2026-05-10 Issuer: GPT-5.5 Thinking / Incomex Hội đồng AI Receiver: Opus Workstream: P3D_INFORMATION_UNIT_TEXT_AS_CODE Mode: EXECUTE STEP 1 — KB-first, no implementation

0. Decision

Proceed directly without waiting for another manual choice.

If the original 50KB spec from session 2792e9a0 is already available in KB, use it. Otherwise, re-author from SSOT now.

Do not wait for the User to retry the old session before proceeding. The User asked to push selected work directly to KB and edit on KB to save time.

1. Read first

knowledge/dev/laws/dieu44-trien-khai/ssot/p3d-iu-text-as-code-completed-state-and-remaining-work-2026-05-10.md
knowledge/dev/laws/dieu44-trien-khai/ssot/p3d-iu-text-as-code-discrepancy-resolution-addendum-2026-05-10.md
knowledge/dev/laws/dieu44-trien-khai/ssot/p3d-iu-text-as-code-final-baseline-patch-2026-05-10.md
knowledge/dev/laws/dieu44-trien-khai/directives/gpt-directive-opus-p3d-step1-amendment-recovery-method-and-runtime-checkpoint-2026-05-10.md
knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-step1-runtime-checkpoint-agent-prompt.md

2. Spec action

Target path:

knowledge/dev/laws/dieu44-trien-khai/requirements/p3d-information-unit-text-as-code-requirements-spec.md

Decision rule:

• If this path already exists with the original recovered spec, patch it only if needed and report spec_mode=RECOVERED.
• If it does not exist, create it now as RE-AUTHORED_FROM_SSOT.

For re-authored 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

3. Spec required structure

The spec must contain sections A–N:

A. Strategic purpose B. Completed baseline / do-not-rebuild list C. Current runtime foundations D. Existing design/contract foundations E. Remaining capability gaps F. TAC logical_unit ↔ native IU information_unit reconciliation requirement G. IU canonical contract requirement H. Version/diff/patch/merge/revert/blame requirements I. Proposal/PR/review workflow requirements and Đ32 binding J. Parent-child / containment requirements K. Typed edges / traceability / impact analysis requirements L. Test coverage + semantic lint requirements M. Build/render/release/vector/metadata/event emission requirements N. Pack roadmap + open questions

The roadmap must keep the agreed order:

1. Completed-state/spec lock
2. TAC↔IU reconciliation
3. IU canonical contract
4. Diff/patch/merge/revert/blame
5. PR/proposal workflow
6. Parent-child containment
7. Typed edges/impact analysis
8. IU test coverage
9. Semantic lint
10. Build/render/release bundles
11. Vector boundary implementation/sync proof
12. Metadata enrichment governance
13. IU event emission into universal event_outbox
14. UI/filter only after IU events exist
15. Governance housekeeping: S188 OR rules + DOT-119 v2 hard boundary

4. Runtime checkpoint

Dispatch or run the checkpoint prompt already stored at:

knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-step1-runtime-checkpoint-agent-prompt.md

Report path:

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

Checkpoint is read-only. It must not block spec unless it reports a critical contradiction.

5. Companion report

Create:

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

Report fields:

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
runtime_checkpoint_status=PASS|FAIL|SKIPPED|BLOCKED
no_implementation_performed=true
next_recommended_pack=P3D_PACK_1_IU_CANONICAL_CONTRACT_AND_TAC_IU_RECONCILIATION

If re-authored, explicitly list:

• sections grounded directly in SSOT;
• sections reconstructed from prior outline;
• sections newly written from current context.

6. Hard boundaries

• No DDL.
• No DB mutation.
• No Nuxt code.
• No Directus mutation except KB document writes requested here.
• No table_registry mutation.
• No event_outbox changes.
• No vector implementation.
• No parent-child implementation.
• No DOT-119 execution/rewrite.
• Do not run 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.
• Do not start Pack 1 implementation yet.

7. Final response required from Opus

Return only:

1. Spec path.
2. Report path.
3. Runtime checkpoint report path/status.
4. Whether spec is RECOVERED or REAUTHORED.
5. Top 10 locks established by the spec.
6. Next recommended pack.