These are literal recorded values, not a compatibility test. Matching declarations do not prove equivalent inputs or fair scoring. A missing structured field may be described elsewhere in the immutable specification.
What was measured · Same recorded value
First result
comprehension_accuracy_delta
Second result
comprehension_accuracy_delta
English comparison declarations · Recorded values differ
First result
[
"bare-failed-with-common-pinned-log-v1"
]
Second result
[
"complete-careful-english-v1"
]
Tested population · Not recorded on either side
First result
Not recorded in this structured field
Second result
Not recorded in this structured field
Unit tested · Not recorded on either side
First result
Not recorded in this structured field
Second result
Not recorded in this structured field
Named instruments (including order) · Same recorded value
Separate outcomes retained for all 2 declared conditions
verdict-fail, no-verdict
An overall average can hide a weak condition. A condition list is not proof that every form or claim in the proposal was tested.
Settlement role
Awaiting independent settlement
An original reports one result. It does not confirm itself.
How often did each version lead to the right answer?
English comparison
81.10%
81.10%
Ainglish version
90.70%
90.70%
Reported real-item accuracy, not the separate calibration score. Both bars use the same 0–100% scale. The difference is measured in percentage points, not percent improvement. Any declared stratum weights are already applied.
Reported item-bootstrap interval: 3.8179 to 15.7058 percentage points.
This interval concerns the difference, not separate uncertainty bounds for either accuracy. It does not measure uncertainty across humans or future models.
Real cases: 256 · Named readers: 2. These are different units; multiple answers to one case are not new cases.
Does the overall result hide differences between conditions?
Every stored condition, without new pooling. Differences and intervals use percentage points. Condition names come from the frozen experiment.
Condition
Reported difference
Reported interval
English accuracy
Ainglish accuracy
verdict-fail
1.8
Not recorded
84.25%
86.05%
no-verdict
17.4
Not recorded
77.95%
95.35%
A missing condition interval is not zero uncertainty. An overall interval cannot substitute for agreement in every load-bearing condition.
Inspect externally stored inputs and recorded answers
The comparison label is the submitter’s declaration, not a semantic certification. Check that both versions preserve the information needed to answer the same question.
Numbers count only readable inputs attached to this receipt. They are not the experiment’s declared sample size or the number of reader calls.
The input material is linked externally. The number of study items and controls in that file has not been checked by this website. “External file” does not mean zero inputs.
Declared input digest: 750d2327a6774ae032d4d82c1882499e7606e3924b84f3f8954462e9efae3cf6. A recorded digest alone does not establish that the linked file matches it.
The website does not fetch the file. Verify the declared digest recipe before relying on it: SDK item digests use canonical JSON of the item array, not the raw pretty-printed file bytes.
No readable study input pairs are stored inline in this receipt. This does not mean the experiment used none.
Prompts, reference material and other context can live elsewhere in the specification. Inputs and keys alone do not reconstruct every reader call or establish a fair comparison.
Declared population, method and retained outcomes
No structured study scope is declared here. Inspect the immutable manifest; do not infer a comparator or population from the headline.
Absolute arm results, reader-specific results and condition results below are retained values, not a newly pooled analysis. Accuracy arms use fractions from 0 to 1; their difference uses percentage points.
Separate outcomes retained for all 2 declared conditions
verdict-fail, no-verdict
An overall average can hide a weak condition. A condition list is not proof that every form or claim in the proposal was tested.
Settlement role
Awaiting independent settlement
An original reports one result. It does not confirm itself.
How often did each version lead to the right answer?
English comparison
97.25%
97.25%
Ainglish version
90.70%
90.70%
Reported real-item accuracy, not the separate calibration score. Both bars use the same 0–100% scale. The difference is measured in percentage points, not percent improvement. Any declared stratum weights are already applied.
Reported item-bootstrap interval: -10.5283 to -2.6532 percentage points.
This interval concerns the difference, not separate uncertainty bounds for either accuracy. It does not measure uncertainty across humans or future models.
At least one declared condition is resolution-limited. The overall interval does not settle every condition.
Real cases: 256 · Named readers: 2. These are different units; multiple answers to one case are not new cases.
Does the overall result hide differences between conditions?
Every stored condition, without new pooling. Differences and intervals use percentage points. Condition names come from the frozen experiment.
Condition
Reported difference
Reported interval
English accuracy
Ainglish accuracy
verdict-fail
-13.95
Not recorded
100.00%
86.05%
no-verdict
0.86
Not recorded
94.49%
95.35%
A missing condition interval is not zero uncertainty. An overall interval cannot substitute for agreement in every load-bearing condition.
Inspect externally stored inputs and recorded answers
The comparison label is the submitter’s declaration, not a semantic certification. Check that both versions preserve the information needed to answer the same question.
Numbers count only readable inputs attached to this receipt. They are not the experiment’s declared sample size or the number of reader calls.
The input material is linked externally. The number of study items and controls in that file has not been checked by this website. “External file” does not mean zero inputs.
Declared input digest: 927bcf9a7ad6bed3fac03b17c9b24dec5367823a61c4bf11c918cdab889053fb. A recorded digest alone does not establish that the linked file matches it.
The website does not fetch the file. Verify the declared digest recipe before relying on it: SDK item digests use canonical JSON of the item array, not the raw pretty-printed file bytes.
No readable study input pairs are stored inline in this receipt. This does not mean the experiment used none.
Prompts, reference material and other context can live elsewhere in the specification. Inputs and keys alone do not reconstruct every reader call or establish a fair comparison.
Declared population, method and retained outcomes
No structured study scope is declared here. Inspect the immutable manifest; do not infer a comparator or population from the headline.
Absolute arm results, reader-specific results and condition results below are retained values, not a newly pooled analysis. Accuracy arms use fractions from 0 to 1; their difference uses percentage points.
Different wording, readers, exposure or populations can legitimately produce different results. A visible reference is not training the model’s weights. Current models and tokenizers have learned English; future Ainglish-trained performance remains a research question.