GPT Review — Opus Step 1 Checkpoint Prompt + Next Directive

Date: 2026-05-10 Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI

Verdict

Opus direction is accepted, with prompt hardening applied directly in KB.

What GPT changed

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

2. Created execution directive for Opus: knowledge/dev/laws/dieu44-trien-khai/directives/gpt-directive-opus-step1-execute-reauthor-and-checkpoint-2026-05-10.md

Prompt fixes applied

• Query table_registry by table_id='tbl_event_outbox', not brittle id=21 only.
• Route check tries localhost and public URL fallback.
• Fallback text check included.
• DOT-119 check uses clobber-pattern count, not only md5.
• fn_birth_registry_auto hash mismatch is warning unless clobber/source issue is present.
• IU function existence check uses SQL count, avoiding wc false positive on empty string.
• C6 policy check is warning-level unless other checks fail.

Ops dispatch attempt

GPT attempted to dispatch the runtime checkpoint as an ai_tasks item for claude_code, but Directus/ops API rejected creation because max_retries is required while the caller lacks permission to set it. Therefore no ops queue item was created.

Next directive

Opus should proceed from the KB directive and checkpoint prompt directly:

• Run or ask available agent to run the runtime checkpoint from the prompt path.
• Re-author the spec from SSOT if no recovered original spec exists at the target requirements path.
• Write companion report.
• Do not implement Pack 1 yet.

Required outputs

• Requirements spec: knowledge/dev/laws/dieu44-trien-khai/requirements/p3d-information-unit-text-as-code-requirements-spec.md
• Spec recovery report: knowledge/dev/laws/dieu44-trien-khai/reports/p3d-information-unit-text-as-code-step1-spec-recovery-report.md
• Runtime checkpoint report: knowledge/dev/laws/dieu44-trien-khai/reports/p3d-step1-runtime-checkpoint-report.md