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.
Today's date is 2026-01-30. To find the date 30 days from today, we add 30 days to January 30, 2026. January has 31 days. Number of days remaining in January = 31 - 30 = 1 day. So, 1 day into the 30 days takes us to January 31, 2026. Remaining days to count = 30 - 1 = 29 days. These 29 days will fall into the next month, which is February. So, 29 days from January 31, 2026, is February 29, 2026. The year 2026 is not a leap year (a leap year occurs every 4 years, except for years divisible by 100 but not by 400). Since 2026 is not divisible by 4, February 2026 has 28 days. Let's re-calculate: Start date: 2026-01-30 Days in January: 31 Days remaining in January: 31 - 30 = 1 day. So, 1 day from 2026-01-30 is 2026-01-31. Remaining days to add: 30 - 1 = 29 days. These 29 days will be in February. Since 2026 is not a leap year, February has 28 days. So, adding 28 days to January 31, 2026, takes us to February 28, 2026. We still need to add 1 more day (29 - 28 = 1). Adding 1 more day to February 28, 2026, takes us to March 1, 2026. The final answer is $\boxed{2026-03-01}$
detector fmi_7_3_v1: date arithmetic correct
2026-03-01
detector fmi_7_3_v1: date arithmetic correct
loop 2026-08-15 · google/gemini-2.5-flash as served · closed weights · released 2025-06 · 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.
Today's date is 2026-01-30. To find the date 30 days from today, we add 30 days to January 30, 2026. January has 31 days. Number of days remaining in January = 31 - 30 = 1 day. So, 1 day into the 30 days takes us to January 31, 2026. Remaining days to count = 30 - 1 = 29 days. These 29 days will fall into the next month, which is February. So, 29 days from January 31, 2026, is February 29, 2026. The year 2026 is not a leap year (a leap year occurs every 4 years, except for years divisible by 100 but not by 400). Since 2026 is not divisible by 4, February 2026 has 28 days. Let's re-calculate: Start date: 2026-01-30 Days in January: 31 Days remaining in January: 31 - 30 = 1 day. So, 1 day from 2026-01-30 is 2026-01-31. Remaining days to add: 30 - 1 = 29 days. These 29 days will be in February. Since 2026 is not a leap year, February has 28 days. So, adding 28 days to January 31, 2026, takes us to February 28, 2026. We still need to add 1 more day (29 - 28 = 1). Adding 1 more day to February 28, 2026, takes us to March 1, 2026. The final answer is $\boxed{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: 3% 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