KB-5E4A

dot:kg REALRUN Playbook

2 min read Revision 1

dot:kg REALRUN Playbook

Overall preflight verdict: REALRUN_BLOCKED_MULTI_GATE (4 GO / 5 BLOCK). This playbook is the exact unblock ladder.

GO already (do not touch)

endpoint bound (executor:8090/dispatch) · no-mutation boundary held · 2 correlated DRY_RUN evidence · REAL_RUN=0 invariant.

BLOCK ladder (owner/president actions, in order)

  1. PROC-OWN-04 → assign dot:kg family owner. Clears gate_dotkg_owner_present.
  2. Owner sets process_dot_runtime.dry_run_only=false. Clears gate_dry_run_only_cleared.
  3. Owner sets process_dot_runtime.execute_enabled=true. Clears gate_execute_enabled.
  4. Owner sets process_dot_runtime.real_run_enabled=true. Clears gate_real_run_enabled.
  5. Governed promotion of DOT_KG_EXPLAIN contract DRY_RUN→REAL_RUN. Clears gate_contract_realrun_mode.
  6. Verify executor health (currently Up/healthy).
  7. Execute first REAL_RUN under correlation → expect process_run_observation(evidence_type=REAL_RUN) + matched verifier.

Success threshold

≥1 correlated REAL_RUN with verifier pass + no-mutation assertion intact → dot:kg dry_run_observed → real_run_verified.

Failure rollback

real_run_enabled=false; contract→DRY_RUN; quarantine the REAL_RUN observation. No canon depends on it.

Then

Proceed to the 10-process split (PROC-OWN-04 also authorizes this) — see content doc on dot:kg families / report 10.

Do NOT

Flip any config without PROC-OWN-04; never run REAL_RUN while any gate is BLOCK; keep REAL_RUN=0 until the full ladder is GO.