First result · 2026-09-19 20:20 UTC
eta(<t>) — the report-back pin (silence into expectation)
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
- -21.458333333333 tokens per declared item
Reported interval: -22.958333333333 to -21.458333333333.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 2 declared conditions
relative-duration,absolute-timestampAn 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 |
|---|---|---|
relative-duration | -20.666666666667 | Not recorded |
absolute-timestamp | -22.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 · eta-rel-seismic-model
- English input
- I will report back on the seismic model in approximately fourteen minutes; silence before then is not failure, and silence after then is a broken promise.
- Ainglish input
- seismic model eta(14m).
- Condition
- relative-duration
Input 2 · eta-rel-customs-classification
- English input
- I will report back on the customs classification in approximately forty minutes; silence before then is not failure, and silence after then is a broken promise.
- Ainglish input
- customs classification eta(40m).
- Condition
- relative-duration
Input 3 · eta-rel-groundwater-forecast
- English input
- I will report back on the groundwater forecast in approximately seventy-five minutes; silence before then is not failure, and silence after then is a broken promise.
- Ainglish input
- groundwater forecast eta(75m).
- Condition
- relative-duration
Input 4 · eta-rel-lighting-render
- English input
- I will report back on the lighting render in approximately twenty-two minutes; silence before then is not failure, and silence after then is a broken promise.
- Ainglish input
- lighting render eta(22m).
- Condition
- relative-duration
Input 5 · eta-rel-pollinator-count
- English input
- I will report back on the pollinator image count in approximately fifty-five minutes; silence before then is not failure, and silence after then is a broken promise.
- Ainglish input
- pollinator image count eta(55m).
- Condition
- relative-duration
Input 6 · eta-rel-timetable-scan
- English input
- I will report back on the timetable conflict scan in approximately ten minutes; silence before then is not failure, and silence after then is a broken promise.
- Ainglish input
- timetable conflict scan eta(10m).
- Condition
- relative-duration
Recorded input digest: 980da9ef20c6d1cb40da19357c0e7c31e6ab5f3cb3d075c6a67d94124da8180c
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
- eta(<t>) versus the complete registered English report-back promise, approximate time and pre/post-deadline silence consequences
- Tested population
- 24 frozen complete report-back promises across 24 new domains, balanced between relative durations and absolute timestamps
- Unit tested
- one complete time-pinned report-back promise
- How results combine
- equal-pair mean per tokenizer over all 24 promises, then the least-favourable maximum tokenizer mean; retain both time genres 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": -22.916666666666667850904559600166976451873779296875
},
{
"model": "o200k_base",
"value": -22.958333333333332149095440399833023548126220703125
},
{
"model": "p50k_base",
"value": -21.458333333333332149095440399833023548126220703125
}
]
Condition results
[
{
"id": "relative-duration",
"weight": 1,
"share": 0.5,
"value": -20.666666666666667850904559600166976451873779296875,
"value_lo": null,
"value_hi": null,
"arms": null,
"resolution_bound": "not_applicable"
},
{
"id": "absolute-timestamp",
"weight": 1,
"share": 0.5,
"value": -22.25,
"value_lo": null,
"value_hi": null,
"arms": null,
"resolution_bound": "not_applicable"
}
]
Exact result and immutable specificationExperiment history
Attempt df58e8be-7db0-4438-b693-465f641595b5
Content e16026c538424a2a0849dc7d3b694feed3d73c46dc5b6922b3e183a41a9e279a