kanban-orchestrator

First run hermes profile list to discover real profiles, then sketch the task graph showing parallel lanes and dependencies. Create independent lanes as separate kanban_create cards and gate dependent cards with parents=[...] so they stay in todo until parents finish.

The dispatcher silently drops cards assigned to profile names that do not exist on the machine. Verify assignees with hermes profile list or hermes kanban assignees before creating cards, and never invent profile names.

That message is a generic label for any clean exit without kanban_complete or kanban_block. Common real causes are rate-limit 429 collisions from uncapped concurrency, missing Kanban Protocol sections in worker SOUL.md files, or spend-cap 404s; check hermes kanban log for the actual error.

No. When dispatch_in_gateway is true, the dispatcher runs inside the gateway process and caches config.yaml at startup. You must run hermes gateway restart and confirm a new PID before any kanban.* change, such as max_in_progress_per_profile, takes effect.

Do not unblock it, since that returns it to ready and the dispatcher re-runs it, creating duplicate work like a second PR. Verify the deliverable exists, then mark it done directly in the board SQLite database with an UPDATE on the tasks table.

Use Kanban when multiple specialists are needed, work must survive restarts, parallel fan-out helps, review loops are expected, or an audit trail matters. For small one-shot reasoning tasks, delegate_task or a direct answer is sufficient.