{"found":true,"collection":"patterns","library_url":"https://www.grokbotdb.com/library/pat.orchestrator-send-once","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-send-once","name":"The orchestrator sends once and waits","category":"cost","problem":"A chief that confirms a task, chases it, then confirms receipt has sent four messages for one job, and one audit found the orchestrator ate more tokens than the workers did.","technique":"Instruct the chief to send each instruction once and then wait, and never to forward attachments between channels.","why_it_works":"Confirmation chatter is billable and adds nothing to the result.","when_to_use":"Every orchestrator.","manual_ref":"3.13","evidence":"reported","attributed_to":"@kloss_xyz","source_url":"https://x.com/kloss_xyz/status/2093680229462269953","related":["pat.chief-of-staff","pat.state-on-disk","pat.tag-exactly-one-bot"],"confidence":"high","first_seen":"2026-09-03","last_verified":"2026-09-03"}}