GPT Review — Pack 21 rev3 Final Check

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

• knowledge/dev/laws/dieu44-trien-khai/design/21-birth-runtime-truth-doc-fix-pack.md rev3
• knowledge/dev/laws/dieu44-trien-khai/prompts/21-birth-runtime-truth-doc-fix-execution-prompt.md rev2

Verdict

Direction PASS. Small rev3.1 prompt hardening required before dispatch.

The anti-hardcode philosophy is now correct: docs must contain source-of-truth query/path + dated snapshot evidence + re-verify instruction, not naked runtime constants.

No constitutional conflict found with doc-only execution.

Constitutional / principles check

• §0-AU anti-hardcode: PASS — runtime counts are now snapshot evidence, not timeless truth.
• NT13 / PG-first: PASS — dynamic runtime facts point to PostgreSQL catalog queries.
• No runtime mutation: PASS — doc-only scope.
• No redesign: PASS — Pack 21 only corrects stale docs, does not redesign birth process.
• Historical integrity: Mostly PASS — S145 is append-only. Add idempotency guard.
• Zero trust: Needs a small guard — target docs may already be patched or absent; prompt should SKIP cleanly.

Required small patches before dispatch

P1 — Add idempotency guard for historical append

For E3 S145 report, before append:

• search for marker Historical context note (Pack 21, 2026-05-05);
• if marker exists → SKIP, do not append duplicate note.

P2 — Do not delete/replace useful schema lists blindly

Execution prompt says “Thay bằng query”. Better wording:

• preserve existing useful schema details if they are not false;
• add a runtime-truth note that PG catalog is source of truth;
• only remove/replace explicit stale hardcoded field counts if present.

This avoids damaging doc readability.

P3 — Make dot_tools query schema-tolerant in doc wording

Pack 21 uses:

SELECT code, tool_name, status FROM dot_tools

But previous reports often use name, not tool_name. Since this is a doc snippet, use schema-tolerant wording:

SELECT column_name
FROM information_schema.columns
WHERE table_name='dot_tools'
ORDER BY ordinal_position;

SELECT code, name, status, operation, file_path
FROM dot_tools
WHERE code ILIKE '%BIRTH%'
   OR name ILIKE '%birth%'
   OR operation ILIKE '%birth%'
   OR file_path ILIKE '%birth%'
ORDER BY code;

If operation/file_path are absent in a future schema, re-check columns first. This keeps the doc from embedding a failing query.

P4 — Add “missing target doc = SKIP, not fail”

CAT-023 or current-state report IDs may vary. Execution prompt should explicitly say:

• if target doc not found, search exact title/path once;
• if still not found → SKIP with reason;
• do not invent a new doc path.

P5 — Add report self-check for anti-hardcode

Report should include a short section:

## Anti-hardcode check
- Naked dynamic runtime constants introduced? yes/no
- Each dynamic count has query/path? yes/no
- Each snapshot has date/evidence? yes/no

Directive to Opus

Patch the execution prompt to rev3.1 with P1–P5. The design pack can remain rev3 unless Opus wants to sync P3 query wording there too.

After this patch, prompt is dispatchable.

Dispatch after patch

Send:

Đọc prompt từ KB rồi thực hiện:
knowledge/dev/laws/dieu44-trien-khai/prompts/21-birth-runtime-truth-doc-fix-execution-prompt.md

Mục tiêu: Sửa KB docs stale về birth pipeline bằng query-path language. Chỉ patch docs, không runtime mutation. HARD STOP sau report.

Hard boundaries remain

• no PG/runtime mutation;
• no DOT script patch;
• no system_issues mutation;
• no rewriting historical report content except append note;
• no over-patching enacted laws;
• no hardcoded numbers as timeless truth;
• no Pack 2C dispatch.