KB-21C5

08 — Discovery Status v4 Views

3 min read Revision 1
dot-runnerv4-viewsdiscovery-status2026-06-04

08 — Discovery Status v4 (Workstream G)

Delivered LIVE: 4 additive read-only views reflecting runner / dry-run state. All derive from DB columns only (generic; no hardcoded candidate facts; filesystem runner facts live in reports, not in SQL).

Views

  1. v_process_discovery_runner_status — per candidate: engine mix (agent_api/hybrid/pg_function/workflow), runner_kind, dryrun_capability. Derived from v_process_discovery_evidence_graph_v2.declared_engine + source_table.
  2. v_process_discovery_dryrun_readiness — runner status + observation markers (fixture_ready, no_execute_tested, sim/dry/real counts) → dryrun_readiness_state.
  3. v_process_discovery_candidate_status_v4 — v3 status + runner columns + candidate_status_v4 ladder.
  4. v_process_discovery_birth_readiness_v4 — v3 birth readiness + runner readiness (does not change birth eligibility).

runner_kind / dryrun_capability (generic mapping)

  • source_table=job_queueexternal_queue_runner / dryrun_runner_exists
  • workflow_engineworkflow_engine / human_in_loop
  • all agent_api → agent_api_only_no_runner / requires_agent_api_contract
  • pg_function only → pg_function_invocable / pg_function_dryrun_possible
  • mixed engines → mixed_engine_partial_runner / requires_agent_api_contract
  • else → engine_unclassified / requires_runner

candidate_status_v4 ladder (runner-aware, verified-safe)

not_a_process → runner_missing → engine_unclassified → fixture_ready → no_execute_tested → dry_run_ready → runner_contract_missing → simulated_observed → dry_run_observed → real_run_observed → verified_candidate → birth_ready. Dry-run/simulated/no-execute never equal verified — v4 inherits the verified computation from v3 (real runtime + cross-component correlation). Confirmed live.

Live snapshot (key rows)

candidate runner_kind dryrun_capability candidate_status_v4 readiness_state
dot:kg mixed_engine_partial_runner requires_agent_api_contract runner_contract_missing blocked_no_runner_contract_fixture_ready
job:cut external_queue_runner dryrun_runner_exists verified_candidate dry_run_runner_available
dot:schema engine_unclassified requires_runner runner_missing runner_or_fixture_missing
wf:WF-001 workflow_engine human_in_loop not_a_process runner_or_fixture_missing

RP/UI can now show runner + dry-run readiness clearly without inflating verification.

Back to Knowledge Hub knowledge/dev/reports/architecture/dot-process-discovery-runner-dryrun-ui-registration-readiness-2026-06-04/08-discovery-status-v4.md