04 — job:cut Registration Candidate (Workstream C)

Re-verified (live)

v_process_discovery_verified_candidates_v3: PROC-CAND:job:cut · kind=job · member_count=8 · candidate_status_v3=verified_candidate · has_cross_component_correlation=true · birth_gate_status_v3=VERIFIED_PENDING_OWNER · owner_missing=true. Policy gap: gap_no_owner → "assign governance owner, then birth". It remains the only member of the verified set.

Decision: FINAL packet — NO approval row inserted (deliberate)

Why not insert a pending request this run:

1. approval_requests INSERT triggers an unretirable birth_registry row; the owner has not decided, so a premature birth is not reversible.
2. No clean action vocab exists for "birth/register a process candidate": apr_action_types has register_axis/register_topic_node/assign_*_owner/amend_law/create_item/etc., none = "register process". Forcing create_item would misrepresent the act.
3. governance_object_ownership is empty system-wide — there is no owner to assign yet; the real gate is the owner decision + governance roots, not a queue row.
4. trg_apr_auto_approve auto-approves action='add'; any insert must use action='review' — but see (1)–(3).

This matches every prior run's deliberate choice and is "as far as safe."

Exact owner action to move forward (one of)

• (a) Assign owner first (recommended): owner approves assign_governance_owner for object PROC-CAND:job:cut (scope: cut pipeline), then a process_improvement registration. Ownership insert is the legitimate first governed write.
• (b) Birth process: with owner authorization, insert the job:cut process definition (10-step or single per owner's model) — this IS an irreversible birth and is owner-gated.

RP / PIV impact (PIV-340..353)

Birthing job:cut as a Type-2 automated process flips counts: PIV-340 (total governed) +1, PIV-342 (Type-2 automated) from candidate→counted, and the PIPELINE:cut governance-gap row clears unborn. These remain CANDIDATE classification until the owner ratifies the AX-PROCESS pivots (doc 06).

Rollback caveat

A birth cannot be retired. Everything up to the birth (ownership assignment via approval flow) is reversible only by the governance retire path; the birth itself is permanent. Hence held for owner.

Completion: job:cut needs no further engineering rediscovery; one owner decision remains.