01 — One-Page Human Ratification Checklist

Package: one-roof-human-ratification-handoff-2026-06-02 Audience: the human governance owner, the council, and the President. Print this page. Work top to bottom. Do not skip a box. No Agent may do any of these steps.

---

What you are approving (one sentence)

Adopt the L0–L4 authorization model: make per-step technical build authorization (governance_build_authorization, "SB-0") the build gate, and reserve the e-sign table (os_proposal_approvals) for the President's sovereign sign-off only. (= D-BOOT-1 + D-BOOT-2.)

This is a one-time constitutional act. After it, building the governance substrate becomes possible — one authorized step at a time. It is not reversible by routine process, so it needs both the council (L2) and the President (L4).

---

The five boxes

• BOX 1 — File the request. A human governance owner creates one approval_requests row, code APR-BOOT-AUTHMODEL-1, with action = modify (not add), status = pending, proposed_action_code left blank, and the full decision text in title + proposed_action. → exact fields in doc 03 §A.

• BOX 2 — Council votes (L2). The council records votes on APR-BOOT-AUTHMODEL-1: at least 1 president-human APPROVE, at least 2 ai_council APPROVE, zero rejects, and the person who filed BOX 1 does NOT vote. → exact wording in doc 02 §2; how to enter in doc 03 §B. (When entered correctly, the system moves the request to approved by itself. Do not edit the status field by hand.)

• BOX 3 — President e-signs (L4). The President personally signs the adoption into os_proposal_approvals with a genuine signature and esignature_agreement = true, linked to APR-BOOT-AUTHMODEL-1. → exact wording in doc 02 §3; how to enter in doc 03 §C. (Only the President may do this. No one signs on the President's behalf.)

• BOX 4 — Verify. Run the read-only checks in doc 04. All must pass: the request exists and is approved; the votes satisfy quorum; the President's e-sign exists; and the not-yet-built things are still absent.

• BOX 5 — Release the build (gated). Only after BOX 4 fully passes, trigger the next macro P3 — gated SB-0 build (doc 05). The build agent will itself re-verify and stop if anything is missing.

---

L2 vs L4 — the one distinction that matters

	L2 — Council	L4 — Sovereign
Who	The council (≥1 president-human + ≥2 ai_council)	The President, personally
Surface	apr_approvals votes on APR-BOOT-AUTHMODEL-1	os_proposal_approvals e-sign
Means	Technical/collective ratification of the text	Sovereign e-signature on the adoption
Alone, is it enough?	No — L2 alone does NOT authorize build	No — L4 alone does NOT authorize build
Together	Both L2 quorum and L4 e-sign are required before any build

Hard rules (read before you start)

1. Both L2 (BOX 2) and L4 (BOX 3) are required. Either one alone authorizes nothing.
2. Do not hand-edit approval_requests.status. The quorum machinery moves it.
3. The filer of BOX 1 must not be a voter in BOX 2 (proposer-excluded rule).
4. This act creates only the request + votes + e-sign. It must not create any table, view, action-type, or grant — those come later, inside the gated build, one authorized step at a time.
5. If any box is unclear or any field can't be filled as written, stop and report it — do not improvise.

---

Until all five boxes are complete and doc 04 verification passes live, the build remains NO-GO. This checklist is a plan for humans to execute; nothing on it has been done.

Cross-links: wording [[02-l2-council-and-l4-sovereign-wording]] · Directus steps [[03-directus-manual-action-guide]] · verify [[04-post-human-verification-checklist]] · build gate [[05-next-build-gate-and-prompt]].