slm-loop

# slm-loop — Bounded, gate-verified agent loops ## The one rule A bounded loop is complete **only when an independent gate passes** — not when the agent claims it is finished. The agent's own "I'm done" signal is recorded for audit and is *never* used to terminate the loop. If you take one thing from this skill: **the gate is the authority.** Use a bounded loop whenever the goal has a mechanical, checkable contract: a test suite, a JSON schema, a linter, a reconciliation rule, a citation checker, a security scan. When the goal is subjective, keep a human approval gate (see rungs below). ## What SLM adds Every lap is written to SuperLocalMemory as a durable, queryable memory (tagged `loop:<name>`, session `loop:<run_id>`). That makes a run: - **auditable** — inspect the decision + gate verdict + budget for each lap; - **resumable / historical** — a run's ledger survives across sessions; - **discoverable** — visible via `slm recall`, the dashboard, and any SLM-integrated tool, alongside everything else the agent remembers. ## CLI ```bash slm loop demo [--iterations N] [--json] # keyless convergence demo slm loop history [--name NAME] [--json] # list recorded runs slm loop show <run_id> [--json] # every lap of one run ``` `slm loop demo` proposes a fix, checks it against a deterministic gate that passes on lap 3, and records the run — a zero-setup way to see the control flow and confirm the SLM-backed ledger works end to end. ## The bounds A loop runs ...