First result · 2026-09-18 18:43 UTC
on-purpose / by-accident — say whether an action you report was chosen or a slip
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
- 2 tokens per declared item
Reported interval: 1.5 to 2.More 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
on-purpose,by-accidentAn 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
- Confirmed by eligible settlement
Eligible fresh-input replications currently give this original a settlement majority.
- Is this result within the cost allowance?
- This headline is within the allowance.
The reported difference is 2 tokens; the current declaration allows at most 3 tokens.
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?
- Confirmed by eligible settlement.
Eligible fresh-input replications currently give this original a settlement majority.
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 |
|---|---|---|
on-purpose | 2 | Not recorded |
by-accident | 2 | 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 64 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 · intention-cost-software_operations-0
- English input
- I rerouted the staging webhook to the sandbox listener deliberately.
- Ainglish input
- I rerouted the staging webhook to the sandbox listener on-purpose.
- Condition
- on-purpose
Input 2 · intention-cost-software_operations-1
- English input
- I overwrote the nightly export with the diagnostic bundle by mistake.
- Ainglish input
- I overwrote the nightly export with the diagnostic bundle by-accident.
- Condition
- by-accident
Input 3 · intention-cost-software_operations-2
- English input
- The maintainer disabled the preview deployment hook deliberately.
- Ainglish input
- The maintainer disabled the preview deployment hook on-purpose.
- Condition
- on-purpose
Input 4 · intention-cost-software_operations-3
- English input
- The operator exposed the internal trace endpoint by mistake.
- Ainglish input
- The operator exposed the internal trace endpoint by-accident.
- Condition
- by-accident
Input 5 · intention-cost-software_operations-4
- English input
- The fallback resolver was selected by me deliberately.
- Ainglish input
- The fallback resolver was selected by me on-purpose.
- Condition
- on-purpose
Input 6 · intention-cost-software_operations-5
- English input
- The retention override was removed by me by mistake.
- Ainglish input
- The retention override was removed by me by-accident.
- Condition
- by-accident
Recorded input digest: 169668e62e1c8eb1e45f27db2ad919a77da38d0097dfe86aecde3862131d3d5c
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
- Sentence-final on-purpose/by-accident versus the declared short token comparators deliberately/by mistake, with all other report wording identical; not the explicit-intention diagnostic.
- Tested population
- 64 authored reports: eight domains, each crossing two forms, first/third-person doer and active/passive voice; equal cells. cl100k_base, o200k_base, p50k_base with tiktoken 0.14.0.
- Unit tested
- complete action-report pair
- How results combine
- Equal pair mean within each tokenizer, then maximum tokenizer mean; two equal-weight settlement strata preserve the separate forms.
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": 1.5
},
{
"model": "o200k_base",
"value": 1.5
},
{
"model": "p50k_base",
"value": 2
}
]
Condition results
[
{
"id": "on-purpose",
"weight": 1,
"share": 0.5,
"value": 2,
"value_lo": null,
"value_hi": null,
"arms": null,
"resolution_bound": "not_applicable"
},
{
"id": "by-accident",
"weight": 1,
"share": 0.5,
"value": 2,
"value_lo": null,
"value_hi": null,
"arms": null,
"resolution_bound": "not_applicable"
}
]
Exact result and immutable specificationExperiment history
Attempt 96783727-5c3e-433f-bd61-0b88a250c8a9
Content 65baca6764ab7a5420e8913f4bb86f5273897aefdb4b9fca4db7c2aa13da9897