Phase 13 — v_rp_candidate_discovery_wiring_plan

aspect	detail	status	next action
source_views	wf_orphan_remediation_queue (143) + process_run_observation + process_component_observation	present	—
builder_handler	NONE — no fn builds wf_process_candidate (only audit-only fn_wf_candidate_action_execute touches it); 19 candidates were a one-time manual build	MISSING	owner authors fn_dot_wf_build_candidates()
schedule	add builder call to wf_scan_orchestrator.sh after the remediation queue step	possible	engineering once builder exists
output	wf_process_candidate rows (pre-birth, governance-visible)	—	owner approves: these are governance-visible writes
risk	candidate creation is pre-birth but RP-visible → not a silent eng write	MEDIUM	owner authority
blocker	OWNER must author + sanction the builder fn before wiring	OWNER_BLOCKED	owner

Conclusion: wiring candidate discovery into the (now provenance-correct) orchestrator is mechanically simple, but the missing piece is an owner-authored builder function that creates governance-visible candidate rows. That is owner-gated, not an engineering-only change — so it is NOT actuated this macro.