{"found":true,"collection":"patterns","library_url":"https://www.grokbotdb.com/library/pat.roster-size-ceiling","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.roster-size-ceiling","name":"Four specialists behind one chief is the ceiling","category":"orchestration","problem":"The biggest team is not the best team, but the org chart is tempting.","technique":"Create a specialist only when the work genuinely requires different tools, different context, different expertise, independent verification or true parallel execution. Add Bots to remove proven bottlenecks.","why_it_works":"Every additional Bot adds another context window, another handoff, another place to lose information and another thing that can fail.","when_to_use":"Any roster design, especially before the system is proven.","manual_ref":"6.1","evidence":"documented","related":["pat.chief-of-staff","pat.split-on-vocabulary-boundary","pat.start-with-one-bot"],"confidence":"high","first_seen":"2026-09-03","last_verified":"2026-09-03"}}