KB-360E

03 — Directus / Manual Action Guide for L2 + L4 (step-by-step)

5 min read Revision 1
one-roof-governanceauthratificationdirectus-guidemanual-stepsl2-councill4-sovereign2026-06-02

03 — Directus / Manual Action Guide for L2 + L4

Package: one-roof-human-ratification-handoff-2026-06-02 Step-by-step manual actions for humans in Directus. Written for non-technical execution. No Agent performs any step here. Field names below are the live PostgreSQL column names (verified read-only this run); in the Directus UI they appear as the corresponding fields of each collection.


A. STEP 1 (L2 author) — File the request in approval_requests

Collection: approval_requestsCreate Item. Set these fields exactly:

Field (column) Value to enter
code APR-BOOT-AUTHMODEL-1
request_type constitutional_ratification
title (paste the title from doc 02 §1)
action modifyNOT add (see warning below)
priority high
status pending
proposed_action (paste the JSON from doc 02 §1)
proposed_action_code leave blank / empty
evidence (paste from doc 02 §1)
source governance/bootstrap
review_note (paste from doc 02 §1)

Then Save.

action MUST be modify. If you set add, the system auto-approves it (fn_auto_approve_add, the L0 path) and the council never rules — wrong for a constitutional act. ⚠ proposed_action_code MUST be blank. No live action-type carries build-authorization meaning; do not pick one from the list.

Done when: one approval_requests row exists with code='APR-BOOT-AUTHMODEL-1', action='modify', status='pending'.


B. STEP 2 (L2 council) — Record the votes in apr_approvals

For each voter, in collection apr_approvalsCreate Item, linked to the request above:

Field (column) Value
apr_id the id of the APR-BOOT-AUTHMODEL-1 request
approver the voter's identity (the president-human voter's name must contain "president")
approver_type the voter's type (human for the president-human; ai_council for the AI voters)
decision the system's approve token
rationale (paste the council decision record from doc 02 §2)

You need, in total, on this request:

  • 1 vote: president-human, decision = approve (name matches %president%, human)
  • 1 vote: ai_council member #1, decision = approve
  • 1 vote: ai_council member #2, decision = approve
  • 0 votes: any reject (a single reject blocks the whole act)
  • the proposer (the person who did Step A) casts no vote

The trigger fn_apr_quorum_check fires as votes are saved and, when the rule is met, moves approval_requests.status to approved. Do NOT open the request and change status yourself. approval_requests has no quorum_passed field — "approved" status is the signal that quorum passed.

Done when: the three approve votes exist, no reject exists, and the request's status has flipped to approved on its own.


C. STEP 3 (L4 sovereign) — President e-signs in os_proposal_approvals

The President performs this personally. Collection: os_proposal_approvalsCreate Item:

Field (column) Value
signature_text President's typed full legal name
signature_image President's signature image (optional)
first_name / last_name President's name
email President's email
esignature_agreement true
proposal reference/link to APR-BOOT-AUTHMODEL-1
metadata (paste the sovereign adoption statement from doc 02 §3)
ip_address / date captured automatically — leave to the system

Then Save.

Only the President may do this. No delegate, assistant, or Agent may enter a signature on the President's behalf — that would be e-sign forgery.

Done when: one os_proposal_approvals row exists with esignature_agreement=true, the President's genuine signature fields, and proposal referencing APR-BOOT-AUTHMODEL-1.


D. STEP 4 — Do NOT do anything else manually

After A–C, stop. Do not manually create any table, view, function, apr_action_types row, governance_build_authorization row, or axis object. Those are built later, by the build agent, under per-step authorization — not by hand here. Manual creation would corrupt the gate.

Next: run the verification in doc 04, then release the gated build per doc 05.


E. Quick reference — what each step writes

Step Collection Rows added Who
A approval_requests +1 (APR-BOOT-AUTHMODEL-1) human governance owner
B apr_approvals +3 (1 president-human + 2 ai_council) council
C os_proposal_approvals +1 (sovereign e-sign) President
everything else 0 nobody (build comes later, gated)

Cross-links: wording [[02-l2-council-and-l4-sovereign-wording]] · checklist [[01-one-page-human-checklist]] · verify [[04-post-human-verification-checklist]].

Back to Knowledge Hub knowledge/dev/reports/architecture/one-roof-human-ratification-handoff-2026-06-02/03-directus-manual-action-guide.md