Mega Gate — Điều 0-G Source Authority Gap
Mega Gate — Điều 0-G Source Authority Gap
Date: 2026-06-18 · Workstream: LEGO-PILOT-SLICE-0-B2-MEGA-GATE-BUNDLE-2026-06-18 (Deliverable 10 of 20) · Editorial revision: rev1
Class: design-only / source-authority gap / decision-support · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NOT remediation · NOT technical design · NOT implementation · NO blocker resolved · NO runtime touched.
Metadata convention. Editorial revision (rev1) only. AgentData storage revision and
content_lengthare authoritative in AgentData metadata at read time; not pinned in this body.
Source-gap lock. This packet documents the Điều 0-G source-authority gap (the inspection rule-set B2 must encode is read from a working source with a broken Constitution reference) and states what recovery requires. It recovers no source, adopts no rule-set, and edits no law/note/report. Recovery is Owner-controlled and out-of-band (external S6). Per CAV-2-style discipline, it asserts only that the source is unreconciled in the inspected substrate, not that it is unrecoverable.
0. Status and non-authorization
STATUS: PASS — engineering / design-only. This is a complete design-only source-authority gap packet: what the Đ0-G rule-set is and where it lives, why it is a working source (not the authoritative law), which part is least-precedented (STAMP/GATE), what recovery requires, what a B2 TD may/may not assume about it, and the Owner-gated future work.
Engineering PASS ≠ authority PASS. A PASS means the gap is fully characterized on paper. It does not recover the source, adopt the working source as authoritative, or resolve PO-1. Default disposition: HOLD.
Pipeline position (downstream-only). Deliverable 10 of the Mega Gate Bundle; it is Option D (resolve Đ0-G source authority) characterized as a gap, and the GATE-3 / PO-1 prerequisite for B2 TD. It recovers nothing.
Non-authorization (explicit). As Deliverable 1 §0, and specifically: it recovers no source; adopts no rule-set; patches no law/note/report; resolves no blocker (PO-1 stays open). v0.1/FIX7 V3 not overwritten; v0.2 not authority.
Evidence basis — INHERITED_EVIDENCE + first-hand Đ0-G read. The Đ0-G working source (architecture/birth-registry-law.md, v1.0/S157/2026-03-21) was read first-hand this run; the authority status (broken Constitution reference; not in laws/) is inherited from the accepted Điều 4 note + readiness scope. AgentData metadata authoritative at read time. CAV-2 discipline applied.
Reading discipline (Codex caveat, honored). All sources read directly from AgentData KB, bounded/sequential, by the main process — no parallel/background reader-agents, no sub-agents, no local-prose inference. /tmp = decode-scratch only, never SSOT.
1. Purpose
Characterize the macro's source-authority question for B2: what exact source gap stands between the carried Đ0-G rule-set and an authoritative basis for B2 TD? The packet answers:
- What is the Đ0-G rule-set, and where does it live? — §3 / §5.
- Why is it a working source, not the authoritative law? — §5.
- Which part is least-precedented? — §5 (STAMP/GATE).
- What does recovery require, and who does it? — §5 / §6 (external S6, Owner out-of-band).
- What may/may not a B2 TD assume about it? — §5.
The one rule, above all detail. B2 must encode the meaning of "inspected" from an authoritative Đ0-G source; today that source is a working document with a broken Constitution reference. TD may not silently treat the working source as authoritative; recovery (or explicit Owner acceptance with the caveat recorded) is the GATE-3 prerequisite. This packet documents the gap; it recovers nothing.
2. Sources read
All 25 required sources read first-hand from AgentData KB, by the main process, sequentially; none SOURCE_NOT_READ (full list in Deliverable 20 §2). Used principally: architecture/birth-registry-law.md (Điều 0-G v1.0 — the rule-set itself, read first-hand); the Điều 4 compatibility note (Đ0-G lives in architecture/, not laws/; law-00g-birth.md reference broken); the B2 TD-prep §5/§15 (PO-1; STAMP/GATE least-precedented); the interface packet S6 (out-of-band recovery); operating-rules ("không chắc đúng = sai").
3. Accepted baseline (carried, not re-derived)
The Đ0-G inspection rule-set (carried from architecture/birth-registry-law.md §2.4; the meaning of "inspected"):
| Inspector | Scope (rows considered) | Pass criteria | On pass | On fail |
|---|---|---|---|---|
PEN (inspect_pen) |
uncertified, inspect_pen unset, governance_role='governed' |
birth-completeness: entity_code + dot_origin + species_code present |
set inspect_pen only |
append failure to audit queue |
STAMP (inspect_stamp) |
inspect_stamp unset and inspect_pen present |
metadata-completeness: name + description + status present |
set inspect_stamp only |
append failure to audit queue |
GATE (inspect_gate) |
inspect_gate unset and inspect_stamp present |
validity: correct species mapping ("đúng chuồng") + business rules | set inspect_gate only |
append failure to audit queue |
| (consumer — NOT B2) | all three present | — | fn_birth_auto_certify sets certified=true, certified_at |
— |
Plus the two load-bearing invariants: strict PEN→STAMP→GATE order; "mỗi DOT chỉ UPDATE cột của mình" (each inspector writes only its own column).
Source-authority facts (carried):
- Điều 0-G v1.0 lives at
architecture/birth-registry-law.md(S157, 2026-03-21) — a temporary working source, not inlaws/, not embedded in the Constitution. - The Constitution reference
law-00g-birth.mdis broken (the file is absent) →SOURCE_RECOVERY_REQUIRED. - The Đ0-G DOT-tools table itself marks PEN = Phase A (built:
dot-inspect-pen, PEN only) and STAMP/GATE = Phase B (Planned, "verify: ls /opt/incomex/dot/bin/dot-inspect-*") — i.e. STAMP/GATE inspection logic was never built. - Blockers — all OPEN. Tool/packet lock carried.
4. Analysis — what kind of gap this is
This is a source-authority gap, not a content gap: the rule-set content is legible (§3), but its authority is unestablished — it sits in a working architecture document whose canonical Constitution anchor is broken. Two consequences:
- TD encoding risk. If B2 TD encodes the PEN/STAMP/GATE meanings from a working source, it pins the producer's behavior to a non-authoritative definition; a later authoritative recovery could change the meaning, forcing rework. This is why GATE-3 requires either recovery or explicit Owner acceptance with the caveat recorded.
- Least-precedented asymmetry. PEN was built once (
dot-inspect-pen, PEN only); STAMP and GATE were Phase B and never built. So the STAMP/GATE meanings (metadata-completeness; species-fit/business-rules) are the most design-open and the most dependent on an authoritative source — they have no implemented precedent to fall back on. CAV-2 discipline: the source is unreconciled in the inspected substrate; this does not assert it is unrecoverable.
5. The source-authority gap — characterized
| # | Gap element | State today | What recovery / acceptance requires | What B2 TD may / may not assume |
|---|---|---|---|---|
| SG-1 | Đ0-G canonical anchor | law-00g-birth.md reference broken; Đ0-G in architecture/ only |
Re-establish Đ0-G at an authoritative source (external S6, Owner out-of-band), or an explicit Owner decision to accept the working source as the TD basis | May not silently treat the working source as authoritative; may proceed only if the Owner accepts it with the caveat recorded (GATE-3 waiver) |
| SG-2 | PEN criteria | built once (dot-inspect-pen, PEN only); meaning legible |
confirm the PEN completeness criteria against the recovered source | May design to the carried PEN criteria, flagged as working-source-derived until recovered |
| SG-3 | STAMP criteria | never built (Phase B); meaning legible but least-precedented | confirm/define the metadata-completeness criteria (name/description/status) against the recovered source |
Most design-open; B2 TD must flag STAMP as least-precedented (PO-1 caveat) |
| SG-4 | GATE criteria | never built (Phase B); meaning legible but least-precedented | confirm/define the species-fit + business-rule criteria ("đúng chuồng") against the recovered source | Most design-open; B2 TD must flag GATE as least-precedented (PO-1 caveat) |
| SG-5 | Ordering + one-column invariants | legible and load-bearing | confirm PEN→STAMP→GATE order + "one column per inspector" against the recovered source | May design to these invariants (they are also B2-AC-13/14), flagged as working-source-derived |
| SG-6 | Schema currency | the birth_registry schema has drifted post-v1.0 (added status, canonical_address, owner, jsonb_profile) — the Đ0-G v1.0 DDL is a baseline, the PG catalog is the runtime truth |
a read-only schema re-confirm (Macro-1) + the recovered Đ0-G | May not treat the v1.0 DDL column-count as current; must read the live catalog (GATE-2) |
Recovery posture (CAV-2 discipline). Recovery is out-of-band and Owner-controlled (external S6); this lane cannot perform it. The packet asserts only that the Đ0-G source is unreconciled in the inspected substrate — it does not assert the source is unrecoverable, and it does not invent or adopt a rule-set. The "không chắc đúng = sai" rule applies: with no authoritative Đ0-G, B2 fails closed (no stamp) on BAD-5 / BI-5 (Deliverable 14).
B2-TD readiness verdict for the source authority (GATE-3 / PO-1): NOT ready. TD that depends on the STAMP/GATE definitions is blocked until Đ0-G is recovered to an authoritative source or the Owner explicitly accepts the working source as the TD basis with the caveat recorded (and STAMP/GATE flagged least-precedented).
6. Owner-gated future work
| Future work | Gate required | Forbidden now? |
|---|---|---|
| Recover Đ0-G to an authoritative source (closes GATE-3 / PO-1) | external S6 — Owner out-of-band | Yes |
Accept the architecture/ working source as the TD basis (GATE-3 waiver) |
Owner decision, with the caveat recorded | Yes (not done here) |
Re-confirm the live birth_registry schema (SG-6) |
Owner authorizes a read-only pass (Macro-1) | Yes |
| Encode the recovered/accepted PEN/STAMP/GATE logic in B2 TD | GATE-3 met + Điều 32 | Yes |
Patch the broken Constitution law-00g-birth.md reference |
separate Owner-gated documentary step (not a remediation; not done here) | Yes |
7. What remains unresolved
- PO-1 / GATE-3 OPEN — Đ0-G is a working source with a broken Constitution reference; recovery is out-of-band (external S6).
- STAMP/GATE are the least-precedented logic (never built; Phase B) — most dependent on an authoritative source.
- Schema currency (SG-6) — the v1.0 DDL is a baseline; the live catalog is the runtime truth (read-only re-confirm owed via GATE-2).
- No recovery / no adoption performed — this lane cannot recover the source; it documents the gap only (CAV-2 discipline).
- Blockers — all OPEN, none resolved: CONS-002, CONS-003, CELL-003/004/007, HOLD-1, HOLD-2, RISK-BYPASS, GOV-016/017, GOV-REUSE-001, Điều 39 runtime-EMPTY, Điều 35 production-readiness FAIL.
- FUTURE_TECHNICAL_DESIGN_REQUIRED (NOT written here): the recovery mechanics; the rule-set encoding; the schema re-confirm queries; the documentary reference patch.
8. Ready for GPT/Codex review
Yes — as a design-only source-authority gap packet, not a recovery.
Core rule, kept above all detail: B2 must encode the Đ0-G "inspected" meaning from an authoritative source; today it is a working document with a broken Constitution reference, and STAMP/GATE are the least-precedented (never-built) parts. GATE-3 closes only by out-of-band recovery (external S6) or explicit Owner acceptance of the working source with the caveat recorded. Nothing is recovered or adopted here.
Default disposition: HOLD. Engineering PASS = a complete gap characterization on paper; it is not an Owner authorization to recover, adopt, or encode the rule-set. No PASS authorizes writes. All blockers remain OPEN.