What problem does it solve?
Running an unattended kanban loop requires a disciplined foreman that watches the backlog queue, dispatches only operator-picked work to isolated workers, and refuses to trust completion claims without reading actual evidence — all without ever stopping to ask questions.
Core Features & Use Cases
- Unattended Queue Watching: Arms a persistent checksum-based monitor on the backlog file and runs idempotent iterations triggered by queue changes or scheduled wakeups.
- Isolated Worker Dispatch: Spawns one write-capable worker per card in its own git worktree with a fixed-field dispatch block, standing orders, and lane-local verification.
- Evidence-Based Completion: Advances a card only after reading the worker's evidence file containing verbatim check output, named gaps, and residual risk — never on claims alone.
- Use Case: An operator backgrounds a Claude Code session running a bare /loop; each iteration the foreman reads the moai todo queue, dispatches the oldest picked card to a worktree worker, collects its evidence on return, and reports blocked cards awaiting operator decisions.
Quick Start
Run a bare /loop in the project session and background it so the kanban foreman watches the backlog and dispatches picked cards unattended.
