Using NTM as the Out-of-Session Substrate

AgentOps 3.0 runs its loops in session and ships no daemon, scheduler, or overnight runner. To run the loop unattended — always-on, scheduled, queue-driven — you hand it to an orchestration substrate. The reference substrate is NTM + MCP + managed-agents; this skill covers the NTM leg: a local Named Tmux Manager swarm of Claude/Codex agent panes. NTM is an adopted external tool (ntm on PATH), not an AgentOps-owned surface — AgentOps adopts it, it does not vendor it.

Skills are the runtime, not the CLI. The substrate dispatches a whole loop by spawning an agent that runs the rpi or evolve skill — it does not shell out to retired RPI/evolve CLI subprocesses. The loop lives as a skill an agent executes. The seam is NTM pane → agent → /rpi <bead> skill, one bead dispatched as one invocable unit.

When to use this skill / when to skip