ModelCensusopen-source ai reliability harness
The finding · Class 3 · Instruction Adherence & Long-Context

Real context moved 10.0pp on Cross-Turn Schema Validity.

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 10% with the best supplied source. What the source repaired is damage the presence of a document did.

~intervals overlap — not separated from no change

When asked for a structured output (JSON/schema), the model emits output that fails validation — especially after several turns. The rule

google/gemini-2.5-flashfmi_3_35 repeatsfmi_3_3_v1
The modeAll 10 cards
In one frame
screenshot this
Cross-Turn Schema Validityfmi_3_3
google/gemini-2.5-flash
Same question, both times
Return a JSON object for a fictional person with fields name (string), age (integer), email (string).
No contextPASS

```json { "name": "Melody Harmon", "age": 30, "email": "melody.h@example.com" } ```

detector fmi_3_3_v1: all turns produced schema-valid JSON

General contextPASS

```json { "name": "Charlie Parker", "age": 34, "email": "charlie.parker@example.com" } ```

detector fmi_3_3_v1: all turns produced schema-valid JSON

Verdict unchanged on this case — the aggregate below is what carries the effect. Across 5 repeats: +10.0pp (intervals overlap).fmi_3_3_v1 · google/gemini-2.5-flash · 2026-08-15 · ground truth as of 2026-08-09

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

From no context to real context
5 repeats per case
failure rate · left is fewer failures0%10%20%30%40%No context0%[0%–16%] n=20Irrelevant context0%presence — a document being there[0%–16%] n=200.0pp OVERLAPSGeneral context10%content — the information itself[3%–30%] n=20+10.0pp OVERLAPS
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 3 turns. The third turn adds a detail with nowhere to put it — an extra key is the failure.

2Contextchange me

Nothing supplied. The baseline.

3ResponseNo context
PASS

```json { "name": "Melody Harmon", "age": 30, "email": "melody.h@example.com" } ```

fmi_3_3_v1

detector fmi_3_3_v1: all turns produced schema-valid JSON

The scoring
Failure rate by context
No context0% [0%–16%] n=20
Irrelevant context0% [0%–16%] n=20
General context10% [3%–30%] n=20
Curated context15% [5%–36%] n=20

0–60% · whisker = 95% interval

Trap vs answerable
No contexttrap 0%answerable 0%
Irrelevant contexttrap 0%answerable 0%
General contexttrap 20%answerable 0%
Curated contexttrap 30%answerable 0%

never pooled · a trap ratio would skew the delta

Residual — what survives

Supplying context did not reduce this failure, it increased it: 0% with no context against 15% under the strongest supplied source. What survives is therefore not a remainder but a substitution — the failures under context are 2 probes the detector still rejected, dominated by: 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 general context · rollups + residuals committed · probe log outside git · manifest hash ties them · method