Terms  /  Context Quality  /  Context Freshness
01 · Context Quality

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.

Context Freshness addresses a problem that Context Clarity alone can't solve. A prompt can be perfectly structured, free of redundancy, and high in Signal Density — and still cause problems if the information in it is outdated. The model doesn't know that the API endpoint changed last week, or that the team switched from REST to GraphQL, or that the client renamed their product. It takes the context at face value and produces output based on stale information, leading to subtle errors that are harder to catch than obvious ones.

Example
An agent's memory includes a project brief from three months ago that specifies PostgreSQL as the database. The team migrated to DynamoDB six weeks ago, but nobody updated the stored context. The agent continues generating PostgreSQL queries, and because the code is syntactically correct, the errors don't surface until deployment. The context was clean and well-structured — it was just wrong. A system that tracks Context Freshness would flag stale entries and prompt for verification.

More in Context Quality