First result · 2026-09-02 16:08 UTC
passed≠applied
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
- -3 tokens per declared item
Reported interval: -3 to -3.Fewer tokens on the named current tokenizers; this is the encoded-length difference, not the proposal decision.
- English comparison
- Other declared comparison; inspect the specification
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_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
- Agrees with the named original
This eligible row adds one agreement to the named original’s settlement tally.
- 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?
- Agrees with the named original.
This replication reports -3 tokens; the named original reported -3.
This eligible row adds one agreement to the named original’s settlement tally.
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.
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
5a85132bc14d9860e642ed3503488d70d227c836389f86b1fbf7f7cc0b4b19d6Inspect 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 16 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
- The licensing change was accepted but not actually enacted or used.
- Ainglish input
- The licensing change is passed-not-applied.
Input 2
- English input
- The logging standard was accepted but not actually enacted or used.
- Ainglish input
- The logging standard is passed-not-applied.
Input 3
- English input
- The migration plan was accepted but not actually enacted or used.
- Ainglish input
- The migration plan is passed-not-applied.
Input 4
- English input
- The service-level objective was accepted but not actually enacted or used.
- Ainglish input
- The service-level objective is passed-not-applied.
Input 5
- English input
- The privacy exemption was accepted but not actually enacted or used.
- Ainglish input
- The privacy exemption is passed-not-applied.
Input 6
- English input
- The release freeze was accepted but not actually enacted or used.
- Ainglish input
- The release freeze is passed-not-applied.
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
Not recorded
Reader or tokenizer results
[
{
"model": "cl100k_base",
"value": -3
},
{
"model": "o200k_base",
"value": -3
}
]
Condition results
Not recorded
Exact result and immutable specificationExperiment history
Attempt 1facf230-9ee5-4d5c-915f-dad2e4dea040
Content e6ef6c3a594032e144a34777b3eb33a60a53f05f0a398eaf706c25c02ee413c2