job:cut — First Official Process Playbook

2026-06-04 · the cleanest path to the organisation's first official governed process.

Why job:cut goes first

job:cut (iu-cutter-v0.6) is the sole VERIFIED candidate: a true Mode.DRYRUN runner with read-only + killswitch + 366 tests. It has 8 members, recommendation CONFIRM_AS_PROCESS, and is already AI-reviewed. It is the lowest-risk, highest-evidence process to canonise first.

Current state (live, 2026-06-04)

• Verified, 8 members. canon_gate_status candidate-stage.
• Owner: UNASSIGNED. Birth: NOT_REQUESTED. Official RP: 0.
• Birth path proven fail-closed today: fn_pa_handler_register_process('actor','human') returns BLOCKED — no human-president approve vote on PROC-OWN-03.

The path to official (post-vote)

1. PROC-OWN-01 approved → AX-PROCESS owner recorded (governance_object_ownership).
2. PROC-OWN-02 approved → AX-PROCESS axis canon ACTIVE.
3. PROC-OWN-03 approved (human president approve vote) → v_process_axis_post_vote_handler_readiness flips PROC-OWN-03 to READY_PREVIEW.
4. Governance runs the deliberate canon step: INSERT axis_assignment(axis_code='AX-PROCESS', target_type='process', target_code='job:cut', approval_ref='PROC-OWN-03', status='active').
5. Official AX-PROCESS RP becomes 1/453 — first official process.

Safety properties

• No birth occurs without the vote (admission is birth-trigger gated).
• The handler computes the exact write but never fires it — a human runs the canon step.
• Fully reversible until the canon row is committed.

Verification after officialization

• SELECT count(*) FROM axis_assignment WHERE axis_code='AX-PROCESS' AND approval_ref IS NOT NULL → expect 1.
• v_rp_process_canon_gate_summary verdict should move off CANON_BLOCKED_OWNER_ONLY for job:cut.
• Birth registry should grow by exactly the admission rows (audit them).

Do not

Do not register job:cut by directly inserting axis_assignment without the PROC-OWN-03 vote — that would be a faked official RP. The whole point is that the vote is the authority.