job:cut Officialization Playbook

2026-06-04. The first official AX-PROCESS process, step by step.

Why job:cut first

It is the sole verified candidate: PROC-CAND:job:cut, 8 members, cross-component correlated, VERIFIED_PENDING_OWNER. iu-cutter v0.6 runs in Mode.DRYRUN (read-only + killswitch + 366 tests).

Preconditions (all met except authority)

• Verified evidence ✓ · 8 members ✓ · cross-component correlation ✓ · REAL_RUN not required for officialization (it is a governance registration, not a runtime act).
• Missing: AX-PROCESS owner + president votes.

Steps (human-president, in order)

1. PROC-OWN-01 approve → assign AX-PROCESS owner (governance_object_ownership).
2. PROC-OWN-02 approve → canon AX-PROCESS axis (axis_registry id 4 → ACTIVE).
3. PROC-OWN-03 approve → register job:cut (INSERT axis_assignment(AX-PROCESS, job:cut)). → Official AX-PROCESS RP coverage 0 → 1.

Effects

• 1 axis_assignment row (not birth-tracked → no species birth, no trigger fan-out).
• No new approval_requests (the 5 PROC-OWN rows already exist).
• RP "official vs candidate" panel shows the first official process; verified badge from v3.

Rollback caveat

Reversing canon is itself a governance act (DELETE the axis_assignment row + revert axis_registry status). The 5 PROC-OWN approval rows are unretirable births — never delete or re-create them.

Verification after the vote

SELECT * FROM v_rp_process_canon_gate_summary WHERE metric='official_ax_process_rp_assigned'; should read value=1.