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: 0% bare against 18% 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-01-30. What date is 30 days from today? Answer with the full date.
To find the date 30 days from January 30, 2026, we need to add 30 days to this date. Starting from January 30, 2026: - January has 31 days. So, from January 30 to January 31 is 1 day. - We need 29 more days to reach a total of 30 days. Adding 29 days to February 1, 2026: - February 2026 is not a leap year, so February has 28 days. - From February 1 to February 28 is 28 days. - We need 1 more day to reach 30 days. Adding 1 more day to February 28, 2026, brings us to March 1, 2026. Therefore, 30 days from January 30, 2026, is March 1, 2026.
detector fmi_7_3_v1: date arithmetic correct
To calculate the date 30 days from today, given that today's date is January 30, 2026, we need to add 30 days to this date. Starting from January 30, 2026: - January has 31 days, so there is 1 day remaining in January after the 30th. - Subtracting this 1 day from the 30 days we need to add leaves us with 29 more days to add. - February 2026 is not a leap year, so it has 28 days. Adding 28 days of February to the 1 day remaining in January covers the entire month of February, leaving us with 1 more day to add. - Adding this 1 day to March 1, 2026, gives us March 2, 2026. Therefore, 30 days from January 30, 2026, is March 2, 2026.
detector fmi_7_3_v1: date arithmetic correct
loop 2026-08-15 · microsoft/phi-4 as served · open weights · released 2024-12 · 14B · set s1.2-live · cases v1.4 · 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.
To find the date 30 days from January 30, 2026, we need to add 30 days to this date. Starting from January 30, 2026: - January has 31 days. So, from January 30 to January 31 is 1 day. - We need 29 more days to reach a total of 30 days. Adding 29 days to February 1, 2026: - February 2026 is not a leap year, so February has 28 days. - From February 1 to February 28 is 28 days. - We need 1 more day to reach 30 days. Adding 1 more day to February 28, 2026, brings us to March 1, 2026. Therefore, 30 days from January 30, 2026, is March 1, 2026.
fmi_7_3_v1
detector fmi_7_3_v1: date arithmetic correct
0–100% · whisker = 95% interval
never pooled · a trap ratio would skew the delta
Supplying context did not reduce this failure, it increased it: 0% with no context against 88% 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-08-23.
- 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