KB-6417

03 — Owner / Governance Drain (2026-06-04)

4 min read Revision 1

03 — Owner / Governance Drain

Outcome: drained to a single action-ready operational surface — v_process_axis_owner_decision_flow (12 rows). No fake approval. No new births.

Rather than create new birth-bearing approval_requests (each insert = 1 unretirable birth, and the candidate-level requests are out-of-sequence until the axis is canon), the drain is delivered as a birth-free decision-flow view that joins every pending decision into one list with required actor, reversibility, whether it flips official RP, and recommended action.

The 12 decisions

President-vote-gated (5) — already-existing APRs PROC-OWN-01..05 (status=pending, action='review')

Decision Subject Type Reversibility Flips official RP? Recommended
PROC-OWN-01 AX-PROCESS axis_ownership REVERSIBLE YES Open APR for president vote (assign axis owner)
PROC-OWN-02 AX-PROCESS axis_canon IRREVERSIBLE_BIRTH YES President vote: CANDIDATE→ACTIVE + canon
PROC-OWN-03 PROC-CAND:job:cut process_registration IRREVERSIBLE_BIRTH no President vote: register job:cut (sole verified, 8 members)
PROC-OWN-04 PROC-CAND:dot:kg process_family_registration IRREVERSIBLE_BIRTH no Hold — dot:kg not verified (real_run 0); see doc 07
PROC-OWN-05 process.* event_activation REVERSIBLE no President vote: activate 7 process.* events

Owner-gated (7) — READY_FOR_OWNER

Decision Subject Required actor Recommended
WPC-BACKUP-DR Backup/DR process candidate PROCESS_OWNER Assign owner → CONFIRM_PROCESS_CANDIDATE
WPC-PERM-GUARD Permission-guard candidate PROCESS_OWNER Assign owner → confirm
WPC-RECONCILE Reconcile candidate PROCESS_OWNER Assign owner → confirm
WPC-HEALTH-MON Health-monitoring candidate PROCESS_OWNER Assign owner → confirm
WPC-CONTENT-PUBLISH Content-publish candidate PROCESS_OWNER Assign owner → confirm
WPC-APPROVAL-LIFECYCLE Approval-lifecycle candidate PROCESS_OWNER Assign owner → confirm
WPC-DOCKER-RUNTIME 11 docker runtime services PROCESS_OWNER Assign owner (residual cluster)

Why no new approval_requests were created

  • approval_requests carries trg_birth_approval_requests → every insert is an irreversible birth.
  • The 6 candidate births cannot precede axis canon (PROC-OWN-02) and owner assignment (PROC-OWN-01); creating them now would burn births out of sequence.
  • Correct sequence (the EXACT BLOCKER): owner assigns owners → confirm → president-gated birth (+1 each) → governance canon → AX-PROCESS axis_assignment (the only step that flips official RP > 0).

Quorum model (live triggers)

trg_apr_quorum_check + trg_apr_block_unimplemented: high-risk/canon APRs require ≥1 human president + ≥2 ai_council; AI can never cast the president vote; and even an approved APR cannot execute while its handler is unimplemented (fail-closed). This is why the drain stops at "ready for vote" and does not — cannot — self-approve.

Drain status: COMPLETE (action-ready). Blocker = human president vote + process owner assignment. No engineering ambiguity remains.

Back to Knowledge Hub knowledge/dev/reports/architecture/registries-pivot-process-coverage-ui-owner-canon-content-closeout-2026-06-04/03-owner-governance-drain.md