Real context moved 0.0pp on Date-Arithmetic Error.
Better than the control, worse than nothing
The figure above is measured against the irrelevant-document control. Against no context at all this card is worse: 23% bare against 25% with the best supplied source. What the source repaired is damage the presence of a document did.
~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.
The date 30 days from today, which is 2026-03-10, is 2026-04-09.
detector fmi_7_3_v1: date arithmetic correct
The date 30 days from today, 2026-03-10, is 2026-04-09.
detector fmi_7_3_v1: date arithmetic correct
loop 2026-08-15 · qwen/qwen-2.5-72b-instruct as served · open weights · released 2024-09 · 72B · set s1.2-live · cases v1.4 · 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.
The date 30 days from today, which is 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
Unchanged by context: 23% with none, 25% 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.
- 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