07 — job:cut Registration Candidate Prep (Workstream F)

job:cut is the only verified_candidate. Pushed as far as safe; no birth, no canon, no approval.

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 (source job_queue.run_id), owner_missing=true.
• birth_readiness_v6: verified_pending_owner. auto_workflow_policy_gaps: gap_no_owner → "assign governance owner, then birth".
• 8 members: cut.request, cut.copy_to_staging, cut.cut, cut.mark, cut.verify_cut, cut.verify_mark, cut.complete, cut.cleanup_checkpoint (all job_queue).
• Runner: real Mode.DRYRUN runner proven (iu-cutter-v0.6, 366/366) + o7 sidecar; real run rows correlated by run_id (not backfill).

Registration-readiness packet (DRAFT)

1. Process definition candidate — job:cut: an 8-step external-queue job process, components correlated by job_queue.run_id, runtime verified by real run rows.
2. Owner requirement — gov_object_ownership has no row for it (owner_missing=true). Needs an owner-of-record (Điều 37) before birth admission.
3. Birth admission packet — gate = VERIFIED_PENDING_OWNER. job:cut is a single job process (not the 10-def split that applies to dot:kg). Birth = one process definition with 8 declared steps.
4. Governance handoff — owner ratifies → birth admission → optional process.* activation (separate, owner-gated).
5. RP pivot impact — already surfaced as verified in v3→v6; UI badge correct; no recomputation needed.

Why NO approval/owner row was inserted (safety)

• trg_apr_auto_approve auto-approves approval_requests.action='add' on insert → any request must use action='review'.
• Each approval_requests insert is an unretirable birth.
• 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.

Exact owner action (for handoff, not executed)

-- 1) ownership (owner-run): INSERT gov_object_ownership row for PROC-CAND:job:cut (Điều 37)
-- 2) registration request (operator-run, action='review' NOT 'add'):
--    INSERT approval_requests (... proposed_action_code='register_process', action='review' ...)
-- 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.