KB-5B5C

Owner / President Decision Manual — PROC-OWN-01..05

3 min read Revision 1
process-axisownerpresidentproc-own2026-06-04

Owner / President Decision Manual — PROC-OWN-01..05

2026-06-04 · for the human president / governance council. Five decisions unlock everything.

Why you are reading this

Every engineering branch of the Process Axis is complete and fail-closed. Nothing further can happen without your authority. Five approval_requests rows (PROC-OWN-01..05, all pending, action='review') are waiting. Casting a real approve vote (recorded in apr_approvals with approver_type='human', approver containing 'president') is the only key.

The five decisions

Code request_type Decision Post-vote handler Effect
PROC-OWN-01 axis_ownership Assign an owner to the AX-PROCESS axis fn_pa_handler_assign_axis_owner Writes governance_object_ownership(axis:AX-PROCESS). Unlocks all canon steps.
PROC-OWN-02 axis_canon Canon AX-PROCESS (CANDIDATE→ACTIVE) fn_pa_handler_register_axis axis_registry status=ACTIVE, approval_ref set.
PROC-OWN-03 process_registration Register job:cut as first official process (verified, 8 members) fn_pa_handler_register_process axis_assignment(AX-PROCESS, job:cut, approval_ref=PROC-OWN-03) → first official RP.
PROC-OWN-04 process_family_registration dot:kg family owner + authorize 10-process split (only after a successful REAL_RUN) fn_pa_handler_assign_governance_owner Owner for dot:kg family; gates the split.
PROC-OWN-05 event_activation Activate 7 process.* event types fn_pa_handler_activate_event_type event_type_registry.active=true for 7 rows.

Dependency order

PROC-OWN-01 must precede 02/03/05 (the handlers refuse canon until axis ownership exists — needs_axis_owner_first=true). PROC-OWN-04 additionally requires a real dot:kg REAL_RUN first.

How to vote (mechanically)

A vote is an INSERT into apr_approvals(apr_id, approver, approver_type='human', decision='approve', rationale) against the PROC-OWN row's id, by a human president. The guarded handlers then move from BLOCKED_NO_PRESIDENT_VOTE to READY_PREVIEW automatically (see v_process_axis_post_vote_handler_readiness). The actual canon write remains a deliberate, separately-run governance step — handlers never auto-write canon.

What you are NOT being asked to approve

You are not approving any agent-fabricated state. Ownership=0, delegation=0, president votes=0 today — nothing has been pre-decided on your behalf. Each vote is yours, fully reversible until the canon step is run.

Approve PROC-OWN-01 (assign AX-PROCESS owner — suggest GOV-COUNCIL per governance_responsibility_scope.policy). That single vote unblocks the entire chain to job:cut.