KB-70E6

04 Owner/President Decision Flow

4 min read Revision 1

04 · Owner / President Decision Flow (Phase C)

Source: v_process_axis_owner_decision_flow (12 rows). The 5 PROC-OWN rows exist as approval_requests with action='review', status='pending' — already action-ready and guarded (auto-approve fires only on action='add', never on 'review'). No new approval_requests were created (each insert is an irreversible birth). Ownership stays 0; nothing was approved.

President-vote decisions (actor: PRESIDENT + AI_COUNCIL_QUORUM)

id subject type reversibility flips official RP state agent can execute?
PROC-OWN-01 AX-PROCESS axis_ownership REVERSIBLE YES pending NO — president vote
PROC-OWN-02 AX-PROCESS axis_canon IRREVERSIBLE_BIRTH YES pending NO — president vote
PROC-OWN-03 PROC-CAND:job:cut process_registration IRREVERSIBLE_BIRTH no pending NO — president vote
PROC-OWN-04 PROC-CAND:dot:kg process_family_registration IRREVERSIBLE_BIRTH no pending NO — president vote (also needs REAL_RUN evidence first)
PROC-OWN-05 process.* event_activation REVERSIBLE no pending NO — president vote

Owner decisions (actor: PROCESS_OWNER)

id subject state agent can execute?
WPC-APPROVAL-LIFECYCLE Approval Lifecycle Automation (DB) UNASSIGNED NO — owner assign then confirm
WPC-BACKUP-DR Backup & Disaster Recovery UNASSIGNED NO
WPC-CONTENT-PUBLISH Content Publish & CDN Sync UNASSIGNED NO
WPC-HEALTH-MON Platform Health Monitoring UNASSIGNED NO
WPC-PERM-GUARD Permission & Config Integrity Guard UNASSIGNED NO
WPC-RECONCILE Data Reconciliation (Tasks & Knowledge) UNASSIGNED NO
WPC-DOCKER-RUNTIME Docker runtime services (11 containers) AWAITING_OWNER NO

Per-decision: what each unlocks + exact guarded action

  • PROC-OWN-01 (owner) → enables AX-PROCESS to receive an owner; guarded action when authority arrives: a real human president approve vote on apr PROC-OWN-01, then governed assign_axis_owner handler (currently unimplemented → blocked).
  • PROC-OWN-02 (canon, IRREVERSIBLE) → registers AX-PROCESS axis as canon; this is the single decision that flips official RP from 0 once axis_assignments are then created.
  • PROC-OWN-03 → births job:cut as the first official process (sole VERIFIED candidate).
  • PROC-OWN-04 → births the dot:kg process family — gated additionally on REAL_RUN evidence (today 0); do not vote before the REAL_RUN ladder (doc 08).
  • PROC-OWN-05 → activates the 7 process.* event types (currently 0/7 active); reversible.
  • WPC-*: owner assigns ownership, then CONFIRM_PROCESS_CANDIDATE becomes meaningful for the 6 PROCESS_CANDIDATE clusters; docker-runtime owner decides which of 11 containers are managed processes.

What the agent did here (safe)

  • Verified all 12 decisions are action-ready and correctly classified.
  • Implemented the guarded handler that will execute these only once real authority exists (doc 02) — every path proven fail-closed today.
  • Did not create ownership, votes, or new approval rows.

Blocker

Authority only: PRESIDENT + AI_COUNCIL_QUORUM votes (PROC-OWN-01..05) and PROCESS_OWNER assignments (7 owner decisions). No engineering blocker.

Back to Knowledge Hub knowledge/dev/reports/architecture/rp-process-axis-owner-gate-handler-ui-content-dotkg-closeout-2026-06-04/04-owner-president-decision-flow.md