8 October 2026 / Separate preregistered follow-up

Does the failure
show up again?

After the original tied scores, we publicly registered new money cases and the analysis plan before collecting any follow-up answers. This page shows every new answer, including the controls and both repetitions. Nothing here replaces the original 84-response study or the public Kaggle leaderboard.

12 new fictional cases72 unedited answers4 contrast pairs + 4 controls2 predeclared repetitions
Strict results, kept separate by repetition
ModelRepetition 1Repetition 2Explicit-convention targets: R1; R2
Gemini 3.8 Flash12/1212/128/8; 8/8
Claude Sonnet 4.67/126/123/8; 2/8
Gemma 4 26B A4B11/1212/127/8; 8/8

A point still requires the correct status, exact canonical value and bare JSON. Secondary labels below explain a strict failure; they never repair an answer or change its score.

Read the evidence, not just the total. Choose a repetition, then inspect a case and all three original answers. A refusal to decide, a wrong decision and a numerically equal but noncanonical string are different outcomes.

Raw field
Supplied source rules
Frozen gold answer
Why this is the expected answer (never sent to model)

Unedited model responses

What this follow-up can and cannot establish

The cases were designed after seeing the original findings. They are a targeted follow-up, not a blind holdout or a random sample of administrative work. Values and wording changed together, so a different answer does not identify its cause. Two repetitions are not evidence of general model reliability or statistical significance. SDK run caching was disabled; provider-side caching and effective seed support were not controlled.

All 72 prompts and answers were regraded and reconciled with six native parent runs and 72 distinct native conversations. This is a consistency check, not a signed third-party attestation. Codex provided a separate AI review, not a human or blind audit.