dot-iu-cutter v0.5 — Constitution Source Snapshot Capture Authoring Report

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

package_status: AUTHORED ; ready_for_GPT_command_review: YES
nature: authoring_only__no_execution
capture_executed: false ; snapshot_written: false ; dml/seed: 0 ;
checksum_persisted_or_updated: NONE ; mutation: none (KB authoring of 5 docs only)
B5_source_document_version_seed: OPEN/BLOCKED (unblock path now fully authored)
decision_authority: GPT / User ONLY ; self_advance: PROHIBITED

1. Executive summary

Per GPT ruling …source-snapshot-version-policy-gpt-ruling-2026-05-18 (PASS_WITH_RULINGS; Q1 APPROVE Option B), this phase authors the snapshot capture procedure, checksum-addressed write-once artifact spec, rehash gates, and the snapshot-bound source seed strategy + verification + rollback. Nothing was captured, written, seeded, or mutated. The package is READY for GPT command-review.

2. What was authored (5 docs)

doc1 operational-framing: race-free mechanism; S1→S5 operator state machine;
     stop conditions SC1..SC6; automatic vs stop-for-review
doc2 artifact-spec: path knowledge/dev/laws/dieu44-trien-khai/snapshots/
     constitution/constitution-normalized-<first16>.md; write-once/no-overwrite;
     STOP_AND_ESCALATE on differing-content collision; metadata header +
     STRICT delimited normalized-content region (identity = hash of region only)
doc3 capture-procedure-draft: read-only CP-1..CP-8 (rehash gate REQUIRED);
     two-gate controlled-execution outline E1(capture+freeze) / E2(seed);
     rollback R1..R5 (never overwrite/delete artifact)
doc4 seed-strategy+verification: content_checksum := snapshot checksum;
     provenance snapshot_*/parser_profile_ref/marker_counts/captured_*/
     supersedes(=null, justified); document_version_id rule VERBATIM unchanged;
     SNAP/POST/NEG + live-drift-independence (LD-1)
doc5 this report

3. Binding rulings honored

Q1 Option B captured artifact = immediate path           -> implemented (QG1)
Q2 document_version_id rule unchanged                     -> verbatim (QG4)
Q3 parser_profile nuxt-incomex-portal-constitution-v1     -> kept
Q4 minimal version_status now (snapshot_captured/fetched) -> applied, details deferred
Q5 supersede lineage via provenance jsonb                 -> provenance key (=null first)
Q6 checksum-addressed write-once + rehash-before-use      -> spec + CP-7 + SNAP-3 (QG2/QG3)
no-retry-old-checksum / no-silent-update / no-unpinned-seed -> preserved

4. Recommended next controlled execution path (QG6)

recommended: TWO separately-gated executions (no seed DML authored against an
  unknown checksum):
  STEP A (this package) -> GPT command-review
  STEP B  E1 gated execution: read-only PRE + CP-1..CP-7 -> WRITE the write-once
          snapshot artifact + rehash PASS  (NO seed)  -> report the now-known
          snapshot checksum
  STEP C  author the seed DML bound to that known checksum -> GPT command-review
  STEP D  E2 gated execution: PRE re-confirm (rows 0/0, artifact present, rehash
          PASS) -> atomic source_document + source_document_version seed ->
          POST/NEG/CK -> on FAIL rollback (doc-3 §3)  -> closes B5
rationale: freezing the artifact FIRST yields a stable, reviewable checksum so
  the seed DML and its command-review reference a fixed identity — eliminating
  the live-page race that blocked Codex.
not_now: E1/E2 are NOT executed; each needs explicit GPT/User authorization.

5. Open items for GPT command-review (do not block readiness)

O1 confirm 16-hex filename prefix (full 64-hex in metadata + SC1 full compare)
O2 confirm version_status concrete value pending live-schema read-only recheck
   at E1 ('snapshot_captured' preferred else 'fetched')
O3 confirm two-gate E1/E2 split (vs single combined gated run)
O4 confirm supersedes_document_version_id = null on first seed (no prior row
   ever persisted — Codex blocked pre-DML)
O5 confirm snapshots/ directory location under dieu44-trien-khai/ acceptable
O6 confirm content-region delimiter convention (BEGIN/END sentinels) as the
   exact identity-hash boundary

6. No-mutation statement

No live fetch-for-capture, no snapshot artifact write, no source_document / source_document_version INSERT, no DML, no checksum persisted or updated, no dry-run, no CUT, no VERIFY, no schema / GRANT / index change, no Directus mutation, no deploy/restart, no git commit, no self-advance. Authority docs read READ-ONLY from KB (Agent Data). Only KB mutation: these 5 authoring documents. (QG5)

7. Statement

• Option B snapshot-capture direction fully authored (QG1); checksum-addressed path + no-overwrite + STOP-on-collision defined (QG2); rehash gate required before seed/dry-run/cut (QG3); document_version_id rule kept verbatim (QG4); nothing executed or mutated (QG5); two-gate next controlled path recommended (QG6); 5 files then STOP (QG7).
• doc 5 of 5; package complete; STOP → route GPT/User. Self-advance PROHIBITED.

Companions: operational-framing, artifact-spec, capture-procedure-draft, seed-strategy-and-verification-plan.