Fresh enough for which job?

A document from twenty years ago may be exactly right for understanding an old architecture. A price from twenty minutes ago may be unsuitable for a transaction that requires a current one.

Age is a clue. Purpose supplies the standard.

Freshness becomes intelligible when you can say what may change, which changes affect the result, and how the caller will know whether those conditions still hold.

Separate three questions.

How old is the contribution? This can often be observed directly.

What has changed since it was made? This may require source, operating, or contextual knowledge.

Does that change matter to this use? This requires understanding the task.

A time limit can be a practical control. Its meaning depends on those relationships. The same elapsed time can be conservative for one use and inadequate for another.

A source can stay unchanged while its use becomes stale.

An architectural packet may be based on unchanged documents but written for a discarded product direction. A recommendation may correctly summarize an earlier scope while a new team has different constraints. A historical availability statement may remain accurate history while failing to describe a current offer.

These examples do not require source mutation. They require a changed relationship between the material and the job.

That is especially important in agent context reuse, where instructions, recipients, and mission state can change independently.

Make renewal purposeful.

Ask which condition should cause reconsideration. A source update? A new recipient? A changed obligation? A period of uncertainty that exceeds the task's tolerance?

The answer can support selective renewal, retaining what remains useful while revisiting the affected contribution.

Someone also has to own that recognition and response. Read the duties after the gauge.

Freshness is valuable because it protects a use. Define the use before deciding what “fresh” must mean.