Macro-2 Điều 0-G Working Source vs Authoritative Source — R2-B2 (2026-06-19)
Macro-2 Điều 0-G Working Source vs Authoritative Source — R2-B2
Date: 2026-06-19 · Workstream: R2-B2-MACRO-2-OWNER-DECISION-PREREQ-CLOSURE-READINESS-2026-06-19 (Deliverable 21 of 45) · Editorial revision: rev1
Class: Điều 0-G working-vs-authoritative analysis / decision-support · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO source recovered · NO source adopted · NO patch · NO write performed.
Metadata convention. Editorial revision (rev1) only. AgentData storage revision/
content_lengthauthoritative at read time; not pinned here.
Distinction lock. This packet distinguishes the working source (the legible
architecture/document) from an authoritative source (recovered + anchored). It adopts neither and recovers nothing. Per CAV-2: working-source legibility ≠ authority.
0. Status and non-authorization
STATUS: PASS — engineering / decision-support. The explicit working-vs-authoritative distinction and the gap between them. It adopts nothing.
Engineering PASS ≠ authority PASS. Default disposition: HOLD. No source recovered/adopted; no patch; no DB write/DDL/DML; no TD; no blocker resolved; v0.1 not overwritten; v0.2 not authority.
Evidence basis — FRESH read of source + INHERITED_KB_EVIDENCE. Reading discipline: main process, no reader-agents.
1. Purpose
Stop the common error of treating a legible working source as authoritative. Define the two clearly and state what closes the gap.
2. Sources / evidence read
Deliverable 20 (lineage); the 30-file Đ0-G recheck; the Mega-Gate Đ0-G gap; the Điều 4 note. Read directly, main process.
3. Accepted baseline (carried)
Recovery is OOB (external S6); the alternative is Owner acceptance of the working source with caveat (GATE-3 waiver). Both are Owner-gated.
4. Working source vs authoritative source
| Dimension | Working source (today) | Authoritative source (target) |
|---|---|---|
| Location | architecture/birth-registry-law.md |
laws/ and/or embedded in the Constitution |
| Anchor | Constitution ref law-00g-birth.md broken |
resolvable, in-force anchor |
| Legibility | legible (PEN/STAMP/GATE rules readable) | legible and authoritative |
| Build precedent | PEN built (Phase A); STAMP/GATE Phase-B, never built | rules pinned, precedented or explicitly approved |
| Status for TD | designable-to with caveat (GATE-3 waiver) | safe TD basis |
| How to get there | accept-with-caveat (Owner) | recover via external S6 (OOB) |
The gap: content is present, authority is not. CAV-2 discipline: the source is unreconciled in the inspected substrate — this does not assert it is unrecoverable; recovery (S6) may establish authority later.
5. What closes the gap (Owner-gated)
- Recover (S6, OOB): fix the Constitution anchor + pin the PEN/STAMP/GATE definitions → working source becomes authoritative.
- Accept-with-caveat (GATE-3 waiver): the Owner accepts the working source as TD basis, recording the caveat (broken anchor; STAMP/GATE least-precedented). Designable, with risk recorded (Deliverable 22).
- Either is the Owner's; neither is done here.
OWNER_DECISION_REQUIRED.
6. Owner-gated future work
Recovery (S6), acceptance-with-caveat, and any anchor patch are Owner-gated; forbidden now.
7. What remains unresolved
- Working source legible but not authoritative; gap open.
- Blockers — all OPEN.
8. Ready for GPT/Codex review
Yes — as the working-vs-authoritative analysis.
Core rule: the architecture/ source is legible but not authoritative; the gap closes only by S6 recovery or an Owner accept-with-caveat; neither performed; nothing adopted.
Default disposition: HOLD. Engineering PASS ≠ authority PASS. All blockers remain OPEN.