10 · dot:kg 10-Process Split + Event Plan (2026-06-05)

Post-REALRUN governance package for the dot:kg family (carried by PROC-OWN-04, process_family_registration). Nothing here is birthed or canon'd without authority.

Why a split

dot:kg is a family, not a single process. After a verified REAL_RUN it is authorized (PROC-OWN-04) to split into ~10 governed process definitions, each with its own owner handoff and event lifecycle.

Proposed 10 process definitions (split criteria = distinct KG operation + distinct evidence contract)

1. dot:kg:explain — explain a node/edge (the piloted DRY_RUN op).
2. dot:kg:ingest — ingest source → entities.
3. dot:kg:link — create/maintain universal_edges.
4. dot:kg:dedupe — entity resolution / merge.
5. dot:kg:classify — entity/label classification.
6. dot:kg:embed — vector embedding refresh (qdrant).
7. dot:kg:verify — deterministic verifier component.
8. dot:kg:reconcile — KG vs source drift reconcile.
9. dot:kg:export — KG → downstream snapshot.
10. dot:kg:retire — node/edge retirement lifecycle.

Split criteria

Each definition must have: a bound endpoint or dot runner, a no-mutation or controlled-mutation assertion, a correlated verifier, and an evidence contract (DRY_RUN→REAL_RUN ladder per op). Ops that mutate (link/dedupe/retire) require stricter owner gating than read ops (explain/classify/export).

Owner / governance handoff

PROC-OWN-04 assigns the dot:kg family owner; the family owner then sub-delegates per-definition owners. No delegation rows exist today (forbidden_actions blocks president-gated actions for non-humans).

Event activation sequence (depends on PROC-OWN-05)

Per-definition lifecycle emits process.run.started → process.step.* → process.run.completed|failed, plus process.correlation.missing / process.evidence.missing guards. Activation is global (7 event types) via PROC-OWN-05, then each dot:kg definition opts in.

Relation to AX-PROCESS / AX-TRIGGER

• AX-PROCESS: each of the 10 becomes an official process row after owner+president (denominator contribution toward 453).
• AX-TRIGGER: dot:kg triggers (dot_event/dot_cron classes) map their relations onto these 10 once AX-TRIGGER is owned.

RP visibility effect

After REAL_RUN + split + birth: RP lists 10 dot:kg processes under AX-PROCESS, each with live run evidence.

Faked: NONE — plan only; 0 dot:kg processes registered, 0 births.