11 — Final Summary

Macro: KG_DOT_PROCESS_DISCOVERY_AND_DOCUMENT_BUILDING_PILOT · Date: 2026-06-04 · Mode: EXECUTION_MODE · Status: PARTIAL (both branches delivered; owner/operator decisions remain).

What was asked

Move KG/dot-kg from "identified pilot" to "real document output and a Process Discovery Engine pilot design backed by live evidence." Complete both branches; don't stop after one.

What was delivered

A. Content / document output

• D1 — knowledge/dev/design/knowledge-graph/d1-knowledge-graph-curated-cluster-2026-06-04.md (published, read-back PASS).
• D2 — knowledge/dev/sop/dot-kg/d2-dot-kg-process-family-sop-runbook-2026-06-04.md (published, read-back PASS).
• KG content cluster map (16 IUs, doc 02); dot-kg evidence graph (36 DOTs, doc 04); document backlog advanced (D1/D2 done, config-table ref + per-DOT specs queued).

B. Process discovery output

• Evidence graph for all 36 dot-kg DOTs (doc 04) + component graph + start/end/orphan analysis.
• Process Discovery Engine v1 generic design — 9-stage lifecycle, correlation design, Hermes-fit, automate-vs-review (doc 06).
• 6 live read-only discovery views scoring 17 candidates system-wide (doc 07).
• dot-kg scored + birth-readiness explicit (doc 08); RP/UI impact (doc 09); next macro (doc 10).

The decisive findings (live-evidence-wins)

1. 36 DOTs, not 18. Every prior report said "18 dot-kg DOTs"; live + law say 36 = 18 producer/verifier pairs. The "18" was the pair count mis-read as a DOT count.
2. The orphan. v_axis_process_inventory counts exactly the 18 verifier (Cấp A, cron/dual) DOTs and silently drops the 18 producer (Cấp B, on-demand) DOTs — the process axis shows half the KG automation. Surfaced live in v_process_discovery_orphan_components.
3. Zero runtime, system-wide. 103 DOT_* DOTs, 0 ever executed. No DOT process can be "verified" today — the entire automation layer is declared-but-never-run. The engine scores honestly: dot:kg = strong_candidate_structural (50), only job:cut = verified_candidate (90, from a real completed run).
4. The binding constraint = correlation. DOT runs have no cross-DOT process_run_id; job_queue.run_id is why cut is verified and dots are not. Closing this is the next macro.

Live mutation

6 additive read-only views — 0 PG-schema births (birth_registry 1,158,132 before == after == post-commit; rehearsed BEGIN/ROLLBACK net-zero; independent MCP read-back PASS). Disclosed side-effect: publishing the 16 KB documents created 16 knowledge_documents provenance births (species ai_support) + auto-managed entity_labels via the normal KB→Directus ingestion path (counter → ~1,158,148) — document provenance, not process/taxonomy/approval births. 0 process born, 0 taxonomy node, 0 approval approved, 0 IU edited, 0 source tag deleted, 0 DOT executed, 0 workflow run, 0 promotion. Rollback: 6 × DROP VIEW (/tmp/process_discovery_views_rollback.sql).

Live numbers (2026-06-04)

births 1,158,132 · AX-PROCESS/AX-TOPIC CANDIDATE · FAC-08 nodes 0 · DOT_KG_* 36 (18 on-demand producers / 18 cron+dual verifiers, 0 executed) · KG IUs 16 (knowledge_graph topic tags 10) · IU 10649925 = #7-36-dot-kg bridge · process inventory 60 (KG=18 verifiers only) · discovery views 6 (evidence 113 / candidates 17 / orphans 84) · job_queue 13 (cut.*, 1 verified run) · KG events 0 · DOT runtime 0/103.

Compliance

No forbidden action: no DOT executed, no active/born process, no AX-PROCESS activation, no approval approved, no IU body edit, no source-tag delete, no broad birth/governance change, no dot-pivot-update registration, no hardcoding (engine generalises to 14 DOT families + jobs + workflows), no "verified" claim without runtime+correlation evidence. Both branches completed.

Next

Primary: PROCESS_DISCOVERY_CORRELATION_ID_AND_RUN_ID_DESIGN (close the binding constraint). Parallel (owner/operator): RP_UI_TOPIC_PROCESS_DISCOVERY_DEPLOY · INFORMATION_PIECE_DOCUMENT_BUILDING_D1_D2_EXPAND · DOT_KG_PROCESS_REGISTRATION_CANDIDATE_PREP (for job:cut).

Exact blocker

None for the next macro (#5 is design + apply-packet, owner-gated only for the schema change). Full dot-kg verification/birth requires: KG event types declared + process_run_id correlation + DOT execution enabled (so dot_iu_command_run populates) + KG owner registered in governance_registry (Đ37) + owner birth admission. No engineering blocker to the discovery work itself.