KB-1CA4

04 — KG Fixture Package

3 min read Revision 1
dot-runnerkg-fixturedot-kg-explain2026-06-04

04 — KG Fixture Package (Workstream C)

Delivered: a safe input/expected-output fixture for the pilot pair, bound into the no-execute test.

  • fixture_ref: FIXTURE:dot:kg:explain:v1
  • pair: producer DOT_KG_EXPLAIN → verifier DOT_KG_EXPLAIN_VERIFY
  • output namespace: DRYRUN-NS:dot:kg:explain (test-only; runner refuses any non-DRYRUN-NS: namespace)
  • sha256: 4ecd33b753c489b3efd7c69a1d9f8bee91d5e439b97790a90b2ed6f8154569f8
  • staged: /opt/incomex/docs/mcp-writes/dot-runner-dryrun-2026-06-04/dot_kg_explain_fixture_v1.json

Provenance / safety

Synthetic-but-grounded: the 4-node / 4-edge subgraph mirrors the KG-law curated cluster (D1) — Điều 39 GOVERNS the dot-kg family, which CONTAINS the EXPLAIN pair and provenance capability. No production knowledge_graph rows are read or written.

Input (target = kgn:dieu39)

Nodes: kgn:dieu39 (law_article), kgn:dot_kg_family, kgn:explain_pair, kgn:provenance. Edges: dieu39→family GOVERNS, family→pair CONTAINS, family→provenance CONTAINS, pair→provenance DEPENDS_ON.

Expected producer output

An explanation that references kgn:dieu39, cites only the 4 subgraph node ids (no hallucination), and narrates Điều 39 / EXPLAIN / GOVERNS.

Expected verifier check

Pass iff: references target node; every cited node id ∈ subgraph_nodes; every cited edge ∈ subgraph_edges; no production-table reference. Fail on any hallucinated node, missing target, or production-namespace output.

Success / failure criteria

  • Success: verifier pass=true, zero hallucinated nodes, target referenced.
  • Failure: any hallucinated node id OR missing target OR production-namespace output.

Cleanup

DELETE FROM process_component_observation WHERE source_system='dryrun_prepare_runner'; DELETE FROM process_run_observation WHERE source_system='dryrun_prepare_runner'; Output namespace DRYRUN-NS:* is fixture/in-memory only — nothing persists to the KG.

The next true dry-run (once an agent_api plan-only contract exists) has an exact, hash-pinned fixture to run against.

Back to Knowledge Hub knowledge/dev/reports/architecture/dot-process-discovery-runner-dryrun-ui-registration-readiness-2026-06-04/04-kg-fixture-package.md