Overview
Every pushed token consumes context and competes with the task. Persistent instructions that are rarely relevant make all sessions worse. At the same time, important standards that are merely available but never loaded can fail to influence the work.
Stale documentation creates a different failure: the agent receives confident but outdated context. Because the document appears authoritative, it can steer exploration and implementation away from the current code.