09 — Source Adapter Registry & Auto-Scale Guard

Table workflow_discovery_source_registry (16 rows) makes source discovery config-driven: adding a new workflow source is a row insert, not code. Columns: source_name, source_type, source_table_or_path, extraction_rule, object_key_rule, class_rule, relation_rule, enabled, owner, scannable_from_db, adapter_status, observed_count, observed_at, last_scanned_at, last_success_at, error_status, coverage_status, notes.

Health computed by fn_dot_wf_source_adapter_health() → wf_source_adapter_health → views v_workflow_discovery_source_health, v_workflow_discovery_source_missing_adapter.

Adapter status (live)

• LIVE_DB_FN (10): dot_tools, dot_family_pairs, job_queue, event_type_registry, pg_trigger, pg_proc_functions, workflows, approval_requests, dot_iu_command, orphan_components.
• MISSING_ADAPTER (6): host_crontab(49), systemd_timers(21), fs_dot_bin(288), fs_scripts(31), docker_containers(11), kb_sop_docs(UNKNOWN).

Auto-scale guarantee

Future workflow types are not silently missed because: (a) the registry enumerates every known source; (b) fn_dot_wf_source_adapter_health flags any row whose adapter_status≠LIVE_DB_FN as missing_adapter=true; (c) v_workflow_discovery_source_missing_adapter surfaces them to the action panel as REGISTER_SOURCE_ADAPTER items. When a new source class appears, an operator adds a registry row + (if host) a host adapter; the census auto-includes it on next run.

What an adapter must provide (the 6 missing)

• host_crontab / systemd_timers: a host probe that emits counts + per-line classification into the registry/digest (e.g. extend process-discovery-policy-scan.service).
• fs_dot_bin / fs_scripts: an FS walk that reconciles filenames to dot_tools.code/script_path.
• docker_containers: docker ps → service-workflow classification.
• kb_sop_docs: a KB extraction adapter with rules to separate "doc mentions a process" from "doc defines a process" (see 10).