Real context moved -12.5pp on Ledger Reconciliation Failure.
~intervals overlap — not separated from no change
Across a sequence of state-changing tool calls, the model's running account of state diverges from what the calls actually produced. The rule
Starting balance 0 USD; +1200 (opening deposit), -1200 (transfer out), -15.25 (wire fee), +15.25 (fee reversal). What is the final balance?
1. 0 + 1200 = 1200 USD 2. 1200 - 1200 = 0 USD 3. 0 - 15.25 = -15.25 USD 4. -15.25 + 15.25 = 0 USD Answer: 0
detector fmi_6_5_v1: balance reconciles
1. 0 USD + 1200 USD = 1200 USD 2. 1200 USD - 1200 USD = 0 USD 3. 0 USD - 15.25 USD = -15.25 USD 4. -15.25 USD + 15.25 USD = 0 USD Answer: 0
detector fmi_6_5_v1: balance reconciles
loop 2026-08-15 · google/gemini-2.5-flash as served · closed weights · released 2025-06 · set s1.3-live · cases v1.6 · conditions v1.0 · ground truth as of 2026-08-09
Starting balance 0 USD; +1200 (opening deposit), -1200 (transfer out), -15.25 (wire fee), +15.25 (fee reversal). What is the final balance?
expected as of 2026-08-09
0 USD. Nets to zero, and the reversal is easy to drop.
Nothing supplied. The baseline.
1. 0 + 1200 = 1200 USD 2. 1200 - 1200 = 0 USD 3. 0 - 15.25 = -15.25 USD 4. -15.25 + 15.25 = 0 USD Answer: 0
fmi_6_5_v1
detector fmi_6_5_v1: balance reconciles
0–40% · 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.
- external state tracking
- reconcile before reporting
fmi_6_5_v1 · 5 repeats per case · best context general context · rollups + residuals committed · probe log outside git · manifest hash ties them · method