Minimize Context

Give an agent the smallest packet that is sufficient to make its assigned decision correctly and safely.

Activation evidence

Apply this principle when constructing or refreshing model-facing context and the candidate material contains more than the assigned decision needs, such as:

• requirements, design sections, tasks, paths, or principles for other work;
• complete conversation history when current approved artifacts are authoritative;
• broad repository listings or files unrelated to the assigned change;
• large logs, test output, generated content, or repeated diagnostics that can be filtered mechanically.

Do not activate merely because a directly relevant artifact has several lines. First identify what the assigned decision requires. Repository instructions, user constraints, conflicting facts, safety conditions, and evidence provenance remain relevant even when they consume context.

Decision rule

Send only the assigned requirements, design decisions, task, governing instructions, relevant paths and interfaces, applicable principles, known blockers, and required evidence; mechanically filter large output and retain a durable pointer to the full receipt.