KG/dot-kg Process Discovery & Document Building Pilot — 00 README First
00 — README First
Macro: KG_DOT_PROCESS_DISCOVERY_AND_DOCUMENT_BUILDING_PILOT Date: 2026-06-04 Mode: EXECUTION_MODE (query_pg RO + ssh contabo → docker exec postgres psql -U directus RW; KB upload_document) Status: PARTIAL — both branches delivered (content + discovery design); only owner/operator decisions remain. Live mutation: YES — 6 additive read-only views. 0 births (1,158,132 before == after; rehearsed BEGIN/ROLLBACK net-zero; independent MCP read-back PASS). 0 process born, 0 taxonomy node, 0 approval approved, 0 IU edit, 0 workflow executed, 0 promotion.
What this package is
The previous macro identified knowledge_graph / dot-kg as the convergence pilot. This macro turns that into two real outputs from live evidence:
- A. Content/document output — D1 Knowledge Graph cluster document + D2 dot-kg SOP/runbook (both published to KB), plus content & process maps.
- B. Process discovery output — an evidence graph for the dot-kg DOTs, a generic Process Discovery Engine v1 design, and 6 live read-only discovery views that already score 17 process candidates system-wide.
The decisive live finding (old reports were wrong on the count)
Every prior report says "18 dot-kg DOTs." Live evidence says 36 (DOT_KG_*, all active). The law (Điều 39 v2.3) itself states "36 DOT (18 cặp)" — 18 producer/verifier pairs = 36 DOTs. The "18" was the pair count, silently re-read as a DOT count.
This matters because the process axis inventory (v_axis_process_inventory) counts exactly 18 of them — and they are not a random 18: they are the 18 Cấp A (verifier) DOTs (cron/dual). The 18 Cấp B (producer) DOTs (on-demand) are orphaned — invisible to the process axis because its trigger filter excludes on-demand. The discovery engine surfaces this precisely.
Read order
01-live-state-and-ssot-confirmation.md— live numbers, SSOT reconciliation, the 36-vs-18 finding, safety baseline.02-kg-content-cluster-map.md— the 16 KG IUs mapped (Workstream A).03-d1-knowledge-graph-cluster-document.md— D1 (the KB-ready cluster document; also published standalone).04-dot-kg-process-evidence-graph.md— the 36-DOT evidence graph (Workstream C).05-d2-dot-kg-sop-runbook.md— D2 (the KB-ready SOP; also published standalone).06-process-discovery-engine-v1-design.md— the generic 9-stage engine design (Workstream E).07-readonly-discovery-views-or-apply-packet.md— the 6 live views + apply/rollback packet.08-kg-dot-kg-scoring-and-birth-readiness.md— scoring & birth-readiness.09-registries-pivot-ui-impact.md— RP/UI impact.10-next-macro-decision.md— next macro.11-final-summary.md— final summary.12-gpt-mcp-readable-checkpoint.md— full checkpoint (also short checkpoint atcheckpoint-kg-dot-process-discovery-pilot-2026-06-04.md).
Published standalone KB documents (the content deliverables)
- D1:
knowledge/dev/design/knowledge-graph/d1-knowledge-graph-curated-cluster-2026-06-04.md(candidate/draft). - D2:
knowledge/dev/sop/dot-kg/d2-dot-kg-process-family-sop-runbook-2026-06-04.md(candidate/draft).
Live artifacts (read-only, drop-reversible)
v_process_discovery_evidence_graph · v_process_discovery_candidates · v_process_discovery_orphan_components · v_process_discovery_quality_score · v_process_discovery_drift_signals · v_process_discovery_birth_ready_queue. Rollback: 6 × DROP VIEW. SQL: /tmp/process_discovery_views.sql.
Hard guardrails honoured
No dot-kg DOT executed. No process canonized/born. AX-PROCESS stays CANDIDATE. No approval approved. No IU body edited. No source tag deleted. No birth/pre-birth/governance broadly altered. No dot-pivot-update registered. Engine is generic (17 candidates across 14 DOT families + jobs + workflows), not hardcoded to dot-kg. No candidate is claimed "verified" without runtime+correlation evidence — and the one that is (job:cut) earns it from a real completed run.