First result · 2026-09-04 18:14 UTC
dispatched(<transport>) / delivered(<witness>) — say which transit event you witnessed, and who witnessed it
Counts in current evidence decisions. This row currently contributes to evidence decisions. Its direction is separate from whether the proposal is ready for adoption.
- What was measured
- comprehension accuracy ·
comprehension_accuracy_delta
How does the wording change correct answers from the declared reader panel? - Reported result
- 0 percentage points
Reported interval: 0 to 0.The value is neutral or does not resolve the registered direction.
- English comparison
- Complete, careful English
Declared by the submitter; not a certification of equivalent information.
Each compact form vs its complete careful-English meaning.
- Reader exposure
- Reader exposure not recorded as a structured label
- Named instruments
spark-zen-13-minimalReader population not separately declared.
- Conditions covered
- Separate outcomes retained for all 2 declared conditions
dispatched,deliveredAn 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
- Disagrees with the named original
This eligible row adds one disagreement. An adverse or null direction is a valid result and remains visible.
This result checks a named original, not every experiment on the proposal. Read its target original
Compare with the exact target attempt
Every declared condition must agree. Overlapping overall intervals alone do not confirm this original.
How much input text was reused?
Complete-pair freshness is not available for this receipt.
Separate-arm overlap is unavailable or has not been computed. This does not mean zero reuse.
Exact text comparisons only; repeated occurrences count separately. Shared text can deserve scrutiny even when each complete pair is new. These arm counts are descriptive and do not change settlement eligibility.
Declared target content identity
39a511cf82362e44c1ebb56eb945f615c245d50e1f65a0aa62dc0c91c45e5ff3How often did each version lead to the right answer?
- English comparison
- 100.00%
100.00% - Ainglish version
- 100.00%
100.00%
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: 0 to 0 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: 12 · Named readers: 1. These are different units; multiple answers to one case are not new cases.
Does the overall result hide differences between conditions?
| Condition | Reported difference | Reported interval | English accuracy | Ainglish accuracy |
|---|---|---|---|---|
dispatched | 0 | Not recorded | 100.00% | 100.00% |
delivered | 0 | Not recorded | 100.00% | 100.00% |
A missing condition interval is not zero uncertainty. An overall interval cannot substitute for agreement in every load-bearing condition.
Inspect actual 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.
Showing 1–6 of 12 readable, inline study items, in stored order—not a selection of successes. 4 control items are kept separate.
Each result has its own input pages. Positions across the two studies do not imply matched cases.
Input 5 · disp-01
- English input
- manifest M was accepted by transport lane-teal for sending for transfer 11; this does not establish that the destination received it.
- Ainglish input
- dispatched(lane-teal): manifest M for transfer 11.
- Question
- What does the message establish?
- Recorded answer options
the destination received the payload·the payload was rejected before sending·both dispatch and receipt are established·the transport accepted the payload for sending; receipt is not established- Submitted answer key
- the transport accepted the payload for sending; receipt is not established. This is the supplied key, not an independent validation of it.
- Condition
- dispatched
Filed correctness against that key (up to 12 reader/arm cells). These flags are not the reader’s verbatim output.
spark-zen-13-minimal· Ainglish: matched the submitted key.
Input 6 · disp-02
- English input
- parcel P was accepted by transport courier-ochre for sending for transfer 12; this does not establish that the destination received it.
- Ainglish input
- dispatched(courier-ochre): parcel P for transfer 12.
- Question
- What does the message establish?
- Recorded answer options
the transport accepted the payload for sending; receipt is not established·the destination received the payload·the payload was rejected before sending·both dispatch and receipt are established- Submitted answer key
- the transport accepted the payload for sending; receipt is not established. This is the supplied key, not an independent validation of it.
- Condition
- dispatched
Filed correctness against that key (up to 12 reader/arm cells). These flags are not the reader’s verbatim output.
spark-zen-13-minimal· English: matched the submitted key.
Input 7 · disp-03
- English input
- backup B was accepted by transport relay-ash for sending for transfer 13; this does not establish that the destination received it.
- Ainglish input
- dispatched(relay-ash): backup B for transfer 13.
- Question
- What does the message establish?
- Recorded answer options
the payload was rejected before sending·both dispatch and receipt are established·the transport accepted the payload for sending; receipt is not established·the destination received the payload- Submitted answer key
- the transport accepted the payload for sending; receipt is not established. This is the supplied key, not an independent validation of it.
- Condition
- dispatched
Filed correctness against that key (up to 12 reader/arm cells). These flags are not the reader’s verbatim output.
spark-zen-13-minimal· English: matched the submitted key.
Input 8 · disp-04
- English input
- patch Q was accepted by transport queue-jade for sending for transfer 14; this does not establish that the destination received it.
- Ainglish input
- dispatched(queue-jade): patch Q for transfer 14.
- Question
- What does the message establish?
- Recorded answer options
the transport accepted the payload for sending; receipt is not established·the destination received the payload·the payload was rejected before sending·both dispatch and receipt are established- Submitted answer key
- the transport accepted the payload for sending; receipt is not established. This is the supplied key, not an independent validation of it.
- Condition
- dispatched
Filed correctness against that key (up to 12 reader/arm cells). These flags are not the reader’s verbatim output.
spark-zen-13-minimal· English: matched the submitted key.
Input 9 · disp-05
- English input
- report R was accepted by transport bus-slate for sending for transfer 15; this does not establish that the destination received it.
- Ainglish input
- dispatched(bus-slate): report R for transfer 15.
- Question
- What does the message establish?
- Recorded answer options
both dispatch and receipt are established·the transport accepted the payload for sending; receipt is not established·the destination received the payload·the payload was rejected before sending- Submitted answer key
- the transport accepted the payload for sending; receipt is not established. This is the supplied key, not an independent validation of it.
- Condition
- dispatched
Filed correctness against that key (up to 12 reader/arm cells). These flags are not the reader’s verbatim output.
spark-zen-13-minimal· Ainglish: matched the submitted key.
Input 10 · disp-06
- English input
- bundle S was accepted by transport mesh-pearl for sending for transfer 16; this does not establish that the destination received it.
- Ainglish input
- dispatched(mesh-pearl): bundle S for transfer 16.
- Question
- What does the message establish?
- Recorded answer options
the payload was rejected before sending·both dispatch and receipt are established·the transport accepted the payload for sending; receipt is not established·the destination received the payload- Submitted answer key
- the transport accepted the payload for sending; receipt is not established. This is the supplied key, not an independent validation of it.
- Condition
- dispatched
Filed correctness against that key (up to 12 reader/arm cells). These flags are not the reader’s verbatim output.
spark-zen-13-minimal· Ainglish: matched the submitted key.
Recorded input digest: 6d783a584a95b520001ebaef95803abd4991ff5fbb8bd9e558062505b7f90cc2
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.
Absolute arm results
{
"english": 1,
"ainglish": 1,
"chance": 0.25
}
Reader or tokenizer results
[
{
"model": "spark-zen-13-minimal",
"value": 0
}
]
Condition results
[
{
"id": "dispatched",
"weight": 1,
"share": 0.5,
"value": 0,
"value_lo": null,
"value_hi": null,
"arms": {
"english": 1,
"ainglish": 1,
"chance": 0.25
},
"resolution_bound": "ceiling"
},
{
"id": "delivered",
"weight": 1,
"share": 0.5,
"value": 0,
"value_lo": null,
"value_hi": null,
"arms": {
"english": 1,
"ainglish": 1,
"chance": 0.25
},
"resolution_bound": "ceiling"
}
]
Exact result and immutable specificationExperiment history
Attempt 9decb5f5-dca8-4ce2-9824-e51f62f2980f
Content 3689e7d1cb139ef5ce16ea038042a001e8ac210fbd541154ad7af89dfaf74b6f