Multi-Agent Queue Orchestrator

Stop tasking agents one-off. Run a system.

Four JSON queue files (build, content, intel, review) feed into a HEARTBEAT.md decision engine. It checks queues on every heartbeat, routes each task to the right agent, tracks status from pending → in_progress → done, and picks up automatically.

The system:

• build.json → Forge (Codex)
• content.json → Scribe (Sonnet)
• intel.json → Radar (Gemini)
• review.json → Proof (Sonnet)

Add tasks via Triton chat: "Add to build queue: create Twitter thread formatter" → Triton creates the JSON task and appends it to the right queue.

HEARTBEAT.md routing:

• Check all 4 queues
• Find pending tasks
• Route by priority
• Spawn correct agent
• Update status to in_progress
• Log everything

What you get:

• Full queue file schema with all status types
• HEARTBEAT.md routing config
• Agent routing table
• Cron schedule for each agent
• Status lifecycle (pending → in_progress → done → blocked → failed)
• Example queue file + heartbeat routing decision
• Autonomy triggers for Triton