Queues & the mesh

Work is durable, addressed to a named identity, and observable while it runs. A request that fails is a ticket in a state you can inspect — not a lost turn in a conversation.

• Tickets, not calls. Scheduled and swarm-initiated work enters a queue with a declared ticket type, and the dispatcher routes it by the workflow that type registered.
• One bot per ticket type, by default. The persona carries its own quality gate — classification rules, citation rules, the artifacts it must produce. Most work needs no second reviewer bot; a workflow can opt into one with a revision limit when the worker genuinely cannot self-gate.
• Interactive work skips the queue and calls the owning bot directly — but records its cost against that same bot, so the accounting is identical either way.
• Streams, heartbeats and dead letters. Each agent reads its own stream with a consumer group and publishes a heartbeat; undeliverable work lands somewhere you can actually look at it.