{"found":true,"collection":"patterns","library_url":"https://www.grokbotdb.com/library/pat.chief-of-staff","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.chief-of-staff","name":"One coordinating Bot you talk to","category":"orchestration","problem":"A roster of five Bots becomes five chat windows you manually shuttle text between.","technique":"Make one Bot the only one you message. It checks whether another Bot owns the task, delegates first, does the work itself only when no specialist fits, and brings the result back to a single conversation.","why_it_works":"It protects the mission contract, preserves shared context, inspects handoffs and escalates only decisions that need you.","when_to_use":"Any roster past two or three Bots.","when_not_to":"Never without the send-once and short-thread rules; the orchestrator is the largest source of avoidable spend.","manual_ref":"3.13","evidence":"documented","related":["pat.orchestrator-send-once","pat.short-orchestrator-thread","pat.chief-builds-the-team"],"confidence":"high","first_seen":"2026-09-03","last_verified":"2026-09-03"}}