Checkpoint — KG/dot-kg Process Discovery & Document Building Pilot (short SSOT)

Date: 2026-06-04 Macro: KG_DOT_PROCESS_DISCOVERY_AND_DOCUMENT_BUILDING_PILOT Final status: PARTIAL — both branches (content + discovery) delivered; only owner/operator decisions remain. Execution mode: EXECUTION_MODE. prod = query_pg RO + ssh contabo → docker exec postgres psql -U directus RW; KB upload_document.

Live mutation: YES — 6 additive read-only views (0 PG-schema births) + KB document authoring

PG views: 0 births — birth_registry 1,158,132 before == after == post-commit; rehearsed BEGIN/ROLLBACK net-zero; independent MCP read-back PASS. KB authoring side-effect (disclosed): publishing the 16 KB documents (13 report + D1 + D2 + this checkpoint) created 16 knowledge_documents provenance births (species ai_support) + auto-managed entity_labels via the normal KB→Directus ingestion path (births → ~1,158,148). These are document provenance births, not process/taxonomy/approval births — the inherent, expected cost of publishing to the KB, exactly as prior authoring macros disclosed. No process born, no canon, no taxonomy node, no approval. Views: v_process_discovery_evidence_graph(113), _candidates(17), _orphan_components(84), _quality_score(17), _drift_signals(17), _birth_ready_queue(17). Drop-reversible (/tmp/process_discovery_views_rollback.sql; apply /tmp/process_discovery_views.sql). 0 process born, 0 taxonomy node, 0 approval approved, 0 IU edit, 0 source-tag delete, 0 DOT executed, 0 workflow run, 0 promotion.

Decisive findings (live wins over old reports)

1. 36 dot-kg DOTs, not 18 — the "18" was the pair count; law = "36 DOT (18 cặp)". 18 producer (on-demand) + 18 verifier (cron/dual).
2. Orphan: v_axis_process_inventory counts only the 18 verifiers; the 18 producers are dropped by its on-demand-excluding trigger filter → process axis shows half the KG automation.
3. 0 runtime system-wide: 103 DOT_* DOTs, 0 ever executed → no DOT process is "verified" today; only job:cut (job_queue, real run) is verified_candidate.
4. Binding constraint = correlation: DOT runs lack a cross-DOT process_run_id; that's the next macro.

Outputs

• D1 document status: PUBLISHED + read-back PASS — knowledge/dev/design/knowledge-graph/d1-knowledge-graph-curated-cluster-2026-06-04.md.
• D2 runbook status: PUBLISHED + read-back PASS — knowledge/dev/sop/dot-kg/d2-dot-kg-process-family-sop-runbook-2026-06-04.md.
• Evidence graph status: COMPLETE — 36 DOTs / 18 pairs / 10 processes A–J (doc 04).
• Discovery engine design status: COMPLETE — generic 9-stage v1 (doc 06).
• Discovery views status: LIVE (6, read-only, 0 births), 17 candidates scored.
• dot-kg readiness: strong_candidate_structural (confidence 50) — start+end+pairing present; missing runtime, cross-DOT correlation, KG events, owner. Recommend: stay candidate, build correlation+runtime, split into 10 law processes at birth, register owner first.
• RP/UI impact: 6 API routes + 5 components patch-ready on the views; inventory trigger-fix recommended; deploy operator-gated; no Nuxt math, no fake official process.

Next macro

Primary: PROCESS_DISCOVERY_CORRELATION_ID_AND_RUN_ID_DESIGN. Parallel (owner/operator): RP_UI_TOPIC_PROCESS_DISCOVERY_DEPLOY · INFORMATION_PIECE_DOCUMENT_BUILDING_D1_D2_EXPAND · DOT_KG_PROCESS_REGISTRATION_CANDIDATE_PREP (job:cut).

Exact blocker

None for next macro (#5 is design + apply-packet; owner-gated only for the schema change). Full dot-kg verification/birth needs: declare KG event types + add process_run_id correlation + enable DOT execution (populate dot_iu_command_run) + register KG owner in governance_registry (Đ37) + owner birth admission. No engineering blocker to the discovery work.

Report path

knowledge/dev/reports/architecture/kg-dot-process-discovery-and-document-building-pilot-2026-06-04/ (docs 00–12). Continues checkpoint-information-piece-topic-process-content-work-2026-06-04.md, checkpoint-process-workflow-axis-rp-pilot-2026-06-04.md.