01 — Ratification Question & Scope

Package: one-roof-auth-model-ratification-intake-2026-06-02 Answers mission §2.1: What exact decision needs ratification?

---

1.1 The exact decision (verbatim scope)

Adopt the L0–L4 authorization model by jointly enacting D-BOOT-1 and D-BOOT-2:

D-BOOT-1 — Redefine the master commit gate M-1 from "a row exists in os_proposal_approvals" (today: an unrelated sales-proposal human e-signature surface) to "a valid per-step governance_build_authorization (SB-0) grant exists for THIS build step," whose validity is recomputed (not asserted) from the backing L2 council quorum and, where the step is constitutionally reserved, an L4 sovereign e-sign.

D-BOOT-2 — Adopt SB-0 governance_build_authorization as the L3 technical build gate, and reserve os_proposal_approvals exclusively for the L4 sovereign e-sign branch (interim target; final target governance_sovereign_esign, hardening doc 12 P3).

The L0–L4 ladder being adopted (hardening doc 02 §2.x)

Level	Authority	What it gates
L0	auto-approve, allowlisted reversible (create_item-class, risk=low)	trivial reversible writes
L1	one non-proposer approver	low-risk single-sign
L2	full council quorum — fn_apr_quorum_check: high ⇒ ≥1 president-human + ≥2 ai_council; medium ⇒ ≥1 president; low ⇒ ≥1 approve; any reject blocks; proposer may not self-approve	governed changes
L3	a valid governance_build_authorization grant issued by someone other than the consuming agent (INV-5)	per-step build authorization (the new M-1)
L4	sovereign e-signature for constitutionally-reserved acts (any birth_registry truth write, law status/version change, and the adoption of this model itself)	constitutional acts

1.2 Why this specific decision is a constitutional bootstrap (not engineering)

SB-0 is simultaneously the first thing the new model would build and the gate the new model uses to authorize building. Authorizing the authorization model through the authorization model is circular — SB-0 cannot issue the L3 grant that would authorize building SB-0.

The only non-circular way to break in is a one-time, out-of-band constitutional ratification: a recorded L2 council decision to adopt the model, plus an L4 sovereign e-sign of that adoption. This is a decision dependency, not an engineering gap — the design is build-ready and rehearsed-green (bootstrap package docs 03–05); nothing remains to design or test. What remains is a human/sovereign act of will that, by constitutional construction, an Agent cannot supply for itself.

The new model is explicitly forbidden from removing the President's single act of e-signing its own adoption (hardening doc 02 §2.7). Self-bootstrapping is the one thing it must not do.

1.3 What is IN scope for this mission

• Decide whether the ratification can be recorded by an Agent through legitimate live mechanisms (doc 03).
• If yes → record the minimal legitimate decision/intake artifact and verify it.
• If no → produce a human/sovereign ratification-ready packet with exact UI/manual steps and stop (doc 04).
• State the build GO/NO-GO and the next macro (docs 05, 06).

1.4 What is explicitly OUT of scope (forbidden)

No Phase-1 build; no SB-0/axis substrate build; no fake/self-approval; no e-sign fabrication; no write to os_proposal_approvals; no event/DOT registration; no event emit; no Directus/Qdrant/Nuxt mutation; no law enactment/version/status change; no production change; no hardcode; no local governance island. (Mission §5, enforced and attested in doc 07.)

1.5 The ratification requirement, stated explicitly (mission §3 criterion)

R-REQ: Enacting D-BOOT-1 + D-BOOT-2 requires a one-time constitutional ratification consisting of (a) a recorded L2 council quorum decision adopting the M-1 redefinition and the L0–L4 ladder, and (b) an L4 sovereign e-signature of that adoption by the President. Both are human/sovereign acts. Silence ≠ approval. No Agent step can satisfy R-REQ; an Agent can only prepare and route it.

1.6 Cross-links

• decision content mirrors [[one-roof-auth-axis-bootstrap-ratification-rehearsal-go-nogo-2026-06-02]] doc 01.
• ladder + state machine: [[one-roof-axis-auth-proposal-operational-hardening-build-ready-design-2026-06-02]] doc 02.
• live proof R-REQ cannot be agent-satisfied: [[02-live-governance-substrate-analysis]], [[03-legitimate-recording-path-decision]].