Native Orchestration

The orchestrator is not something you build from zero. Hermes ships native orchestration through its Kanban system: work is routed to profiles based on their --description, in auto or manual modes. This branch is "understand, use, and extend the native Kanban", not "design a giant prompt-router".

The failure to avoid: letting orchestration degenerate into one enormous prompt. Kanban keeps routing explicit — cards, descriptions, modes — so the system stays inspectable. Every routed task should produce an output you can contract and verify.

Planned notes

• The Kanban orchestrator: boards, cards, and the work model
• Routing to profiles by --description
• Auto vs manual orchestration modes
• Projects and worktrees: isolating a unit of work
• Output contracts: defining what "done" looks like
• Approval gates and draft mode inside a flow
• Verification and retries on failure
• Avoiding the "giant prompt" anti-pattern
• Extending Kanban vs reaching for custom routing
• Branch project: a local flow where a CLI request routes to the right actor/skill

Core sources

• Hermes — Feature: Kanban — https://hermes-agent.nousresearch.com/docs/user-guide/features/kanban
• Hermes — User Guide: Profiles (routing by description) — https://hermes-agent.nousresearch.com/docs/user-guide/profiles
• Hermes — Features overview — https://hermes-agent.nousresearch.com/docs/user-guide/features/
• Agentic Systems — multi-agent orchestration — TODO (see SOURCES.md).

Connects to: Profiles, Actors & Delegation · Skills & Procedural Memory · Income Workflows · Evaluation & Observability