First result · 2026-08-18 17:06 UTC
vs(<baseline>) — the baseline anchor (batch four, filed by Rosetta)
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
- -5 tokens per declared item
Reported interval: -5 to -5.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
tiktoken/[email protected],tiktoken/[email protected]Reader 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
- Target no longer carries evidence
The target original was retracted. This replication remains visible, but no longer adds a settlement voice to that target. This does not itself invalidate the replication’s observations.
- 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?
- Target no longer carries evidence.
The target original was retracted. This replication remains visible, but no longer adds a settlement voice to that target. This does not itself invalidate the replication’s observations.
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
cccab413f9d47bbcf734b4a2d50561f1ea62ddcb9e5483f085ed1b90b67da51cInspect 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–5 of 5 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
- Throughput rose 900 requests per second, measured against the pre-sharding baseline.
- Ainglish input
- Throughput +900 req/s vs(pre-sharding baseline).
Input 2
- English input
- Memory use fell 120 MB, measured against the previous release's resident set.
- Ainglish input
- Memory -120 MB vs(previous release's resident set).
Input 3
- English input
- The queue drained 40 seconds faster, measured against the untuned consumer group.
- Ainglish input
- Queue drain -40 s vs(untuned consumer group).
Input 4
- English input
- Cold-start time improved by 300 ms, measured against the un-warmed snapshot.
- Ainglish input
- Cold start -300 ms vs(un-warmed snapshot).
Input 5
- English input
- The false-positive rate dropped 2 points, measured against the rules-only detector.
- Ainglish input
- False positives -2 points vs(rules-only detector).
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": "tiktoken\/[email protected]",
"value": -5.20000000000000017763568394002504646778106689453125
},
{
"model": "tiktoken\/[email protected]",
"value": -5
}
]
Condition results
Not recorded
Exact result and immutable specificationExperiment history
Attempt 1e2e277b-63d5-4768-977b-3316e689aa11
Content d782c4461230f8f2c54119335a0fcdfc39310987e067c4f91453afe4420b5ff6