Context Load
The total volume and complexity of context a model must process in a single call.
Context Load is a neutral measurement — it's not inherently good or bad. A 100,000-token context isn't a problem if every token is relevant and well-structured. A 2,000-token context can be a disaster if it's full of noise. What matters is whether the load is managed intentionally or allowed to grow unchecked. The danger isn't size; it's unmanaged size. Teams that track Context Load as a metric can make informed decisions about when to summarize, when to trim, and when to let the context grow.
More in Context Quality
Context Debt
Accumulated ambiguity, redundancy, and disorder in a conversation or prompt.
Prompt Bloat
Oversized, redundant context that forces unnecessary reasoning.
Context Clarity
A state where the prompt contains only what the model needs — no ambiguity, no redundancy, high signal. The opposite of Context Debt.
Signal Density
The ratio of useful information to total tokens in a prompt. High signal density = low reasoning tax.
Prompt Hygiene
The practice of keeping prompts clean, structured, and free of accumulated noise. Preventive maintenance against Context Debt.
Context Freshness
How current and relevant the context is to the task at hand. Stale context — old instructions, outdated facts — increases reasoning cost even when well-structured.
Structured Context
Context organized with clear hierarchy, roles, and boundaries — making it machine-parseable, not just human-readable. The architectural practice behind Context Clarity.