Principle of Parsimony in Context Engineering

The Principle of Parsimony in Context Engineering is a design rule: every element in the context, and every level of detail within each element, exists because it contributes to unambiguous task interpretation, enforceability of constraints, or result quality. In compact form: A context is parsimonious when nothing in it can be removed without introducing ambiguity or degrading the result. What the Definition Means in Practice The definition above packs several ideas into one sentence. Here is what each part means when you sit down to assemble a context. "Every element." An element is anything that occupies tokens in the context window: a prompt, an instruction rule, a specification, a code fragment, a document excerpt, dialog history. Before adding any of these, ask: does this help the model do the current task? Example: You are fixing a bug in authentication. The reporting module's database schema does not help. Leave it out. "Every level of detail." Even when an element belongs in c