GPT Audit — Completed State vs Opus Feedback

Date: 2026-05-10 Author: GPT-5.5 Thinking / Incomex Hội đồng AI Purpose: Audit Opus feedback against KB evidence to avoid rebuilding already completed work.

Verdict

Opus feedback is materially correct: GPT's earlier completed-state list was incomplete. It covered TAC cut/render + recent event_outbox display, but missed IU production machinery, IU design foundation, graph/registry/governance foundations, and pending landmines.

Confirmed completed / present

TAC pipeline

• Text was cut into units / information pieces.
• PG contains 3 publications / 86 units.
• Round-trip 0 drift achieved.
• Directus collections exposed.
• Nuxt /knowledge/laws shows 3 publications.
• TAC model exists: tac_publication, tac_logical_unit, tac_unit_version, tac_publication_member.
• Render order / publication assembly exists.
• Đ38/P7A segmentation reference exists.

Nuxt / laws reader

• P10D parallel TAC laws screen exists.
• /knowledge/laws and reader page assemble/render publication.

event_outbox display

• D28 generated-map / Nuxt blocker resolved enough.
• /knowledge/registries/event_outbox route public-visible.
• Unsafe field probes pass/403 for denied fields.
• Label changed from “Phân loại payload” to “Phân loại dữ liệu”.
• Filter UI config PASS.
• “Thông tin” filter deferred because no event_domain='information_unit' events exist yet.

IU production machinery

• Pack 22 COMPLETE: fn_iu_create canonical writer + IU Creation Gateway enforcement.
• fn_iu_verify_invariants and helper functions exist per Pack 22 closure.
• Direct INSERT/UPDATE to information_unit / unit_version is blocked by gateway marker policy.
• IU Creation Gateway README says canonical path is fn_iu_create_plan then fn_iu_create.
• Pack 23 design/inspection/edit workflow anchors exist: P1 design, P2 inspection, P3C2/P3C4 prompts/reviews. Some are design/prompt/approved-for-dispatch, not all implemented.

IU notification machinery

• P3D1 PASS: IU notification schema/functions.
• P3D2 PASS: notification triggers + board, read-state semantics; runtime active for limited use.
• Later universal event/outbox work supersedes/pauses narrow IU-only notification expansion for broader architecture.

Foundations

• P38-XC / IU-0 minimum standard exists with UMC 10 elements as design/contract.
• Đ38 P5 schema draft v0.2 exists as design notation, not production DDL.
• universal_edges exists in meta_catalog CAT-130 with 2199 rows.
• collection_registry/description_policy foundations exist; exact count varies by report/time, must verify live before relying on a fixed count.
• DOT-119 repair arc exists; must avoid old v1 clobber risk and preserve v2/no-clobber behavior.

Confirmed missing / not uploaded

• knowledge/dev/laws/dieu44-trien-khai/requirements/p3d-information-unit-text-as-code-requirements-spec.md is currently NOT_FOUND in Agent Data. Opus claim that spec was drafted but not uploaded is consistent with missing KB path, but GPT cannot verify the 50KB content unless Opus/session provides it.
• Companion report path is not confirmed present.

Classification warning

Do not treat every Opus item as implemented runtime. Some are:

• implemented/runtime: Pack 22, P3D1/P3D2, TAC 3 publications/86 units/render proof, event_outbox display.
• design/contract: UMC 10, P38-XC, P5 v0.2, P44 design docs.
• prompt/approved/pending: parts of Pack 23 edit/apply path and Opus first-pass spec.
• landmine/pending: DOT-119 old script/no-clobber preservation.

Next required before work resumes

1. Build a definitive completed-state matrix with columns: item, status, evidence path, implemented/design/prompt/pending, do-not-rebuild note.
2. Recover/upload Opus first-pass 50KB spec if available, rather than rewriting from zero.
3. Only after state matrix + roadmap are accepted, dispatch next implementation/design pack.