Timeliness asks whether information remains valid when an agent uses it. In a dispute, an amendment may become governing only after its effective date, a corrected delivery record may change the chronology, and a later authority may limit a legal proposition. Freshness alone is insufficient: permissions, consent, policies, workflows, operational signals, graph assertions, indexes, and model configurations can all change. section 5.6
Manage timeliness by checking:
- effective dates, expiry, invalidation, and supersession conditions; section 5.6
- the source, policy, graph, model, and tool versions active at a material decision point. section 5.6
Dispute chronology
An agent may reconstruct the information it used yet still fail to show that the information was authoritative at that moment. A corrected delivery record, effective contract amendment, or later judgment can invalidate an otherwise traceable position. section 5.6



