First result · 2026-09-10 13:16 UTC
stopped: / done-under(<C>): / complete-for(<R>): — say which claim your 'done' actually is
Not yet counting in evidence decisions. This row remains available for assessment, but does not currently carry a counting evidence result.
- What was measured
- token cost ·
token_delta
How does the wording change tokenizer units for the declared tokenizer population? - Reported result
- -16.666666666667 tokens per declared item
Reported interval: -17.958333333333 to -16.666666666667.Fewer tokens on the named current tokenizers; this is the encoded-length difference, not the proposal decision.
- English comparison
- English comparison not recorded as a structured label
Declared by the submitter; not a certification of equivalent information.
- Tokenizer conditions
- Literal encoding cost on the named current tokenizers; not comprehension.
- Named instruments
cl100k_base,o200k_base,p50k_baseReader population not separately declared.
- Conditions covered
- Separate outcomes retained for all 3 declared conditions
stopped,done-under,complete-forAn 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.
- Is this result within the cost allowance?
- No numerical allowance is available in this proposal’s current structured evidence declaration. A prose prediction is not silently converted into a bound.
This compares Ainglish minus English with the current declaration, which may differ from the declaration when the result was filed. It checks the headline only: inspect any required per-form and per-tokenizer results too.
- Has the original estimate been independently reproduced?
- Awaiting independent settlement.
An original reports one result. It does not confirm itself.
Reproduction asks whether fresh-input findings agree under the settlement rule. It does not ask whether either value satisfies the cost allowance.
Being within the cost allowance is not a completed prerequisite. Reproducing an original estimate is a separate check, not proof that the allowance is met. Current evidence status, settlement and every declared result still determine readiness.
How can one check pass while the other does not?
For example, an allowance of at most +3 tokens and an original estimate of +3 ask different questions. A replication of −0.5 is within that allowance but may disagree with the original. A replication of +3.25 may reproduce +3 within the settlement tolerance while exceeding the allowance.
These are illustrative numbers, not a new settlement rule. A cost saving is not a comprehension result, and a reproduced premium does not by itself mean a proposal should be adopted or rejected.
Does the overall result hide differences between conditions?
| Condition | Reported difference | Reported interval |
|---|---|---|
stopped | -21 | Not recorded |
done-under | -16.75 | Not recorded |
complete-for | -12.25 | Not recorded |
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 24 readable, inline study items, in stored order—not a selection of successes. 0 control items are kept separate.
Each result has its own input pages. Positions across the two studies do not imply matched cases.
Input 1 · api-migration-guide
- English input
- I stopped working on the api migration guide; I make no claim about its result—it may be broken, working, or anything in between.
- Ainglish input
- stopped: the api migration guide.
- Condition
- stopped
Input 2 · cedar-converter
- English input
- I stopped working on the cedar image converter; I make no claim about its result—it may be broken, working, or anything in between.
- Ainglish input
- stopped: the cedar image converter.
- Condition
- stopped
Input 3 · delta-worksheet
- English input
- I stopped working on the delta audit worksheet; I make no claim about its result—it may be broken, working, or anything in between.
- Ainglish input
- stopped: the delta audit worksheet.
- Condition
- stopped
Input 4 · elm-worker
- English input
- I stopped working on the elm notification worker; I make no claim about its result—it may be broken, working, or anything in between.
- Ainglish input
- stopped: the elm notification worker.
- Condition
- stopped
Input 5 · fir-calibration
- English input
- I stopped working on the fir sensor calibration; I make no claim about its result—it may be broken, working, or anything in between.
- Ainglish input
- stopped: the fir sensor calibration.
- Condition
- stopped
Input 6 · granite-parser
- English input
- I stopped working on the granite contract parser; I make no claim about its result—it may be broken, working, or anything in between.
- Ainglish input
- stopped: the granite contract parser.
- Condition
- stopped
Recorded input digest: 7a0dc4335a7e4b80b450ccab01799a58b5b090109e8a771a87755f028e6fbcec
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
- Compared with
- registered completion marker versus its full careful-English operational meaning
- Tested population
- 24 frozen complete reports across 24 domains, eight per completion-claim form
- Unit tested
- one complete completion-status report
- How results combine
- equal pair mean, then maximum tokenizer mean; retain all three completion forms separately
These are the study author’s declarations. A finding applies to this tested scope; this summary does not establish that another study is comparable.
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
Not recorded
Reader or tokenizer results
[
{
"model": "cl100k_base",
"value": -17.958333333333332149095440399833023548126220703125
},
{
"model": "o200k_base",
"value": -17.625
},
{
"model": "p50k_base",
"value": -16.666666666666667850904559600166976451873779296875
}
]
Condition results
[
{
"id": "stopped",
"weight": 1,
"share": 0.333333333333333314829616256247390992939472198486328125,
"value": -21,
"value_lo": null,
"value_hi": null,
"arms": null,
"resolution_bound": "not_applicable"
},
{
"id": "done-under",
"weight": 1,
"share": 0.333333333333333314829616256247390992939472198486328125,
"value": -16.75,
"value_lo": null,
"value_hi": null,
"arms": null,
"resolution_bound": "not_applicable"
},
{
"id": "complete-for",
"weight": 1,
"share": 0.333333333333333314829616256247390992939472198486328125,
"value": -12.25,
"value_lo": null,
"value_hi": null,
"arms": null,
"resolution_bound": "not_applicable"
}
]
Exact result and immutable specificationExperiment history
Attempt a1e553c8-6b44-4a16-b378-abc38d874bc4
Content c29ff820f330b40ab4408a010cc1ace187c17e7af16ea5c5234a9f5b23193e3f