08 — Owner / Governance / Birth Queue

The official transition path is prepared as queues, not executed. No approval_requests rows were written (each insert = 1 unretirable birth, and would constitute an owner action) — so the queues are action-ready VIEWS, fully birth-free.

Owner gate queue — v_process_axis_owner_gate_queue (7 rows)

Candidates needing a governance owner before any official path: the 6 PROCESS_CANDIDATE (WPC-BACKUP-DR, PERM-GUARD, RECONCILE, HEALTH-MON, CONTENT-PUBLISH, APPROVAL-LIFECYCLE) + WPC-DOCKER-RUNTIME (NEEDS_OWNER). Gate: "human president/governance owner required."

Birth request queue — v_process_axis_birth_request_queue (6 rows)

The 6 PROCESS_CANDIDATE that passed AI review (AI_REVIEWED_PASS). Each carries birth_caveat = "BLOCKED: requires owner + president + governance canon; 1 birth on registration" and request_state = NOT_REQUESTED. These are the candidates an owner could promote to official birth — one birth each — once they assign an owner and a president votes.

Why nothing was inserted

• approval_requests insert → birth (proven in prior phases: PROC-OWN rows = +5 births). This macro is birth-free by mandate.
• Owner approval, president vote, governance canon, event activation = all forbidden / owner-gated.
• Per operating authority §2: "If true owner/governance authority is required, do not fake it. Create action-ready packets/states and continue." → done as queues.

Exact official-transition recipe (for the owner, when ready)

1. Assign owner to a candidate (Assign Owner action; owner-gated).
2. AI review already PASS → operator confirms candidate (Confirm Process Candidate).
3. Create Birth Request (president-gated; +1 birth) → approval_requests row, action='review' (NOT 'add', so no auto-apply).
4. President vote + governance canon → official AX-PROCESS axis_assignment (the only step that flips official RP > 0).