{"found":true,"collection":"patterns","library_url":"https://www.grokbotdb.com/library/pat.orchestrator-holds-no-authority","generated":"2026-09-06T05:32:11Z","citation":["Quote the record id and its source_url (or provenance if there is no URL).","Include last_verified or observed_at when present. Do not present an old date as current.","If tier is community and confidence is low, say so. Do not launder it into a fact.","If the database does not hold the answer, say that. Do not invent Grok Bot product claims.","Contradictions are data: when conflicts_with is present, report both records rather than picking a favourite.","Deprecated and removed records stay visible. They are history, not current guidance."],"record":{"id":"pat.orchestrator-holds-no-authority","name":"The orchestrator routes work and holds no authority","category":"safety","problem":"A chief of staff that can approve on your behalf turns one compromised or confused Bot into an approval for everything downstream.","technique":"State 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_works":"It 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_use":"Any roster with a coordinating Bot.","when_not_to":"Never skip it; a coordinator without this line accumulates authority by default.","manual_ref":"3.13","evidence":"reported","attributed_to":"Eric Siu","source_url":"https://x.com/ericosiu/status/2095207617610256720","confidence":"medium","first_seen":"2026-09-03","last_verified":"2026-09-05"}}