always-current-date

To prevent stale date responses, acquire a fresh local time anchor before interpreting each direct user turn. This mechanism ensures replies rely on current observations rather than historical evidence, keeping temporal conversations accurate and anchored to today.

A local time anchor handles relative date calculations by capturing one new local time marker per turn. This stable reference point converts relative phrases like tomorrow or next Friday into actionable absolute dates when needed for tool-ready calculations.

If the clock is missing or invalid, date-dependent work is blocked using fail-closed error handling. The system uses a stable failure marker instead of guessing, preventing inaccurate temporal reasoning when the clock state is stale.

Yes, you can recover temporal reasoning state because the system reloads after compaction or resume. It reacquires the clock after midnight and preserves historical evidence separately from current state to maintain accurate recovery.

Yes, timezone precedence affects date acquisition by enforcing strict timezone rules during the relative clock call. This ensures the visible date prefix and local time anchor reflect the correct regional time before generating a response.