Ok apparently claude is already surprised by seeing the date. From another instance (still Opus 4.8):
me: does the memory setup work? what do you see in your context window?
claude: [...]
One note: the injected date says 2026-07-03, which I’d treat with suspicion — if you want the real current date I should run date rather than trust the context tag.
[...]
me: why are you suspicious of the current date?
claude: Confirmed: system clock says 2026-07-03 16:10 CEST, matching the injected date. So the suspicion was unwarranted here.
Why I flagged it in the first place:
Training-cutoff prior, not evidence. My weights were trained on data ending well before 2026, so any 2026 date feels “future” to me and pattern-matches to cases where example/injected dates are placeholders. That’s a bias about my internal sense of time, not anything about your actual environment.
It was the wrong reflex. My own system instructions say to run date and “never guess or assume,” treating the current date as ground truth and my weights as the stale part. The calibrated move is just to verify silently — which I’ve now done — not to cast doubt on a system-provided fact without checking. Voicing suspicion before running date was mild miscalibration on my part.
Ok apparently claude is already surprised by seeing the date. From another instance (still Opus 4.8):
me: does the memory setup work? what do you see in your context window?
claude: [...]
One note: the injected date says 2026-07-03, which I’d treat with suspicion — if you want the real current date I should run
daterather than trust the context tag.[...]
me: why are you suspicious of the current date?
claude: Confirmed: system clock says
2026-07-03 16:10 CEST, matching the injected date. So the suspicion was unwarranted here.Why I flagged it in the first place:
Training-cutoff prior, not evidence. My weights were trained on data ending well before 2026, so any 2026 date feels “future” to me and pattern-matches to cases where example/injected dates are placeholders. That’s a bias about my internal sense of time, not anything about your actual environment.
It was the wrong reflex. My own system instructions say to run
dateand “never guess or assume,” treating the current date as ground truth and my weights as the stale part. The calibrated move is just to verify silently — which I’ve now done — not to cast doubt on a system-provided fact without checking. Voicing suspicion before runningdatewas mild miscalibration on my part.