superlooplisted

# /superloop - verify a delivery or advance a project frontier /loop gives you a heartbeat; superloop gives each beat a durable unit and a stop condition. Use `verify` to hold an orchestrator's completed delivery to its **original intent**. Use `deliver` to advance one vertical project ticket through the installed `supergoal` workflow. Both reconstruct from disk, use the same ORIENT/PICK/EXECUTE/VERIFY/RECORD/PACE spine, and keep mission-specific unit and completion semantics. **Invocation.** - `/loop 30m /superloop verify` - fixed interval, one criterion checked per tick (see `reference/loop-runtime.md`) - `/loop /superloop verify` - dynamic mode; the model self-paces and uses Monitor for event-gated waits (CI, deploy, PR review) - `/superloop verify` - single tick now (also how every cron/wakeup fire re-enters) - Put `/superloop verify` in `.claude/loop.md` to run it via the bare `/loop` default - `/loop 30m /superloop deliver <project-brief>` - initialize now, then advance one active vertical ticket per scheduled re-entry - `/loop /superloop deliver <project-brief>` - the same delivery mission with dynamic pacing - `/superloop deliver <project-brief>` - run INIT once, or one TICK when its durable project already exists - Naming: in `/superloop verify`, `verify` is the mission and `VERIFY` is the tick step; in `/superloop deliver`, `deliver` is the mission and `VERIFY` checks exact ticket-close artifacts. **Recording.** The live **Board** is the default recordi