Start setup

Library / Practices / pat.orchestrator-holds-no-authority

The orchestrator routes work and holds no authority

CategorysafetyManual3.13EvidencereportedAttributed toEric Siu

ProblemA chief of staff that can approve on your behalf turns one compromised or confused Bot into an approval for everything downstream.

TechniqueState in the orchestrator's description that it cannot send, cannot publish, and does not count as the approval for anything. Approvals live in the one-to-one conversation with the Bot that owns the action.

Why it worksIt keeps routing and authority in different places, so the convenience of an orchestrator does not quietly become a bypass of every red line underneath it.

When to useAny roster with a coordinating Bot.

When not toNever skip it; a coordinator without this line accumulates authority by default.

safetymedium confidencex.com/ericosiu/status/2095207617610256720 ↗pat.orchestrator-holds-no-authority

Cite this page or the record id. For bulk lookup use /api/record?id=pat.orchestrator-holds-no-authority. Do not invent a claim that is not on this page.