dot-iu-cutter v0.5 — Constitution Source Snapshot & Version Policy Report

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

package_status: AUTHORED ; ready_for_GPT_review: YES
nature: read_only_design_authoring__no_seed_no_dml
dml/seed: 0 ; checksum_persisted_or_updated: NONE ; mutation: none
  (Agent Data read-only inspection only) ; git_commit: false
B5_source_document_version_seed: OPEN/BLOCKED (unchanged this phase)
decision_authority: GPT / User ONLY ; self_advance: PROHIBITED

1. Executive summary

The Constitution source is a living AD→Directus→Nuxt article (knowledge/dev/laws/constitution.md, AD revision 44, AD = SSOT). The 2026-05-18 QG1 block was a real source change (living KB-revision drift), correctly handled. GPT selected OPT_2 pin immutable snapshot (primary) + OPT_3 version model policy (secondary); OPT_1 re-ratify only after a snapshot/policy exists. This package authors the operations framing, options analysis, version policy, and seed-strategy update. Nothing executed or mutated.

2. Recommended immediate path (QG4 — one safe route)

recommended: Option_B — captured snapshot artifact, reusing the ratified
  parser_profile nuxt-incomex-portal-constitution-v1
why:
  - directly satisfies GPT primary OPT_2 (immutable pin) with the LEAST new design
  - reuses B6 (CLOSED) + the ratified parser profile -> no new determinism proof
  - offline re-hash verification -> the seed/cut race is structurally CLOSED
  - simplest operations-first route to unblock B5 safely
important_nuance: the previously-ratified bytes (f9d22d05…/17791) are NOT
  recoverable (never persisted verbatim). Option B therefore freezes the
  CURRENT content (Codex-observed 17522/17660443… under the nuxt profile) as
  the immutable artifact. This is a legitimate OPT_1 "re-ratify a NEW version"
  — but now race-free because it is pinned to frozen bytes, exactly the GPT
  precondition ("OPT_1 only_after_snapshot_or_version_policy_is_defined").
durable_upgrade (later, not now): Option_A (AD markdown revision) once an AD
  historical-revision fetch capability is confirmed + a new markdown parser
  profile is ratified. Option_D (raw canonical endpoint) logged as a future
  enabler for the batch-factory direction. Option_C REJECTED as production
  identity (usable only as the fetch step inside B's capture).

3. Next phase decision (QG4)

next_phase: v0_5_constitution_source_snapshot_capture_authoring
nature:     authoring_only__no_execution   (capture procedure + artifact spec +
            integrity gate + revised atomic seed bound to the artifact)
NOT chosen:
  - policy_only_closeout  -> rejected: leaves B5 blocked, no path to cut
  - raw_endpoint_design   -> deferred: future enabler, needs infra, not immediate
  - source_seed_re_authoring_directly -> premature: must first define & freeze the
    snapshot artifact + its write-once/integrity convention
sequence (each separately gated; no self-advance):
  1. THIS design package            -> GPT review
  2. (if PASS) snapshot-capture authoring: capture procedure + write-once
     checksum-addressed artifact spec + snapshot-integrity precheck +
     revised atomic seed DML draft  (still NO execution)
  3. GPT command-review of the capture+seed package
  4. (if PASS) separately-gated controlled capture + seed execution
     -> closes B5 on verified success

4. Blocker / state disposition

B1_marker_coverage:                 CLOSED (unchanged)
B6_parser_checksum_determinism:     CLOSED for a fixed content revision (NOT
                                    invalidated by this drift — GPT confirmed)
B5_source_document_version_seed:    OPEN/BLOCKED — unblock path now DEFINED
                                    (Option B snapshot capture), execution gated
live_source_drift:                  CONFIRMED real; handled by INV-SNAP + version
                                    policy; recurrence prevented by pinning
rejected_and_still_forbidden:       retry old checksum f9d22d05… ; silent
                                    in-place checksum update ; seed from unpinned
                                    live page ; all execution/mutation this phase

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

Q1: confirm Option B (immediate) + Option A (durable upgrade) + D (future) split
Q2: confirm document_version_id rule kept UNCHANGED (recommend keep)
Q3: confirm parser_profile stays nuxt-incomex-portal-constitution-v1 for Option B
Q4: confirm version_status lifecycle (fetched->ratified->active; old->superseded)
    pending live-schema read-only reconfirmation in the capture phase
Q5: confirm supersede lineage via provenance jsonb until/unless schema amendment
Q6: confirm write-once convention for the checksum-addressed KB artifact
    (KB docs are revisioned; immutability is by convention + re-hash gate)

6. No-mutation statement

No source / production / Directus / repo mutation. No DML, no source_document / source_document_version INSERT, no checksum persisted or updated, no snapshot captured, no dry-run, no CUT, no VERIFY, no schema / GRANT / index change, no deploy/restart, no git commit. Agent Data accessed READ-ONLY (get_document / list / batch_read). Only KB mutation: these 5 design documents. (QG6)

7. Statement

• Live source drift treated as real; old checksum never retried (QG1). Four snapshot/version options evaluated (QG2). Version-model policy for same-label/changed-checksum defined with drift taxonomy + supersede/lineage (QG3). One safe immediate path recommended = Option B snapshot-capture authoring next (QG4). No-silent-update preserved structurally + by policy (QG5). Nothing executed or mutated (QG6). 5 files uploaded then STOP (QG7).
• doc 5 of 5; package complete; STOP → route GPT/User. Self-advance PROHIBITED.

Companions: operations-framing, options-analysis, version-policy-design, seed-strategy-update.