KB-6603
07 — dot:kg Guarded Split / Event Path
2 min read Revision 1
07 — dot:kg Guarded Split / Event Path (Workstream F)
Status: ACTION-READY, verification gate open (do NOT fake verified)
dot:kg = correlated_dryrun_observed (one producer+verifier DRY_RUN pair sharing a correlation_id). REAL_RUN = 0; not in verified_candidates_v3. AI review = NEEDS_MORE_EVIDENCE.
Preview of effects
- 10-process split → would create 10 unretirable process births. Defer until verified.
- Event activation (the 7 process.* events) → changes runtime emission; reversible by deactivation.
- Owner assignment (family owner) → governance-level; can proceed independently of verification.
- birth/canon → all president-gated + handler unimplemented ⇒ guarded execute BLOCKS for any AI actor.
Verifier component decision
The verifier (DOT_KG_EXPLAIN_VERIFY) remains modeled as a deterministic component — its endpoint is NOT bound (VERIFY_ONLY). Binding it is an owner decision; leaving it modeled keeps the system fail-closed and avoids a second live endpoint. Recommendation: keep modeled until the REAL_RUN ladder begins.
Exact next steps (sequenced)
- Owner: assign dot:kg family owner (PROC-OWN-04, APPROVE_OWNER_ASSIGNMENT) — safe now.
- Engineering (next macro): REAL_RUN ladder for the EXPLAIN producer (runtime gate → first REAL_RUN → verified). Only then does dot:kg enter
verified_candidates_v3. - Owner: authorize the 10-process split → 10 births (after verification).
- Owner: activate process.* events (PROC-OWN-05), ideally after the first birth.
Invariant preserved
verified_candidates_v3 = job:cut only. dot:kg was NOT promoted, NOT verified, NOT born. No event activated.