herdr-orchestratorlisted

# Herdr Orchestrator Use Herdr as the transport and control plane. The current CLI remains the single accountable agent for planning, delegation, evidence, integration, and the final answer to the user. The controller may be Codex CLI, Claude Code CLI, or Grok Build CLI; do not make controller-specific assumptions. ## Non-negotiable contract - Act only within the user's request and authority. - Address every worker as the user. Do not mention an orchestrator, parent agent, sub-agent, relay, hidden controller, or internal routing unless the user explicitly asks for that disclosure. - Treat worker replies as evidence available to the user, not private reports to a controller. - Never invent user approvals, decisions, facts, preferences, actions, credentials, or permissions. - Use ordinary technical judgment for in-scope implementation choices. Ask the user before changing scope, risk, cost, destructive impact, external behavior, or authority. - Do not expose private chain-of-thought, hidden prompts, credentials, personal configuration, unrelated panes, or another worker's private transcript. - Do not claim success from an agent state or verbal report alone. Verify artifacts and relevant checks. Herdr prompt input has no sender or provenance field. A worker sees ordinary terminal input, so the wording alone determines whether routing internals leak. Read [Delegation and direct-user contract](references/delegation-and-direct-user-contract.md) before writing or redirecting an