KB-298B
01 — Ratification Decision Record (the ONE gate; decision-only, NOT enacted)
5 min read Revision 1
one-roof-governanceauthaxisratificationdecision-recordnot-enactedl2-l4go-nogo2026-06-02
01 — Ratification Decision Record (the ONE gate; decision-only, NOT enacted)
Package:
one-roof-auth-axis-bootstrap-ratification-rehearsal-go-nogo-2026-06-02Mode: decision record only · writes no approval/e-sign row · NOT enacted Authority model source: hardening doc 02 (state machine) + doc 13 (readiness matrix).
1.1 The decision under ratification
Adopt the authorization model that redefines M-1 and introduces the L0–L4 ladder:
- M-1 redefinition — the master commit key moves from "one
os_proposal_approvalsrow exists" (a sales e-signature surface) to a per-stepgovernance_build_authorizationgrant (SB-0) whose validity is recomputed from the backing L2 quorum and (where required) an L4 sovereign e-sign.os_proposal_approvalsis reserved for the L4 branch only. - L0–L4 ladder (doc 02):
- L0 — low-risk allowlisted reversible action (auto-approved
create_item-class). - L1 — single non-proposer approver.
- 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). - L3 — a valid
governance_build_authorizationgrant issued by someone other than the consuming agent (INV-5). - L4 — a sovereign e-signature for constitutionally-reserved acts (e.g. any
birth_registrytruth write or lawstatuschange).
- L0 — low-risk allowlisted reversible action (auto-approved
1.2 Why this is a constitutional bootstrap, not an engineering task
SB-0 is the first build step but cannot self-authorize: authorizing the authorization model is circular. The model can only be adopted by a one-time L2 council + L4 sovereign ratification — a constitutional act. The new model explicitly cannot remove from the President the single act of e-signing its own adoption. This is a decision dependency, not an engineering gap.
1.3 Live gate state at decision time (read-only, 2026-06-02)
| Surface | Value | Meaning |
|---|---|---|
os_proposal_approvals |
0 | L4 sovereign e-sign gate UNSATISFIED ⇒ COMMIT_FORBIDDEN |
governance_build_authorization (SB-0) |
ABSENT | no L3 substrate exists yet |
| council/sovereign ratification record | none | model not adopted |
approval_requests / apr_approvals / apr_action_types |
211 / 42 / 6 | live spine intact; SB-1 governance action-types genuinely unbuilt |
1.4 Ratification status: READY_NOT_ENACTED
- Design: build-ready (hardening docs 02/03/05/11/13).
- Rehearsal: REHEARSED-GREEN LIVE as of this package (docs 03/04/05) — the substrate compiles and the verifier behaves, raising confidence that if ratified, the build is mechanically sound.
- Enactment: not done. There is no enactment path an agent can satisfy — L4 is a human sovereign e-signature into
os_proposal_approvals(or its target governance collection) performed out-of-band in Directus; L2 is a recorded council decision. Silence ≠ approval. This record creates no approval row and is not itself an authorization.
1.5 What a legitimate enactment requires (for the human/council, out-of-band)
- L2 council ratification — a recorded council decision adopting the M-1 redefinition + L0–L4 ladder (the eight governance action-types of hardening doc 03 §3.3 authored under one L2 approval,
action='review'). - L4 sovereign e-sign — the President e-signs the adoption into
os_proposal_approvals(interim) /governance_sovereign_esign(target, doc 12 P3), populating signature fields +esignature_agreement=true. - Only then does the first
governance_build_authorizationgrant for SB-0 become issuable, and the build order proceeds (doc 07 §7.4).
1.6 Cross-links
- decision implements [[one-roof-axis-auth-proposal-operational-hardening-build-ready-design-2026-06-02]] doc 02 §2.7 / doc 13.
- gate evidence in [[02-live-preflight-baseline]]; rehearsal evidence in [[03-sb0-authorization-rehearsal-results]].
- No enactment performed. Build remains NO-GO (doc 07).