dot-iu-cutter v0.5 — Constitution Nuxt Parser Reference Authoring Report

Phase: v0_5_constitution_nuxt_parser_reference_implementation_authoring · Nature: authoring + read-only test — no capture, no seed, no DML · Date: 2026-05-18 · doc 5 of 5

decision_authority: GPT / User ONLY ; self_advance: PROHIBITED

1. Outcome

phase_status: PASS
parser_profile: nuxt-incomex-portal-constitution-v1
reference_implementation: nuxt-incomex-portal-constitution-v1.refimpl.r1 (doc 3)
reproduces_ratified_canonical: YES — 17660443e0f23e994e1807cf8e22920951a9e70c
  598956dbd0e752f4f5cae80c / length 17522 / markers ✅19 📋1 📝1 ⛔1,
  deterministic 3/3 on the live source (doc 4)
divergence_root_cause: IDENTIFIED — N8 vertical-whitespace ("collapse blank-line
  runs to a single \n"). Canonical = drop ALL empty lines (one \n between
  content). Claude E1's prose reconstruction kept a blank line between blocks
  -> deterministic +135 chars -> 072983ac…/17657. Proven by single-step variant
  ablation (doc 2 §4, doc 4 §3): V-canonical == 17660443/17522,
  V-detag == 072983ac/17657 exactly. Markers / span / NFC / entity / nbsp
  excluded as causes.
source_drift: NONE vs the ratified canonical (live normalized content is
  byte-identical; raw byte variance is forensic Nuxt render noise).

2. Quality gates

QG1 no snapshot/seed write          : PASS (no artifact, no INSERT, no DML; KB
                                       read-only + 5 uploads; /tmp scratch deleted)
QG2 identify divergence or insuff.  : PASS (precisely localized to D-VSPACE; not
                                       "insufficient evidence")
QG3 byte-exact reference impl       : PASS (doc 3; embedded form verified)
QG4 test vs live/source fixture     : PASS (read-only ·3; exact canonical repro)
QG5 no silent canonical update      : PASS (canonical reproduced & confirmed,
                                       never altered/invented)
QG6 recommend safe next step        : PASS (§4 below; decision left to GPT/User)
QG7 stop after 5 files              : PASS (this is doc 5; STOP next)

3. Forbidden-list compliance

snapshot artifact write          : NOT done
source_document INSERT           : NOT done
source_document_version INSERT   : NOT done
DML execution                    : NOT done
production DB mutation           : NOT done
checksum persistence into registry: NOT done (reproduced in /tmp scratch only)
dry-run / CUT / VERIFY           : NOT done
schema change / GRANT/REVOKE     : NOT done
Directus mutation                : NOT done
deploy / restart                 : NOT done
git commit                       : NOT done (reference impl is in KB, not a repo)
self-advance to E1 capture / E2  : NOT done

4. Recommended next step (decision is GPT/User — NOT taken here)

Per task §5 branch 1 (implementation reproduces canonical) the safe path is:

recommended:
  S1 GPT ratifies reference implementation nuxt-incomex-portal-constitution-v1.
     refimpl.r1 as THE canonical executor for parser_profile
     nuxt-incomex-portal-constitution-v1 (the GPT-selected R2 durable path).
  S2 THEN open a gated E1 re-run that uses ONLY this ratified implementation to
     capture + freeze the snapshot artifact. Because the artifact identity =
     sha256 of the BEGIN/END sentinel region = this implementation's
     normalized_content, the frozen checksum WILL equal the ratified canonical
     17660443…/17522 (no executor ambiguity remains).
  S3 E2 seed binds source_document_version.content_checksum to that pinned
     artifact (unchanged Option-B chain; still atomic, enacted_only, Điều 44
     deferred; still separately gated).
durability_note: this also satisfies drift-triage OPT-2 (pin immutable
  snapshot) + OPT-3 (version policy) — once the artifact is frozen under a
  ratified implementation, future "Cắt Hiến pháp" rehashes the artifact and is
  immune to live Nuxt re-render AND executor divergence. Live-page drift, if it
  later occurs, surfaces as FAIL_DRIFT → new version + review, never silent.
fallback_if_GPT_prefers_R1: a canonical-executor (Codex/VPS) E1 re-run remains
  valid; the refimpl then serves as the cross-executor equivalence oracle.

Requested rulings (Agent recommends; decides nothing)

R-RI1 ratify reference implementation refimpl.r1 as canonical executor for
      nuxt-incomex-portal-constitution-v1?  (recommend YES)
R-RI2 canonical script form + its sha256: ratify the doc-3 §4 embedded source as
      the canonical text and have the ratifying executor re-pin a sha256 over an
      agreed canonical header line (script hash is provenance, NOT identity —
      identity stays normalized_content_checksum).  (recommend YES)
R-RI3 D-VSPACE canonical semantics ("single \n" = drop all empty lines) — adopt
      as the normative N8 reading and amend the prose profile doc-3 §3 to remove
      the ambiguity?  (recommend YES)
R-RI4 next phase = gated E1 re-run using refimpl.r1 (S2), or GPT prefers R1
      canonical-executor re-run with refimpl.r1 as equivalence oracle?
      (recommend S2)
none_self_resolved: all are flagged requests; B5 remains OPEN until GPT rules.

5. State delta

before: E1 BLOCKED (SC3 parser-profile reproduction divergence); parser profile
  prose-only; no portable byte-exact implementation; canonical checksum not
  reproducible by non-canonical executors.
after:  byte-exact reference implementation authored in KB SSOT; reproduces the
  ratified canonical 17660443…/17522/19·1·1·1 deterministically on the live
  source; +135 divergence root-caused & fixed (D-VSPACE). B5 still OPEN (E1
  re-run + seed are separately gated and NOT performed). B6 mechanism intact.
unchanged: enacted_only first dry-run scope; Điều 44 controlled-draft deferred;
  document_version_id rule; Option-B snapshot/version policy; artifact spec
  (checksum-addressed, write-once, sentinel-region identity).

6. Statement

• PASS: byte-exact reference implementation authored + KB-embedded + verified to reproduce the ratified canonical identity 3/3 on the live source; historical +135 divergence root-caused to D-VSPACE and removed.
• Nothing executed/persisted/mutated beyond this 5-file KB authoring package; /tmp scratch deleted; no secrets recorded.
• doc 5 of 5; STOP → route GPT/User review. Self-advance PROHIBITED.

Companions: operational-framing, algorithm-analysis, implementation-draft, test-result.