dot-iu-cutter v0.5 — Constitution source_document Seed Authoring Report

Phase: v0_5_constitution_source_document_seed_authoring · Date: 2026-05-18 · doc 5 of 5

package_status: AUTHORED ; ready_for_GPT_command_review: NO
blocker: B6 (Nuxt parser / normalized content_checksum determinism) = BLOCKED
dml_executed: 0 ; rows_inserted: 0 ; dry_run: none ; cut: none ; verify: none
decision_authority: GPT / User ONLY ; self_advance: PROHIBITED

---

1. Executive summary

The Constitution source_document seed was authored operations-first. Source identity is fully grounded and the source_document_registry row is schema-accurate and determinable now. However, the source_document_version_registry row cannot be safely authored as executable DML: its NOT NULL content_checksum identity depends on a normalization/parser ruleset (OD-SR2) that is not ratified, against a Nuxt SPA/SSR living-document source. Per QG5, doc 3 is a NO-DML-DRAFT, not unsafe DML. The package is NOT ready for command-review; it converts B6 into a precise, ratifiable specification and prepares mechanical execution once unblocked.

---

2. What was read (KB, read-only)

read:
  - handoffs/dot-iu-cutter-current-operating-objectives-and-principles-2026-05-18
  - reviews/...constitution-status-marker-amendment-production-closeout-gpt-review-2026-05-18
  - reviews/...constitution-fixture-ratification-gpt-ruling-2026-05-18 (R1..R5)
  - reviews/...WS-Q5-seed-privilege-production-closeout-gpt-review-2026-05-18
  - v0.5-constitution-fixture-source-grammar-ratification/ (grounding-report,
    source-document-version-plan)
  - v0.5-constitution-status-marker-amendment-production-execution/ (verification-result)
  - v0.5-ws-q5-registry-substrate-production-apply/ (reauthorized-verification-result)
  - v0.5-ws-q5-seed-privilege-production-execution/ (execution-log, verification-result)
  - v0.5-fabric-addendum-scope/ WS-2 source-family-grammar-authority +
    entity-registry-and-address-namespacing designs
kb_state: consistent ; no path missing ; no conflict with latest GPT rulings
production_state_vs_stated_live_facts: consistent
  (source_document=0, version=0, family=3, markers=4, sysid 7611578671664259111)

3. What was grounded

source_url: https://vps.incomexsaigoncorp.vn/knowledge/dev/laws/constitution
method: one read-only HTTP GET this session (200) + prior-session header GET (KB)
identity: internal Incomex Architecture Constitution v4.6.3 BAN HÀNH — CONFIRMED
markers_observed: ✅ 📋 📝 ⛔  (matches LIVE 4-marker map; B1 closed)
dieu_44: 📋 controlled_draft (GPT R3 deferred from first dry-run) — consistent
discrepancy_flagged: this-session fetch inferred "server-rendered"; prior-session
  HTTP headers show x-powered-by: Nuxt -> resolved on header evidence = Nuxt SPA/SSR
  (strengthens B6 blocker). Not silently resolved.

4. What was authored (and what was not)

authored:
  doc1 operational-framing: operations-first, "Cắt Hiến pháp" enablement, 6 STOP conditions
  doc2 grounding+checksum-plan: identity confirmed; deterministic capture strategy +
       proposed parser_profile "nuxt-incomex-portal-constitution-v1"; B6=BLOCKED
  doc3 seed-DML: NO-DML-DRAFT (QG5). source_document_registry row fully specified &
       schema-accurate; version row blocked on content_checksum (no INSERT rendered)
  doc4 rollback+verification: clean DELETE path A + compensation path B;
       pre/post/negative/checksum verification, catalog/codepoint method
  doc5 this report
NOT authored:
  - executable INSERT for source_document_version_registry (B6 BLOCKED, QG5)
  - any runnable .sql artifact
  - any other document's seed (QG6 — Constitution only)
NOT touched: grammar_profile / status_marker / source_family / address_template
  (read-only referenced); schema; grants; Directus; vector

5. B5 / B6 status

