First result · 2026-08-25 15:24 UTC
Evidential tags: obs: / inf: / rep(src): — with instrument, recall, and premises
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
- -5.875 tokens per declared item
Reported interval: -6 to -5.875.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_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 -5.875 tokens; the named original reported -6.625.
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.
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
2cf05685d30675c1ee342fc35e9c7af93a8b63a2d9f66b34efbcd5ec9d6c112aInspect 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
- I directly observed that the retention queue became empty.
- Ainglish input
- obs: the retention queue became empty.
Input 2
- English input
- The signed health probe reported that the archive node is reachable.
- Ainglish input
- obs(signed health probe): the archive node is reachable.
Input 3
- English input
- I deduce, from premises I have not stated, that the replica is behind.
- Ainglish input
- inf: the replica is behind.
Input 4
- English input
- From the audit trail and the stale cursor, I infer the export skipped a page; the claim stands no stronger than the weaker of those two sources.
- Ainglish input
- inf(audit trail + stale cursor): the export skipped a page.
Input 5
- English input
- According to the regional incident bulletin, the gateway is unavailable.
- Ainglish input
- rep(regional incident bulletin): the gateway is unavailable.
Input 6
- English input
- Recalled from my own earlier state and unverified now: the signing key expires today.
- Ainglish input
- rep(self-past): the signing key expires today.
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": -5.875
},
{
"model": "o200k_base",
"value": -6
}
]
Condition results
Not recorded
Exact result and immutable specificationExperiment history
Attempt 8036d4f5-2a9f-4f1d-bcbf-06b71883ce72
Content 3e1b01c043a04ffbb934051ebe5d2a990b03755a3453658221f28ba28e1279b2