dot-iu-cutter v0.5 — Source Document & Authority Selection

Date: 2026-05-17 · Status: DESIGN ONLY — no source ingested, no write, no selection committed. Parent: design-master.

1. The three already-cut documents (grounded, read-only)

public.tac_logical_unit (production) contains exactly three documents (the "three previously cut documents"):

doc_code	rows	shape	authority	lifecycle	fmt
DIEU-28	27	root/section/unit (fully tiered)	draft	draft_only	canonical-address-v1
DIEU-32	23	tier blank	draft	draft_only	canonical-address-v1
DIEU-35	36	tier blank	draft	draft_only	canonical-address-v1

All 86 rows uniformly non-enacted draft. These are articles ("Điều") of the dieu44 dossier (address prefix D38-). The first production CUT/VERIFY trial cut one DIEU-28 leaf IU (D38-DIEU28-S3-P1). They are the merge baseline for any new full document.

2. Authoritative source for Hiến pháp — NOT in system; OPEN

No constitution/Hiến pháp document exists in the corpus (only DIEU-28/32/35). The authoritative source is external and is not invented here. Candidate (worked example, subject to GPT): the officially promulgated Hiến pháp nước CHXHCN Việt Nam năm 2013 — Lời nói đầu + 11 Chương + 120 Điều; Điều contain Khoản, some contain Điểm.

OD-2 (OPEN for GPT) — authoritative source & ingestion: which canonical text/edition is authoritative (official gazette text vs an internal vetted copy); how it is ingested into public.tac_logical_unit (manual structured load vs an ingestion tool — note: the v0.4 cutter consumes a signal/IU reference; ingestion of the raw constitution into logical units is a separate upstream step, not the cutter's job, and is itself unauthorized/undesigned). No source path is hardcoded; source location is config/parameter-driven (no-hardcode rule).

3. Authority / lifecycle posture (proposed)

• Trial target authority = draft / draft_only only, never enacting the constitution (the supreme legal instrument; enacting is categorically out of scope). This mirrors the validated single-IU trial (draft_only/draft) and bounds blast radius. OD-12 (confirm).
• The constitution is maximum legal authority as a real-world instrument → even a draft-only cut is high reputational/blast-radius; this argues for dry-run-first + staged batch (see routing design) and possibly choosing a smaller, lower-authority document as the actual first full-document target instead of Hiến pháp. OD-1 (OPEN) — GPT explicitly said "Do NOT cut Hiến pháp yet"; Hiến pháp here is the design example only.

4. Selection criteria for the first full-document target (proposed)

Whatever document is chosen (OD-1): non-enacted/draft posture; complete & stable source; bounded article count for a first staged run; co-residency-safe canonical-address namespace (no collision with D38-DIEU28/32/35); not a load-bearing enacted instrument. Hiến pháp satisfies "complete/structured" but is the highest-authority instance — explicitly flagged.

Boundaries / Git

Design only; no ingestion, no write, no selection finalised. Git: main · e93424b5ff7fa5e4b8406131977ce4339cd0856a · git status --short -- iu-cutter clean (0 lines). No hardcoded source path/label/destination. SQL SSOT; no vector/NoSQL. Open: OD-1, OD-2, OD-12. Next = GPT review.