detector fmi_3_3_v1: all turns produced schema-valid JSON
loop 2026-08-15 · mistralai/mistral-small-3.2-24b-instruct as served · open weights · released 2025-06 · 24B · set s1.3-live · cases v1.6 · conditions v1.0 · ground truth as of 2026-08-09
From no context to real context
5 repeats per case
whiskers are 95% intervals · each step is measured from the stop before it, not from zero
Try the other contexts
stored · no model call
1Questionheld fixed
Return a JSON object for a fictional person with fields name (string), age (integer), email (string).
expected as of 2026-08-09
Schema-valid JSON on all 2 turns. Two turns, one shape. The second turn is where drift starts.
detector fmi_3_3_v1: all turns produced schema-valid JSON
The scoring
Failure rate by context
No context50%[18%–82%] n=20 · eff 6
Irrelevant context35%[10%–72%] n=20 · eff 6
General context40%[13%–76%] n=20 · eff 6
Curated context25%[6%–65%] n=20 · eff 6
0–100% · whisker = 95% interval
Trap vs answerable
No contexttrap 100%answerable 0%
Irrelevant contexttrap 70%answerable 0%
General contexttrap 80%answerable 0%
Curated contexttrap 50%answerable 0%
never pooled · a trap ratio would skew the delta
Residual — what survives
50% with no context, 25% under the best supplied source. What survives is 5 failing probes at that best condition, the detector's reason on most of them being: turn 3: data must NOT have additional properties.
Mitigations from the index — the claim
—schema-constrained decoding
—validate-and-repair loops
fmi_3_3_v1 · 5 repeats per case · best context curated context · rollups + residuals committed · probe log outside git · manifest hash ties them · method