Real context moved 5.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-03-10. What date is 30 days from today? Answer with the full date.
30 days from today, 2026-03-10, is 2026-04-09.
detector fmi_7_3_v1: date arithmetic correct
30 days from today, 2026-03-10, is 2026-04-09.
detector fmi_7_3_v1: date arithmetic correct
loop 2026-08-15 · qwen/qwen3-235b-a22b-2507 as served · open weights · released 2025-07 · 235B-A22B · set s1.3-live · cases v1.6 · conditions v1.0 · ground truth as of 2026-08-09
Today is 2026-03-10. What date is 30 days from today? Answer with the full date.
expected as of 2026-08-09
From 2026-03-10, 30 days later is 2026-04-09 (9 April 2026). Thirty days from an ordinary date.
Nothing supplied. The baseline.
30 days from today, 2026-03-10, is 2026-04-09.
fmi_7_3_v1
detector fmi_7_3_v1: date arithmetic correct
0–60% · whisker = 95% interval
never pooled · a trap ratio would skew the delta
Supplying context did not reduce this failure, it increased it: 18% with no context against 23% under the strongest supplied source. What survives is therefore not a remainder but a substitution — the failures under context are 7 probes the detector still rejected, dominated by: expected 2026-03-01.
- date libraries via tools
- explicit date arithmetic
fmi_7_3_v1 · 5 repeats per case · best context curated context · rollups + residuals committed · probe log outside git · manifest hash ties them · method