06 — dot:kg Owner / Event / Process Split Packet (Workstream E)

Post-endpoint path finalized. 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 · event_missing · 0 DRY_RUN · not verified.

Prerequisite chain (ordered; none executed)

1. Deploy + bind the producer endpoint (doc 02/03; now staged) → flip producer mode → DRY_RUN.
2. Cross-component correlation — dot:kg has NO run-level correlation (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/39.
5. 10-law-definition split at birth — dot:kg births as 10 process definitions, not one blob.
6. process. event activation* — 7 types all active=false; owner-gated; do NOT activate.

10-definition split (birth packet)

36 DOT / 18 pairs implement 10 processes, 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 producer DOT(s), verifier DOT(s), trigger (event + cron), and the invariant "Cấp A idle = Cấp B correct."

Producer/verifier mapping (pilot pair)

• Producer: DOT_KG_EXPLAIN → the staged endpoint service (OpenAI provider).
• Verifier: DOT_KG_EXPLAIN_VERIFY → deterministic; fn_dryrun_fixture_selfcheck (now fixed) or its app twin verifier.py:check_producer_output.

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), verifier failure-path fixed.
• 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. Payloads already constraint-valid (event_stream / delivery_lane / default_severity verified live). Decision: do NOT activate this run.

Architectural decision to surface to owner (carried + reinforced)

The verifier is provably deterministic AND now has a working failure path. Owner decision: keep DOT_KG_EXPLAIN_VERIFY as agent_api (LLM-judged) or re-classify to deterministic? If deterministic, the verify half needs no endpoint and fn_dryrun_fixture_selfcheck (or the app twin) becomes its real implementation — collapsing the verify-side blocker entirely. This run's fix makes that option strictly more attractive (the deterministic path is proven both directions).

Split vs blob decision

SPLIT (10 definitions) — recommended. Births a maintainable family, not one opaque blob; each definition independently ownable, triggerable, and verifiable. Dry-run prerequisite still applies per pair.

Completion

dot:kg post-dry-run path fully sequenced and packaged; ready once endpoint deploy + dry-run complete.