KB-7E23

SSOT Addendum — Discrepancy Resolution: GPT vs Opus

6 min read Revision 1
ssotdiscrepancy-resolutionopusgptp3dinformation-unittext-as-code2026-05-10

SSOT Addendum — Discrepancy Resolution: GPT vs Opus

Date: 2026-05-10 Author: GPT-5.5 Thinking / Incomex Hội đồng AI Purpose: Resolve discrepancies between GPT SSOT and Opus verification notes before continuing P3D IU/Text-as-Code.

1. Discrepancies checked

1.1 event_outbox published/live/PASS

Verdict: GPT position confirmed by Agent Data.

Evidence:

  • registries/table_registry/tbl_event_outbox shows Status: published, page URL /knowledge/registries/event_outbox.
  • knowledge/dev/laws/dieu44-trien-khai/reports/p3d4c2u-resume-notification-display-report.md shows route /knowledge/registries/event_outbox, route_http_status=200, smoke_scan=PASS, unsafe field probes denied.
  • knowledge/dev/laws/dieu44-trien-khai/reports/p3d4c2w-event-outbox-label-clarify-report.md shows status_before: published, status_after: published.
  • knowledge/dev/laws/dieu44-trien-khai/reports/p3d4c2x-event-outbox-filter-ui-config-patch-report.md shows filter UI config patch PASS.

Conclusion: tbl_event_outbox is not pending draft. The route is live. P3D4C2U/P3D4C2W/P3D4C2X are completed enough for current monitoring.

1.2 Pack 23 P3C2/P3C3/P3C4

Verdict: GPT position confirmed.

Evidence:

  • knowledge/dev/laws/dieu44-trien-khai/reports/23-p3c2-iu-apply-edit-functions-report.md shows P3C2 PASS and deployed fn_iu_apply_edit_draft + fn_iu_edit.
  • knowledge/dev/laws/dieu44-trien-khai/reports/23-p3c3-iu-natural-save-router-report.md shows P3C3 PASS and deployed fn_iu_save.
  • knowledge/dev/laws/dieu44-trien-khai/reports/23-p3c4-iu-policy-and-agent-context-report.md shows P3C4 PASS and policy switched auto_applyrequire_review.

Conclusion: P3C2/P3C3/P3C4 are runtime completed, not prompt-pending.

1.3 P3B-FU invariant generalization

Verdict: Opus addition accepted.

Evidence:

  • knowledge/dev/laws/dieu44-trien-khai/reports/23-p3c2-iu-apply-edit-functions-report.md states predecessor 24-P3B-FU PASS (invariant generalized for current-anchor).
  • knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-final-approval-24-p3bfu-invariant-prompt-rev3-2026-05-07.md confirms pack purpose and dispatch approval.

Conclusion: Add P3B-FU to completed runtime chain as predecessor/unblocker of P3C2.

1.4 Đ43 System Context Law

Verdict: Opus addition accepted.

Evidence:

  • knowledge/dev/laws/dieu43-system-context-law.md is v1.2 FINAL BAN HÀNH.
  • knowledge/dev/laws/dieu43-migrations/03-dieu43-v1-2-extensions.sql includes section definitions, health checks, and 7 dot_config keys.

Conclusion: Add Đ43 as enacted/context foundation for agent context and graph/context operations.

1.5 Generated table-map commits

Verdict: Opus addition accepted with status wording: D28 generated-map chain PASS/resolved enough.

Evidence:

  • knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-d28-phase1b-partial-success-and-next-pack-directive-2026-05-10.md records generated_map_commits 0947613,d2db418 during partial phase.
  • Later p3d4c2u and p3d4c2x reports show route/display/filter success.

Conclusion: Include generated table-map as completed infrastructure foundation, not merely UI polish.

1.6 Đ44 Universal Method Law

Verdict: Opus addition accepted, but cite current law doc before making detailed claims. P3D workstream is under dieu44-trien-khai and must remain Đ44-governed.

1.7 DOT-119 v1 landmine

Verdict: Opus warning accepted.

Evidence:

  • DOT-119 repair reports and no-clobber redesign arc exist.
  • GPT SSOT already warned not to run old DOT-119 v1 scripts and not to drop/replace fn_birth_registry_auto v2 without reviewed pack.

Conclusion: Keep as hard boundary in every relevant future prompt.

1.8 9 OR rules from S188

Verdict: Opus addition accepted as pending/governance gap, but exact wording must be verified before official OR amendment.

Conclusion: Add to pending/governance section; do not silently treat them as enacted OR.

2. Corrected start point

The accurate start point is not zero. Completed foundations include:

  1. TAC unitization/render proof: 3 publications / 86 units / 0 drift.
  2. TAC tables and render_order/publication assembly.
  3. Nuxt /knowledge/laws reader/listing.
  4. Pack 22 IU canonical create/gateway machinery.
  5. Pack 23 edit/save/policy runtime through P3C4, including P3B-FU.
  6. P3D1/P3D2 IU notification runtime.
  7. Universal event_outbox display published/live/filter PASS.
  8. P38-XC/IU-0/UMC and Đ38 P5 design foundations.
  9. universal_edges/context graph foundation.
  10. Đ43 enacted context foundation.
  11. D28 generated-map infrastructure foundation.

3. Remaining work remains broadly unchanged

Remaining work must not rebuild the above. It should focus on:

  • recover/upload P3D 50KB spec or re-author from this SSOT;
  • reconcile TAC logical_unit with IU native information_unit;
  • final IU canonical contract;
  • diff/patch/merge/revert/blame;
  • PR/proposal workflow;
  • parent-child containment;
  • typed edges/impact analysis;
  • IU test coverage;
  • semantic lint;
  • build/render/release bundles;
  • vector boundary implementation/sync proof;
  • metadata enrichment governance;
  • IU event emission into universal event_outbox with event_domain='information_unit';
  • UI only after contracts/data/events exist.

4. Decision

Use this addendum plus the SSOT document as the agreed state. Do not continue implementation until User/GPT accept this corrected baseline.

Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/ssot/p3d-iu-text-as-code-discrepancy-resolution-addendum-2026-05-10.md