logic-guardian

# logic-guardian ## Purpose Complex projects (trading bots, payment systems, game engines, state machines) contain interconnected logic that AI agents routinely destroy by accident. The pattern is always the same: new session starts, agent doesn't know existing logic, rewrites or deletes working code, project regresses. `logic-guardian` breaks this cycle by maintaining a machine-readable logic manifest, enforcing a pre-edit gate on logic files, and validating that edits don't silently remove existing logic. It is the "institutional memory" for business logic. ## Triggers - `/rune logic-guardian` — manual invocation (scan project, generate/update manifest) - Auto-trigger: when `cook` or `fix` targets a file listed in `.rune/logic-manifest.json` - Auto-trigger: when `surgeon` plans refactoring on logic-heavy modules - Auto-trigger: when `.rune/logic-manifest.json` exists in project root ## Calls (outbound connections) - `scout` (L2): scan project to discover logic files and extract function signatures - `verification` (L3): run tests after logic edits to confirm no regression - `hallucination-guard` (L3): verify that referenced functions/imports actually exist after edit - `journal` (L3): record logic changes as ADRs for cross-session persistence - `session-bridge` (L3): save manifest state so next session loads it immediately ## Called By (inbound connections) - `cook` (L1): Phase 1.5 — when complex logic project detected, load manifest before planning - `fix` (L2): pr...