KB-7449

KG/dot-kg Discovery — 08 dot-kg Scoring & Birth-Readiness

5 min read Revision 1
dot-kgscoringbirth-readinessworkstream-g2026-06-04

08 — KG / dot-kg Scoring & Birth-Readiness (Workstream G)

Score of the KG/dot-kg candidate process, from the live engine (v_process_discovery_quality_score / …_birth_ready_queue) + manual review.

8.1 Score

PROC-CAND:dot:kgconfidence 50/100, band strong_candidate_structural, gate BLOCKED_NEEDS_RUNTIME_AND_CORRELATION.

axis weight dot:kg note
start signal 20 18 on-demand producers
end signal 20 18 cron/dual verifiers
cross-component correlation 25 no shared run id across DOTs (dot_iu_command_run.run_id is per-command)
runtime evidence 25 0 executions ever
pairing/structure 10 18 paired
total 50 structure complete, behaviour absent

8.2 Classification

strong_candidate (structural). Not weak (it has a complete, governed, law-backed 36-component structure with explicit producer/verifier pairing). Not verified (zero runtime, zero correlation — it has never run). Not birth_ready (verified is the gate for birth-ready). Definitely not not_a_process (36 members, 18 pairs, 10 processes).

8.3 Blockers (explicit)

blocker present? detail
missing start/end no both present (producers + verifiers)
missing correlation_id YES no cross-DOT process_run_id; highest-leverage gap (doc 06 §6.11)
missing queue/event YES 0 KG events in event_type_registry; producers are event-driven but no events declared
missing runtime evidence YES 0 executions; execution_engine=pg_function declared but no realised run
missing owner YES KG owner not in governance_registry / governance_object_ownership (empty system-wide)
missing IU/SOP partial→resolved was: only one matrix IU. Now D1 (cluster) + D2 (SOP) authored this macro
missing health check no (designed) HEALTH (D, monthly Gold-Standard) is the designed health DOT — but never run
missing governance YES Đ37 owner unregistered; lifecycle/change policy undefined for this family

8.4 The orphan dimension

18 of 36 members are orphaned from the process inventory (ORPHAN_PRODUCER_PAIR_COVERED). Before any birth, the inventory's trigger filter must be widened to include on-demand, or the producer half will be born invisible. This is an engineering fix to a discovery view, not an owner decision — recommended as a fast follow (see doc 09 RP impact).

8.5 Decision: what should dot:kg do?

Stay CANDIDATE; do NOT birth yet; gather runtime + correlation; and SPLIT into 10 process units, not 1.

Reasoning:

  1. Stay candidate / wait for evidence — birthing a 0-runtime process would canonize an unverified, unretirable definition. The law itself gates on runtime (Phase-1 exit needs quality_log + Gold Standard implemented + verified).
  2. Split, don't birth as one — the law defines 10 distinct processes A–J, each with its own trigger, cadence, and producer/verifier set. Modelling dot-kg as a single process is the same granularity error the inventory makes in reverse (it sees 18 singletons; a naive birth would see 1 monolith). The correct unit is the process (A–J) = 18 pairs distributed across 10 processes. Recommended: when birth happens, register 10 Type-1 process units (or 18 pair-units) under one knowledge_graph parent, not one blob.
  3. Sequence to verified: (a) declare KG event types; (b) add process_run_id correlation; (c) enable execution so dot_iu_command_run populates; (d) re-score → verified_candidate; (e) register owner (Đ37); (f) owner admits birth from v_process_discovery_birth_ready_queue.

8.6 Contrast: job:cut is the birth-ready exemplar

PROC-CAND:job:cut scores 90 / verified_candidate / BIRTH_READY_PENDING_OWNER because it has a real completed run with a shared run_id (start cut.request → end cut.complete/cleanup). It is the template for what "verified" looks like — and what dot:kg needs (correlation + runtime) to get there. Its only blocker is owner assignment + the UNBORN workflows row (per prior RP checkpoints).

8.7 Verdict

dot:kg is the strongest structural candidate in the system but is not birth-ready. Keep candidate; build runtime + correlation; split into the 10 law-defined processes at birth; register the KG owner first. The engine will auto-promote it the moment runtime + correlation evidence appears — no re-scoring by hand.

Back to Knowledge Hub knowledge/dev/reports/architecture/kg-dot-process-discovery-and-document-building-pilot-2026-06-04/08-kg-dot-kg-scoring-and-birth-readiness.md