05 — dot:kg Owner / Event / 10-Process Split (Workstream D)

Status advance (this run)

dot:kg moved plan_only_tested → dry_run_observed (candidate_status_v6). The first true DRY_RUN of the EXPLAIN producer is recorded with real gpt-4o evidence (doc 02). It is not verified (correctly).

Updated sequence (what's done / what's next)

1. endpoint ✓ deployed + bound (DOT_KG_EXPLAIN).
2. true dry-run (producer) ✓ done, verifier 5/5, is_mock=false.
3. correlation — NEXT engineering-feasible step: run EXPLAIN + VERIFY under one correlation_id and record cross-component correlation (policy gate gate_correlation currently false for dot:kg). VERIFY is deterministic; a dry-run pair would set has_cross_component_correlation=true.
4. real run — owner-gated (would require flipping runtime gates; FORBIDDEN here).
5. verified — only after real run + correlation + owner.
6. owner — assign governance owner (Điều 37); governance_object_ownership currently empty.
7. 10-process-def split — see below.
8. process.* event activation — 7 events inactive; owner-gated (FORBIDDEN here).

VERIFY contract — owner decision

DOT_KG_EXPLAIN_VERIFY is deterministic. Owner decides: keep as agent_api (bind to same endpoint) OR re-classify as a deterministic DOT (no endpoint). Recommendation: re-classify deterministic — the verifier is pure code; an LLM endpoint adds cost/nondeterminism for no benefit. Left unbound pending this decision.

10-process definition proposal (D2 SOP)

The dot:kg family (12 agent_api DOTs incl. EXPLAIN pilot; 36 members in the cluster) should be born as 10 law-grounded process definitions, NOT one blob — per d2-dot-kg-process-family-sop. Split axes: explain, verify, curate-cluster, provenance-tag, audit, ingest, embed, link, render, govern. Each gets its own definition_code, owner, fixture, and dry-run gate. Birth = 10 defs (owner-gated; FORBIDDEN here).

Packets finalized (no live mutation)

• owner packet (assign Điều-37 owner) — ready.
• event activation packet (7 process.* → active=true via activate_event_type approval) — ready, NOT executed.
• correlation/real-run requirements — documented.
• birth admission checklist — structural✓ simulated✓ dry_run✓ correlation✗ real_run✗ verified✗ owner✗ event✗.
• governance handoff checklist — ready.

Completion: dot:kg path ready; next safe engineering step = EXPLAIN+VERIFY correlated dry-run pair (no real run, no birth, no activation).