Registries-Pivot · Process Axis — Operator Guide

Audience: process owners, council members, operators. Companion to the 2026-06-04 owner-gate closeout.

The one number that matters

Official AX-PROCESS RP = 0/453. A process is governed only when it carries an axis_assignment on the canon AX-PROCESS axis. Today none do. Everything else (candidate lists, 373 DB defs, 69 candidate-visible) is staging, not governance.

Reading the Process Axis screen

• Official vs Candidate — official = 0/453 (canon); candidate_visible = 69/143 (listable, not governed). Don't confuse them.
• Candidate list / detail / graph — the 19 process candidates and their member objects.
• Owner gate queue / Birth request queue — what needs an owner or a president vote.
• Residual — orphan objects, now hardened to 2 genuine owner-reconcile items.
• Action panel — buttons, not checkboxes. Every button previews first.

Why some buttons are locked (FAIL_CLOSED)

The action handler is fail-closed by construction:

• Assign owner / Reconcile → locked until an owner exists (today 0).
• Create birth request / Send to governance → locked until a real human president approve vote is recorded. An AI agent can never satisfy this; a human without a recorded vote also can't. Locked is the correct, safe state — not a bug.

The owner/president decisions (in order)

1. PROC-OWN-01 — assign AX-PROCESS owner (reversible)
2. PROC-OWN-02 — make AX-PROCESS canon (irreversible; this flips official RP)
3. PROC-OWN-03 — birth job:cut (first official process)
4. PROC-OWN-04 — birth dot:kg only after REAL_RUN evidence
5. PROC-OWN-05 — activate process.* events (reversible)

Rule of thumb: vote 01 before 02; never vote 04 before dot:kg has real REAL_RUN observations.

What's safe to click today

Request more evidence, Mark not-process, Accept OS-level, Quarantine, Confirm candidate (triage), Merge, Split — all preview-only, reversible, no canon/birth effect.