10 — dot:kg Owner / Event Activation Prep (Workstream I)

Prepare downstream governance without performing it.

Current dot:kg state

v5 plan_only_tested; owner_missing=true; event_missing=true; 0 DRY_RUN; not verified. Blocked from verification by the missing agent_api endpoint (doc 07).

Prerequisite chain (ordered, none executed)

1. agent_api endpoint (engineering) — bind endpoint_ref, flip contract mode to DRY_RUN → true DRY_RUN → dry_run_observed.
2. Correlated real run (later) — REAL_RUN with shared process_run_id → real_run_observed → verified_candidate.
3. Owner registration — gov_object_ownership row for dot:kg (currently empty system-wide; do not fabricate). Điều 37.
4. 10-law-definition split at birth — dot:kg births as 10 law-process definitions, not one blob (per d2 SOP). Split proposal belongs in the birth packet.
5. process.* event activation — 7 types all active=false. Activation packet staged (reference-without-emit until owner approves); do not activate in this macro (production-affecting).

Owner registration packet (DRAFT)

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

Event activation packet (DRAFT, inactive)

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

Status

dot:kg downstream path is fully sequenced. First unblock = the endpoint (Workstream F blocker). Everything after is governance, not engineering.