First result · 2026-09-17 16:06 UTC
include-both / include-start-only / include-end-only / exclude-both — make range endpoints explicit
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
- token cost ·
token_delta
How does the wording change tokenizer units for the declared tokenizer population? - Reported result
- 1.25 tokens per declared item
Reported interval: 0.25 to 1.25.More 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
- No condition-by-condition settlement contract recorded
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
- Disagrees with the named original
This eligible row adds one disagreement. An adverse or null direction is a valid result and remains visible.
- 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?
- Disagrees with the named original.
This replication reports 1.25 tokens; the named original reported 1.125.
This eligible row adds one disagreement. An adverse or null direction is a valid result and remains visible.
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.
This result checks a named original, not every experiment on the proposal. Read its target original
Compare with the exact target attempt
How much input text was reused?
100.0% of complete English–Ainglish pairs are fresh.
- 0 of 8 English inputs reuse text from either side of the original.
- 0 of 8 Ainglish inputs reuse text from either side of the original.
Declared item-bank digests: different. This compares bank identity, not shared sentences; different bank digests can still contain identical pairs.
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
e5274f09c6700c8ce9d3908908f8472353bbf5abf308ef62bdcbbe0f08449b1cInspect 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 8 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
- English input
- Export invoices 710 up to but not including 760.
- Ainglish input
- Export invoices 710 to 760, include-start-only.
Input 2
- English input
- Monitor from 14 March inclusive to 19 March exclusive.
- Ainglish input
- Monitor 14 March to 19 March, include-start-only.
Input 3
- English input
- Staff shifts Wednesday through Sunday, both days included.
- Ainglish input
- Staff shifts Wednesday to Sunday, include-both.
Input 4
- English input
- Allow ports 9100 through 9140, including both ends.
- Ainglish input
- Allow ports 9100 to 9140, include-both.
Input 5
- English input
- Migrate versions after 7.2 up to and including 7.8.
- Ainglish input
- Migrate versions 7.2 to 7.8, include-end-only.
Input 6
- English input
- Charge for kilometres above 55 and up to and including 90.
- Ainglish input
- Charge for kilometres 55 to 90, include-end-only.
Recorded input digest: 5de498d510503b3f7b4d2b3cff3f7715d8bfddafa84804a743a98ca030efb775
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
- range with one endpoint qualifier versus the shortest careful English stating both endpoint memberships
- Tested population
- eight fresh two-endpoint range instructions across records, dates, confidence, versions, distances, ports and temperatures, two per qualifier
- Unit tested
- complete range instruction sentence
- How results combine
- maximum tokenizer mean
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": 0.25
},
{
"model": "o200k_base",
"value": 0.25
},
{
"model": "p50k_base",
"value": 1.25
}
]
Condition results
Not recorded
Exact result and immutable specificationExperiment history
Attempt 2a68d1cb-2632-4a71-b47e-526b28d67ffc
Content 62e45602414331be60e0726180ceb1ca9b5bf4dcc50d463eea55c4e8a97a32ce