First result · 2026-09-10 21:34 UTC
as_of(t) and until(t) — evidence epoch and claim expiry pins
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
- -16.375 tokens per declared item
Reported interval: -18 to -16.375.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
as_of,untilAn 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 |
|---|---|---|
as_of | -15.75 | Not recorded |
until | -17 | 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 · warehouse-inventory
- English input
- At 2026-09-10T18:00Z, the supporting observation was current and licensed the claim that warehouse inventory is complete; this makes no claim about later changes.
- Ainglish input
- Warehouse inventory is complete as_of(2026-09-10T18:00Z).
- Condition
- as_of
Input 2 · malware-scan
- English input
- At 2026-09-10T18:07Z, the supporting observation was current and licensed the claim that the malware scan is clean; this makes no claim about later changes.
- Ainglish input
- The malware scan is clean as_of(2026-09-10T18:07Z).
- Condition
- as_of
Input 3 · backup-restore
- English input
- At 2026-09-10T18:14Z, the supporting observation was current and licensed the claim that the backup is restorable; this makes no claim about later changes.
- Ainglish input
- The backup is restorable as_of(2026-09-10T18:14Z).
- Condition
- as_of
Input 4 · api-health
- English input
- At 2026-09-10T18:21Z, the supporting observation was current and licensed the claim that the payments api is healthy; this makes no claim about later changes.
- Ainglish input
- The payments API is healthy as_of(2026-09-10T18:21Z).
- Condition
- as_of
Input 5 · access-roster
- English input
- At 2026-09-10T18:28Z, the supporting observation was current and licensed the claim that the access roster is approved; this makes no claim about later changes.
- Ainglish input
- The access roster is approved as_of(2026-09-10T18:28Z).
- Condition
- as_of
Input 6 · invoice-ledger
- English input
- At 2026-09-10T18:35Z, the supporting observation was current and licensed the claim that the invoice ledger is reconciled; this makes no claim about later changes.
- Ainglish input
- The invoice ledger is reconciled as_of(2026-09-10T18:35Z).
- Condition
- as_of
Recorded input digest: d9bca83cfa7df045c138939aebc5b561feef40619452392ba3b17052af9c268d
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
- as_of(<t>)/until(<t>) versus the registered full careful-English evidence-epoch/claim-expiry meaning
- Tested population
- 24 frozen complete status reports across 24 domains, twelve evidence-epoch and twelve claim-expiry reports
- Unit tested
- one complete timestamp-bounded status report
- How results combine
- equal pair mean per tokenizer, then least-favourable maximum tokenizer mean; retain both forms 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": -17.958333333333332149095440399833023548126220703125
},
{
"model": "o200k_base",
"value": -18
},
{
"model": "p50k_base",
"value": -16.375
}
]
Condition results
[
{
"id": "as_of",
"weight": 1,
"share": 0.5,
"value": -15.75,
"value_lo": null,
"value_hi": null,
"arms": null,
"resolution_bound": "not_applicable"
},
{
"id": "until",
"weight": 1,
"share": 0.5,
"value": -17,
"value_lo": null,
"value_hi": null,
"arms": null,
"resolution_bound": "not_applicable"
}
]
Exact result and immutable specificationExperiment history
Attempt ed05f936-2e56-4ba4-a523-9ce397e43d00
Content df04c8267b486be13c1fb8550070bb144e0d25976deb296a884979409ef38614