Start setup

Library / Practices / pat.split-on-vocabulary-boundary

Split on the vocabulary boundary, not on task size

CategoryorchestrationManual3.1EvidencereportedAttributed to@0xRafy

ProblemThere is no good rule for when to add a second Bot, so people split on task size and get it wrong.

TechniqueAdd a second Bot the first time you catch yourself correcting context, for example clarifying that you meant the vendor Acme rather than the client Acme.

Why it worksThat correction means one Bot is holding two domains with different vocabularies, and it will keep confusing them.

When to useWhenever you notice yourself disambiguating.

orchestrationhigh confidencex.com/0xRafy/status/2090077067509370983 ↗pat.split-on-vocabulary-boundary

Cite this page or the record id. For bulk lookup use /api/record?id=pat.split-on-vocabulary-boundary. Do not invent a claim that is not on this page.