08 — dot:kg Owner / Event / Process Split Prep (Workstream G)

Prepare the post-dry-run path without performing it. No activation, no birth.

Current dot:kg state (live)

candidate_status_v6=plan_only_tested; endpoint_binding_status=all_missing (2 contracts, 0 endpoints); birth_readiness_v6=blocked_endpoint_missing; 36 members; owner_missing=true; event_missing=true; 0 DRY_RUN; not verified.

Prerequisite chain (ordered; none executed)

1. agent_api producer endpoint (engineering, external) — bind endpoint_ref, flip producer mode → DRY_RUN → true dry-run → dry_run_observed.
2. Cross-component correlation — dot:kg currently has no run-level correlation (the earliest policy gap). Establish a shared process_run_id across the pair/family runs.
3. Correlated REAL_RUN → real_run_observed → verified_candidate.
4. Owner registration — gov_object_ownership row (empty system-wide; do not fabricate). Điều 37 / Điều 39 (KG law owner).
5. 10-law-definition split at birth — dot:kg births as 10 process definitions (the 10 operating processes A–J), not one blob. Split proposal below.
6. process.* event activation — 7 types all active=false; activation is owner-gated and production-affecting → do not activate.

10-definition split proposal (birth packet)

Per D1/D2, the 36 DOTs implement 10 processes. Birth should create 10 process definitions, each a producer/verifier set: A Knowledge formation · B Business · C Feedback · D Monitoring · E Scaffold (partial invalidation) · F Priority decomposition · G Bottom-up discovery · H Eviction · I Self-learning · J Conversational. (Plus a governance/provenance overlay: PROVENANCE/OVERRIDE/EXPLAIN pairs.) Each definition declares its producer DOT(s), verifier DOT(s), trigger (event + cron), and the design invariant "Cấp A idle = Cấp B correct."

Owner packet (DRAFT)

• Object: PROC-CAND:dot:kg (KG family, 36 DOT / 18 pairs).
• Proposed owner role: Knowledge-Graph law owner (Điều 39).
• Evidence: contract-ready pilot, plan_only_tested, fixture sound (self-check 7/7).
• Gate: owner authority for unretirable birth + 10-def split.

Event activation packet (DRAFT, inactive)

• 7 process.* types → activation = one active=true flip each, owner-gated.
• Payload contract already defined (stream/lane/severity constraint-valid).
• Decision retained: do not activate this macro (no production emission).

Governance vs engineering boundary

First unblock = the producer endpoint (engineering, external). Correlation = engineering. Everything after step 3 is governance (owner, split, events) — sequenced and ready.

Architectural decision to surface to owner

The verifier (DOT_KG_EXPLAIN_VERIFY) is provably deterministic (doc 02 self-check). Owner decision: keep it agent_api (LLM-judged) or re-classify to deterministic? If deterministic, the verify half needs no endpoint and fn_dryrun_fixture_selfcheck (or app twin) becomes its real implementation — collapsing the verify-side blocker entirely.

Completion

dot:kg post-dry-run path fully sequenced and packaged.