GPT Review — File 13 rev2 Description Policy Agent Prompt
GPT Review — File 13 rev2 Description Policy Agent Prompt
Date: 2026-05-04 Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI Reviewed:
knowledge/dev/laws/dieu44-trien-khai/design/13-iu0-description-policy-tiering-and-pack2b-f6-preflight.mdrev 2
Verdict
PASS DIRECTION. Agent prompt is almost ready, but patch small runtime-safety guards before dispatch.
Opus applied the 8 GPT patches correctly:
- Q7 SQL precedence fixed.
- Q6 now uses
pg_get_functiondef. - Q9 checks H11 runtime registration.
- Q10/Q11 check Directus/schema and JSONB/species.
- Q3 checks schema before data.
- Tier B wording clarifies structured metadata is still mandatory.
- Options are neutral instead of pre-selecting DDL.
- Agent read-list added.
No scope violation: no Pack 2B, no DDL, no runtime write, no law patch.
Remaining small issues
These are not conceptual blockers, but they can cause the Agent prompt to fail unnecessarily if runtime columns differ.
P1 — Schema-first guard for Q3/Q9/Q10/Q11
Some queries still assume columns exist after schema inspection:
- Q3 assumes
taxonomy_facets(code, name)exist. - Q9 assumes
system_health_checks(code, name, executor_type, executor_ref, threshold_config, severity_on_fail, is_active)exist. - Q10 assumes
directus_fields(field, type, meta, sort)exist. - Q11 assumes
collection_registry.extra_metadataexists.
Agent should be told:
If a referenced column/table does not exist, do not treat as failure. Record “column/table absent” and adapt with schema output. Do not write or repair.
For Q11, only run the extra_metadata value query if Q8 confirms the column exists.
P2 — Read-list should include exact law paths
Add exact paths for Đ3/Đ4/Đ43 rather than “relevant sections if needed”:
knowledge/dev/laws/law-03-metadata.mdknowledge/dev/laws/law-04-birth-process.mdknowledge/dev/laws/dieu43-system-context-law.md
P3 — Report path missing
The Agent prompt should specify an upload target, e.g.:
knowledge/dev/laws/dieu44-trien-khai/reports/iu0-description-policy-tiering-runtime-investigation-report.md
P4 — Hard stop after report
Add:
After uploading report: HARD STOP. Do not propose or execute a patch.
Directive
Ask Opus to patch file 13 to rev3 with only the above prompt-safety fixes, then prepare the final read-only Agent dispatch prompt. No need to alter the core Tier A/B/C design.
Do not dispatch Agent until GPT/User reviews the exact rev3 prompt.
No Pack 2B, no DDL, no law patch, no runtime write.