KB-48BD

09 Process Discovery Automation Reality

2 min read Revision 1

09 — Process Discovery Automation Reality (v_rp_process_discovery_automation_reality)

Is process discovery automated or only a one-time view/manual build? Mixed — and now labelled per artifact.

artifact class items last refreshed age
orphan_remediation_queue REAL_AUTOMATION 143 2026-06-05 02:10:50 6.5h
process_candidates MANUAL_ONLY 19 2026-06-04 10:42 21.9h
candidate_members MANUAL_ONLY 143 2026-06-04 10:42 21.9h
residual_evidence_v4 VIEW_ONLY_LIVE 23 (live view)
process_run_observation PARTIAL_EVIDENCE 6
process_component_observation PARTIAL_EVIDENCE 9

Findings

  • Orphan remediation queue IS automated — rebuilt every orchestrator run (143 items: 132 ai-can-handle, 11 owner, 0 birth).
  • Candidate discovery is NOT wired to the orchestrator — wf_process_candidate is a one-time manual build frozen at 06-04 10:42. This is the honest gap: the queue refreshes daily, the candidates do not.
  • residual_v4 (23): 2 AWAITING_OWNER_RECONCILE + 21 resolved (component / not-process / already-managed) — live computed.
  • Runtime evidence is thin (6 runs / 9 components) because REAL_RUN is disabled — labelled PARTIAL_EVIDENCE, not presented as complete.
  • Type-1/2/3 readiness and official RP remain authority-gated (official RP 0).
Back to Knowledge Hub knowledge/dev/reports/architecture/rp-adapter-automation-reality-no-blind-spot-closeout-2026-06-05/09-process-discovery-automation-reality.md