Backlog & lifecycle

Agents work like a team: they pull tasks from a prioritized backlog and pass through a clear state machine.

Backlog as a first-class object

The backlog is a persistent store with priorities and states. Tasks arise from various sources (manual, heartbeat/tick, a target system's webhook).

The dispatch loop

A cheap, always-running orchestration loop (no LLM) processes wake events per agent. A tick is a periodic "what's up?" impulse.

Triage → working → done

• triage — gather context, query memory
• working — do the task, use tools
• done — record the result, learnings into the wiki

Blocked & follow-up questions

If information or an approval is missing, the task goes blocked — with a question to a human. When the answer arrives, the agent continues at the same point (event correlation).