Which clock should govern an agent’s authority to act?
A user, server, scheduler, model context, and policy may each carry a different account of the current time. None is correct for every action. A local calendar matters for a meeting. A monotonic clock matters for runtime order. A policy calendar may define a legal cutoff.
Time as evidence
A timestamp is not enough. A consequential action needs the time frame that gives the timestamp meaning, evidence that the observation is fresh, and a rule for disagreement between observers.
If that evidence weakens near an important boundary, authority may need to narrow until the system can establish the right frame again.
Questions to carry forward
Which observer matters for this action? How fresh must its time evidence be? What happens near midnight, a daylight-saving transition, or an expiring permission? Should an irreversible action stop when the relevant clocks disagree?
Time checks catch defects. A time model should also constrain what the system is allowed to do.