KB-6425

KG/dot-kg Discovery — 10 Next Macro Decision

3 min read Revision 1
next-macrodecisionworkstream-i2026-06-04

10 — Next Macro Decision (Workstream I)

Candidates

  1. PROCESS_DISCOVERY_ENGINE_READONLY_APPLY_AND_DOT_KG_SCORE
  2. INFORMATION_PIECE_DOCUMENT_BUILDING_D1_D2_EXPAND
  3. DOT_KG_PROCESS_REGISTRATION_CANDIDATE_PREP
  4. RP_UI_TOPIC_PROCESS_DISCOVERY_DEPLOY
  5. PROCESS_DISCOVERY_CORRELATION_ID_AND_RUN_ID_DESIGN

Applying the decision rule

  • "if D1/D2 are strong and discovery views are live → choose expansion or UI deploy." — D1/D2 are published, views are live. ✓ (supports #2/#4)
  • "if dot-kg lacks correlation/start/end → choose correlation/run-id design." — dot:kg has start+end but lacks correlation (and runtime). ✓ (supports #5)
  • "if birth-ready → choose registration candidate prep." — dot:kg is not birth-ready; only job:cut is. (partial support for #3, but for cut not kg)
  • "do not choose approval-only." — none chosen is approval-only. ✓
  • #1 is already substantially done this macro (views applied + dot-kg scored) → not the next step.

Decision: #5 PROCESS_DISCOVERY_CORRELATION_ID_AND_RUN_ID_DESIGN (primary)

Why: every DOT family — KG included — is blocked at the same wall: BLOCKED_NEEDS_RUNTIME_AND_CORRELATION. Start/end structure is already complete; the binding constraint on the whole discovery→verify→birth pipeline is the absence of a cross-component process_run_id/correlation_id. It is the single highest-leverage change (doc 06 §6.11, doc 08 §8.5): it converts every structurally-strong candidate toward verified_candidate the moment processes start correlating their DOT runs. The decision rule names this case explicitly.

Scope of #5: design process_run_id (uuid) on dot_iu_command_run; a correlation_id event convention; the process_discovery_baseline table (drift); how a process orchestrates multiple DOTs under one run id; reconcile with job_queue.run_id (the working exemplar) and Điều 45 Queue Law. Design + apply-packet; owner-gated for the schema change.

Parallel (owner/operator-gated)

  • #4 RP_UI_TOPIC_PROCESS_DISCOVERY_DEPLOY — deploy the 6 routes + 5 components on the live views; fix the inventory trigger filter (operator).
  • #2 INFORMATION_PIECE_DOCUMENT_BUILDING_D1_D2_EXPAND — author the 14 KG config-table reference + per-DOT specs; expand D1/D2 (owner-free, authoring).
  • #3 DOT_KG_PROCESS_REGISTRATION_CANDIDATE_PREP — but for job:cut (the only birth-ready candidate), not dot:kg; prep its MOW registration (owner-gated).

Not chosen

  • #1 — done this macro.
  • #3-for-dot:kg — premature (not birth-ready; needs #5 first).
Back to Knowledge Hub knowledge/dev/reports/architecture/kg-dot-process-discovery-and-document-building-pilot-2026-06-04/10-next-macro-decision.md