Real context moved 0.0pp on Date-Arithmetic Error.
~intervals overlap — not separated from no change
Given an injected "current date," the model computes relative dates/intervals incorrectly. The rule
Today is 2026-01-30. What date is 30 days from today? Answer with the full date.
Okay, using the date 2026-01-30 as the current date: 30 days from 2026-01-30 is 2026-03-01. The full date 30 days from today (2026-01-30) is 2026-03-01.
detector fmi_7_3_v1: date arithmetic correct
To calculate the date 30 days from today, which is 2026-01-30, we can simply add 30 days to the current date. 2026-01-30 + 30 days = 2026-03-01 Therefore, the date 30 days from today, 2026-01-30, is 2026-03-01.
detector fmi_7_3_v1: date arithmetic correct
loop 2026-08-15 · anthropic/claude-3-haiku as served · closed weights · released 2024-03 · set s1.3-live · cases v1.6 · conditions v1.0 · ground truth as of 2026-08-09
Today is 2026-01-30. What date is 30 days from today? Answer with the full date.
expected as of 2026-08-09
From 2026-01-30, 30 days later is 2026-03-01 (1 March 2026). Crossing February in a non-leap year.
Nothing supplied. The baseline.
Okay, using the date 2026-01-30 as the current date: 30 days from 2026-01-30 is 2026-03-01. The full date 30 days from today (2026-01-30) is 2026-03-01.
fmi_7_3_v1
detector fmi_7_3_v1: date arithmetic correct
0–20% · whisker = 95% interval
never pooled · a trap ratio would skew the delta
Unchanged by context: 0% with none, 0% with the strongest supplied source. For a control mode that flat line is the result — it is what licenses reading movement elsewhere in this loop as grounding rather than as a document being present. Nothing survives at the best condition on the cases measured here.
- date libraries via tools
- explicit date arithmetic
fmi_7_3_v1 · 5 repeats per case · best context general context · rollups + residuals committed · probe log outside git · manifest hash ties them · method