D1-supp — KG EXPLAIN Pilot Subgraph + Process Discovery Status

STATUS: DRAFT / CANDIDATE companion to d1-knowledge-graph-curated-cluster-2026-06-04.md. Adds the contract-bound EXPLAIN pilot and the live discovery status. Does not alter the law or D1. No DOT executed; 0 production mutation.

1. The 36-DOT / 18-pair correction (clarified)

D1 §8 lists the family as 36 DOTs = 18 producer/verifier pairs. The dot:kg process candidate (PROC-CAND:dot:kg) has 36 members in evidence_graph_v2 (verified this run). Engine mix across the family: pg_function / agent_api / hybrid; the 12 agent_api DOTs are the LLM-reasoning subset, of which the EXPLAIN pair is the pilot. The earlier "18 producers orphaned" inventory artefact was a filter bug (on-demand excluded), since fixed in v_axis_process_inventory_v2.

2. The EXPLAIN pilot subgraph (canonical KG dry-run shape)

Fixture FIXTURE:dot:kg:explain:v1 (4 nodes / 4 edges), synthetic-but-grounded, mirrors the KG-law cluster — no production knowledge_graph row is read or written:

• nodes: kgn:dieu39 (Điều 39 law article, the target) · kgn:dot_kg_family · kgn:explain_pair · kgn:provenance.
• edges: dieu39 —GOVERNS→ dot_kg_family; dot_kg_family —CONTAINS→ explain_pair; dot_kg_family —CONTAINS→ provenance; explain_pair —DEPENDS_ON→ provenance.
• producer (DOT_KG_EXPLAIN) must reference kgn:dieu39, cite only the 4 node ids, narrate "Điều 39 / EXPLAIN / GOVERNS".
• verifier (DOT_KG_EXPLAIN_VERIFY) checks: target referenced, no hallucinated node, every edge exists, no production-table reference.

This is the canonical KG dry-run shape: a producer emits a grounded explanation over a fixed subgraph; a verifier confirms it cited only real nodes/edges. The pair is the template for all KG agent_api DOTs.

3. Fixture is provably sound (this run)

The deterministic verifier logic was implemented (fn_dryrun_fixture_selfcheck) and run on the real fixture: 7/7 pass (namespace, target-in-subgraph, must-reference, no hallucinated nodes, narrative non-empty, pass-criteria non-empty, no production-table reference). Negative control (inject a ghost node) → fails with the exact reason. The fixture and the verify logic are sound; only the producer's LLM invocation endpoint is missing.

4. Connecting IU 10649925 (the bridge)

IU 10649925 (#7-36-dot-kg) is the single matrix IU that bridges the knowledge_graph topic to the 36 DOTs (D1 §10). It is the structural anchor for the dot:kg process candidate. No per-DOT spec IUs exist yet (D1 §11 gap #1) — the EXPLAIN pilot is the first DOT given a full input/output contract (the fixture), and can seed a per-DOT spec series.

5. Process discovery status (live, this run)

• dot:kg: candidate_status_v6 = plan_only_tested, birth_readiness_v6 = blocked_endpoint_missing, admission gap = no_correlation_model (earliest; also fails endpoint + dry-run gates).
• The design "has never run" (D1 §11 gap #5) remains true: 0 DOT executions, 0 DRY_RUN, 0 REAL_RUN, 0 KG events.
• The discovery views (v_process_discovery_*v6) now track exactly which rung each candidate is on and the next required action.

6. Warning

No production DOT was executed. This companion documents structure and contract only; it authorises nothing.