KB-65BE

Macro-3 Điều 0-G Source-Authority Proof Plan (2026-06-19)

3 min read Revision 1
laws-newR2-B2macro-3dieu0gsource-authorityproof-plannon-authorizingowner-gated2026-06-19

Macro-3 Điều 0-G Source-Authority Proof Plan (2026-06-19)

Date: 2026-06-19 · Workstream: R2-B2-MACRO-3-OPTION-D-OWNER-DELEGATE-DECISION-PACKAGE-2026-06-19 (Deliverable 29 of 60) · Editorial revision: rev1 Class: Điều 0-G source-authority proof plan · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · proof obligations only — NOT run · SOURCE_ADOPTION_DRIFT guard · NO write performed.

Metadata convention. Editorial revision (rev1) only. Storage revision/content_length authoritative at read time.


0. Status and non-authorization

STATUS: PASS — engineering / decision-prep. What recovery (0G-A) must prove before the source is authoritative. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Define the obligations that turn the legible working source into a recovered, anchored, authoritative source.

2. Sources / evidence read

Macro-2 lineage matrix, working-vs-authoritative packet. Main process, no reader-agents.

3. Accepted baseline (carried)

Authoritative = recovered (via S6) + anchored (Constitution ref resolvable) + rules pinned/precedented.

4. Evidence / analysis — proof obligations (0G-PO)

# Obligation
0G-PO-1 Recover the source via external S6 (out-of-band), preserving lineage
0G-PO-2 Fix the broken anchor so law-00g-birth.md (or its successor) resolves in-force
0G-PO-3 Pin PEN/STAMP/GATE rules to the recovered authority (no free-floating text)
0G-PO-4 Reconcile in the inspected substrate (not just the architecture/ doc)
0G-PO-5 Record provenance so the authority is auditable (no silent adoption)

5. Recommendation / matrix / result

Satisfying 0G-PO-1…5 is what "recover-first" means; none is attempted here. Until then GATE-3 stays NO_GO.

6. Owner-gated future work

Recovery + anchoring are Owner-gated, out-of-band; forbidden now.

7. What remains unresolved

No obligation satisfied; source not authoritative.

8. Ready for GPT/Codex review

Yes — Codex should confirm 0G-PO-4 (substrate reconciliation) is required, not just doc-level legibility.

Back to Knowledge Hub knowledge/dev/laws-new/newlaws/consolidation/macro3-dieu0g-source-authority-proof-plan-2026-06-19.md