06 — Workflow Orphan / Unmanaged Detector

Built by fn_dot_wf_orphan_detector() → wf_orphan_digest → views:

• v_workflow_orphan_components (summary by kind)
• v_workflow_unmanaged_process_clusters (host_scheduler / fs_executors / document_defined_sops)
• v_workflow_rp_missing_processes (enumerates 311 = 309 DOT + 2 wf with no AX-PROCESS assignment)
• v_workflow_phantom_process_candidates (AX-PROCESS assignment with no source object — currently 0)

Orphan signal (live)

Orphan kind	Count	Severity
user_trigger_unmodelled	410	low (components; FP-risk control applied)
host_source_unmanaged	400	high
rp_missing_all_definitions	311	high
dot_without_process_candidate	178	medium
queue_run_without_candidate	7	medium
event_type_no_candidate	7	medium
phantom_axis_process	0	high (clean)

Existing discovery's v_process_discovery_orphan_components = 84 (component-level) is retained and cross-referenced.

Interpretation

The dominant orphan driver is RP-missing (311) + host-unmanaged (400) — i.e. things exist and run but are not surfaced/governed on the process axis. phantom=0 confirms no fabricated assignments.