05 — job:cut Registration Owner Packet (Workstream D)

job:cut is the only verified_candidate. Re-verified live this run. Pushed to final actionable state. No birth, no canon, no approval row inserted.

Live evidence (this run)

• verified_candidates_v3: PROC-CAND:job:cut · kind=job · 8 members · verified_candidate · birth_gate_status_v3=VERIFIED_PENDING_OWNER · has_cross_component_correlation=true · owner_missing=true.
• closeout_status: verified_candidates=1.
• 8 members (job_queue): cut.request, cut.copy_to_staging, cut.cut, cut.mark, cut.verify_cut, cut.verify_mark, cut.complete, cut.cleanup_checkpoint.
• Runtime basis: real Mode.DRYRUN runner (iu-cutter-v0.6, 366/366) + o7 sidecar; real run rows correlated by job_queue.run_id (not backfill).

Final registration packet

1. Process definition candidate — job:cut: an 8-step external-queue job process; components correlated by job_queue.run_id; runtime verified by correlated real-run rows.
2. Members — the 8 steps above, as ordered declared steps of one process definition.
3. Evidence — verified_candidate via existing verified_candidates_v3 logic (never hand-set); correlation true; this is a single job process, NOT the dot:kg 10-def split.
4. Owner requirement — gov_object_ownership has no row (owner_missing=true). Needs an owner-of-record (Điều 37) before birth admission.
5. Birth admission plan — one process definition with 8 declared steps; gate VERIFIED_PENDING_OWNER.
6. Governance handoff — owner ratifies → birth admission → optional process.* activation (separate, owner-gated).
7. RP / AX-PROCESS effect — already surfaced as verified in v3→v6→v7; UI badge correct; no recompute.
8. Rollback caveat — birth is unretirable; approval_requests inserts are unretirable births; trg_apr_auto_approve auto-approves action='add' → any request MUST use action='review'.

Why no DRAFT/PENDING row was inserted this run

• Every approval_requests insert is an unretirable birth (would change the birth count).
• gov_object_ownership.lifecycle_status has no 'draft' → cannot pre-stage ownership without committing it.
• Therefore this stays a KB packet. The owner/operator files the review-action request and the ownership row. No fake approval, no fabricated owner. (This matches the safety posture; the macro permits DRAFT/PENDING packets but here the schema makes any insert a real birth.)

Exact owner/operator actions (handoff, not executed)

1. Owner: insert the gov_object_ownership row for PROC-CAND:job:cut (Điều 37).
2. Operator: insert the registration approval_requests row with action='review' (NOT 'add'), proposed_action_code='register_process'.
3. After approval: birth admission of the single job process definition (8 steps).

Completion

job:cut can be registered after the owner decision without rediscovery. No engineering blocker remains.