B1_marker_coverage: CLOSED (LIVE, 4 markers codepoint-exact)
B5_source_document_version_seed: OPEN
  - source_document row: specified & determinable (not executed — gated with version, QG6)
  - source_document_version row: cannot be authored as DML until B6 resolved
B6_Nuxt_parser_checksum_determinism: BLOCKED
  - design progress PARTIAL: capture strategy + parser_profile proposal authored
  - unresolved: OD-SR2 (extract_authoritative_span / Nuxt strip ruleset) NOT ratified;
    no controlled raw GET captured under a ratified profile

6. Ready / not ready for GPT command-review

ready_for_GPT_command_review: NO
exact_blocker: content_checksum (NOT NULL, identity) is not deterministically
  computable -> OD-SR2 unratified + Nuxt SPA/SSR + living-document drift.
  Authoring/executing seed DML now would require inventing a checksum (QG5 / governance breach).
what_IS_ready: source_document_registry row fully specified; rollback +
  verification plans complete; B6 reduced to a single ratifiable decision (OD-SR2).

7. Open decisions (for GPT / User)

OD-SR2 (PRIMARY, blocks B6/B5):
  ratify extract_authoritative_span + Nuxt chrome-strip ruleset + normalize profile
  for source_family internal_incomex_constitution
  -> proposed: parser_profile_ref "nuxt-incomex-portal-constitution-v1" (doc2 §3)
PP-1: accept parser_profile recorded in provenance jsonb (no live parser_profile
  table) vs require a parser_profile registry first?
RB-B: approve compensation path B (lifecycle deprecate / version_status void) for
  the case downstream refs exist at rollback time? (doc4 §1)
SEP-1: confirm address scheme separator slash-vs-hyphen (carried over OD-A1 /
  WS-2 D6 flag) — ICX-CONST uses '/' per locked BR-A1; reconfirm OK.
REG-1: confirm registered_by principal "constitution-source-seed" (distinct from
  'ws-q5-seed-bootstrap') acceptable.

8. Next recommended step

recommended_next: parser/checksum design fix (NOT command-review)
  phase: v0_5_constitution_parser_profile_ratification (design/decision)
  purpose: GPT/User rule on OD-SR2 + PP-1 -> ratify the Nuxt normalization profile
  then: a single controlled raw GET computes content_checksum -> fill the
        NO-DML-DRAFT placeholders -> THEN open command-review for the source seed
do_not: open command-review or execution for the source seed while B6 BLOCKED

9. Explicit no-execution + access statement

no_DML_executed: true ; no source_document INSERT: true ;
no source_document_version INSERT: true ; no UPDATE/DELETE: true ;
no Constitution dry-run: true ; no CUT: true ; no VERIFY: true ;
no schema change: true ; no GRANT/REVOKE: true ; no index DDL: true ;
no Directus mutation: true ; no vector/NoSQL: true ; no deploy/restart: true ;
no git commit: true ; self_advance: PROHIBITED
git_repo_access: none — primary working dir is not a git repository; no VPS/repo
  shell this session. KB is SSOT, accessed via Agent Data (read + 5 uploads only).
  Production facts taken from KB read-only + one read-only HTTP GET; no catalog
  SELECT executed this session (live schema relied upon from 2026-05-18
  read-only-confirmed KB records: source-document-version-plan + WS-Q5
  reauthorized catalog verification).
files_uploaded: 5 (this package) -> STOP -> route GPT/User

10. Statement

• Operations-first (QG1); source grounded read-only (QG2); DML adapted to LIVE schema only (QG3); Nuxt/parser/checksum determinism addressed (QG4); B6 BLOCKED → NO-DML-DRAFT not unsafe DML (QG5); seed scoped Constitution-only (QG6); rollback+verification complete (QG7); nothing executed (QG8); 5 files then STOP (QG9).
• doc 5 of 5; package complete; STOP → route GPT/User. Self-advance PROHIBITED.

Companion: operational-framing, grounding-and-checksum-plan, seed-DML-draft (NO-DML-DRAFT), rollback-and-verification-plan.