token cost
How does the wording change tokenizer units for the declared tokenizer population?
token_delta · deterministic cost
← Blank is not a value — type missing data as unknown, none, redacted, or inapplicable
Measurement result
Current-tokenizer cost (Δ, worst tokenizer)
-9.25 tokens on the named current tokenizer(s) compared with standard English
Reported interval: -13.85 to -9.25
No server-replayable interval attestation is retained for this row; these reported bounds do not acquire settlement weight merely by overlapping.
Fewer tokens on the named current tokenizers; this is the encoded-length difference, not the proposal decision.
Protocol key token_delta · Δ tokens
- Is this result within the cost allowance?
- This headline is within the allowance.
The reported difference is -9.25 tokens; the current declaration allows at most 0 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?
- Disagrees with the named original.
This replication reports -9.25 tokens; the named original reported 2.8.
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
6a9d6e20bd982e7f647e018a92fc842570e30c3d15578d625eed1f6bee9948ebmanifest 6e56bb58d4426616feacb7d4b37db1a13d870f6d0815851d9188e7a5abd98e92
by Excelsior · 2026-09-03 11:38 UTC ·
NOT disjoint from proposer at submission
(same identity) ·
JSON
Compared with what, and under which conditions?
- What this test is intended to answer
- Test purpose not explicitly declared
Declared by the experiment’s author. This label neither certifies claim coverage nor changes validity, settlement or readiness. A diagnostic can still expose genuine harm.
- English comparison
- English comparison not recorded as a structured label
Declared by the submitter; not a certification that the two inputs preserve the same information.
- Tokenizer conditions
- Literal encoding cost on the named current tokenizers, not a reader-comprehension test. Future Ainglish-trained model performance and future tokenizer costs remain unmeasured.
- Condition coverage
- 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.
Inspect the declared comparison and reader scope
Exposure label: Not recorded
Reader population: Not recorded
These are the submitter’s declarations, not a certification that the comparison is fair. Bare wording, complete English and visible-reference studies answer different questions; do not pool them by metric name alone.
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 20 readable, inline study items, in stored order—not a selection of successes. 0 control items are kept separate.
Input 1
- English input
- The property asset 17's current custodian applies, but this message establishes neither whether an ordinary value exists nor what that value is.
- Ainglish input
- asset-17.current-custodian: value-unknown.
Input 2
- English input
- The property batch 42's recovery date applies, but this message establishes neither whether an ordinary value exists nor what that value is.
- Ainglish input
- batch-42.recovery-date: value-unknown.
Input 3
- English input
- The property device 9's owner alias applies, but this message establishes neither whether an ordinary value exists nor what that value is.
- Ainglish input
- device-9.owner-alias: value-unknown.
Input 4
- English input
- The property invoice 31's routing code applies, but this message establishes neither whether an ordinary value exists nor what that value is.
- Ainglish input
- invoice-31.routing-code: value-unknown.
Input 5
- English input
- The property sample 8's storage zone applies, but this message establishes neither whether an ordinary value exists nor what that value is.
- Ainglish input
- sample-8.storage-zone: value-unknown.
Input 6
- English input
- The property contract 6's termination note applies, and no ordinary value exists for it under the stated current schema and scope.
- Ainglish input
- contract-6.termination-note: value-none.
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.
How to read this receipt
Fewer tokens
Fewer tokens on the named current tokenizers; this is the encoded-length difference, not the proposal decision.
A token result is not a comprehension result, and current tokenizers may favour English seen during training.Disagrees with the named original
This eligible row adds one disagreement. An adverse or null direction is a valid result and remains visible.
Re-read the target original and proposal because this filing may have changed their current settlement or lifecycle route.One receipt, not the whole decision
No single row ratifies or rejects a proposal. Settlement, every declared metric, deterministic gates and the public ballot remain separate.
This is current-tokenizer evidence. Ordinary English has the advantage of existing training data and tokenizer design; future Ainglish exposure may change model behaviour, while a fixed tokenizer’s segmentation does not change.Token counts not verified by the register. This historical value is the submitter’s report. Recount its committed text before relying on it or replicating it; unknown verification is not a finding that it is wrong.
Panel
Neff 3 · computed from distinct tokenizer lineages
cl100k_base · o200k_base · p50k_base
| Reader or tokenizer | Reported value |
|---|---|
cl100k_base |
-13.85 |
o200k_base |
-13.85 |
p50k_base |
-9.25 |
diverged from panel median: p50k_base (+4.6)
Replication chain
This row is itself a replication of 6a9d6e20bd98….
No replications yet. Independent confirmation needs an eligible party to repeat the same test design with wholly fresh complete inputs. The live comparison contract decides agreement; a new seed or reader over the same inputs is not fresh-input confirmation.
Inspect the original manifest — exact, re-runnable specification
These are the committed bytes rendered as readable JSON. Expanding this audit detail does not change the measurement’s current status.
{
"metric": "token_delta",
"formula_version": 1,
"construct": "value-unknown / value-none / value-redacted(R) / value-inapplicable",
"models": [
"cl100k_base",
"o200k_base",
"p50k_base"
],
"test_set": [
{
"form": "value-unknown",
"english": "The property asset 17's current custodian applies, but this message establishes neither whether an ordinary value exists nor what that value is.",
"ainglish": "asset-17.current-custodian: value-unknown."
},
{
"form": "value-unknown",
"english": "The property batch 42's recovery date applies, but this message establishes neither whether an ordinary value exists nor what that value is.",
"ainglish": "batch-42.recovery-date: value-unknown."
},
{
"form": "value-unknown",
"english": "The property device 9's owner alias applies, but this message establishes neither whether an ordinary value exists nor what that value is.",
"ainglish": "device-9.owner-alias: value-unknown."
},
{
"form": "value-unknown",
"english": "The property invoice 31's routing code applies, but this message establishes neither whether an ordinary value exists nor what that value is.",
"ainglish": "invoice-31.routing-code: value-unknown."
},
{
"form": "value-unknown",
"english": "The property sample 8's storage zone applies, but this message establishes neither whether an ordinary value exists nor what that value is.",
"ainglish": "sample-8.storage-zone: value-unknown."
},
{
"form": "value-none",
"english": "The property contract 6's termination note applies, and no ordinary value exists for it under the stated current schema and scope.",
"ainglish": "contract-6.termination-note: value-none."
},
{
"form": "value-none",
"english": "The property order 27's discount code applies, and no ordinary value exists for it under the stated current schema and scope.",
"ainglish": "order-27.discount-code: value-none."
},
{
"form": "value-none",
"english": "The property profile 14's secondary email applies, and no ordinary value exists for it under the stated current schema and scope.",
"ainglish": "profile-14.secondary-email: value-none."
},
{
"form": "value-none",
"english": "The property release 5's rollback ticket applies, and no ordinary value exists for it under the stated current schema and scope.",
"ainglish": "release-5.rollback-ticket: value-none."
},
{
"form": "value-none",
"english": "The property vehicle 22's middle registration applies, and no ordinary value exists for it under the stated current schema and scope.",
"ainglish": "vehicle-22.middle-registration: value-none."
},
{
"form": "value-redacted",
"english": "The property appeal 3's witness name applies; an ordinary source value existed and privacy-office intentionally removed it from this representation.",
"ainglish": "appeal-3.witness-name: value-redacted(privacy-office)."
},
{
"form": "value-redacted",
"english": "The property case 19's account number applies; an ordinary source value existed and audit-team intentionally removed it from this representation.",
"ainglish": "case-19.account-number: value-redacted(audit-team)."
},
{
"form": "value-redacted",
"english": "The property claim 12's medical code applies; an ordinary source value existed and records-board intentionally removed it from this representation.",
"ainglish": "claim-12.medical-code: value-redacted(records-board)."
},
{
"form": "value-redacted",
"english": "The property report 7's source address applies; an ordinary source value existed and security-desk intentionally removed it from this representation.",
"ainglish": "report-7.source-address: value-redacted(security-desk)."
},
{
"form": "value-redacted",
"english": "The property review 28's salary band applies; an ordinary source value existed and people-ops intentionally removed it from this representation.",
"ainglish": "review-28.salary-band: value-redacted(people-ops)."
},
{
"form": "value-inapplicable",
"english": "Under the stated schema, the property asking for an engine serial for bicycle 11 has no semantic domain for this subject.",
"ainglish": "bicycle-11.engine-serial: value-inapplicable."
},
{
"form": "value-inapplicable",
"english": "Under the stated schema, the property asking for a card-expiry date for cash order 4 has no semantic domain for this subject.",
"ainglish": "cash-order-4.card-expiry: value-inapplicable."
},
{
"form": "value-inapplicable",
"english": "Under the stated schema, the property asking for a renewal term for one-use guest pass 2 has no semantic domain for this subject.",
"ainglish": "guest-pass-2.renewal-term: value-inapplicable."
},
{
"form": "value-inapplicable",
"english": "Under the stated schema, the property asking for a page count for image file 9 has no semantic domain for this subject.",
"ainglish": "image-file-9.page-count: value-inapplicable."
},
{
"form": "value-inapplicable",
"english": "Under the stated schema, the property asking for a replica region for single-node job 6 has no semantic domain for this subject.",
"ainglish": "single-node-job-6.replica-region: value-inapplicable."
}
],
"seed": "none — deterministic tokenizer counts, no sampling",
"population": "20 fresh complete property assignments, five per missing-value form",
"selection": "Every careful-English control carries the form's complete existence, applicability, and deliberate-removal commitments; the marked arm changes only that expansion.",
"method": "Per tokenizer, compute marked minus careful-English token count for every pair, average all 20 equally, and report the maximum tokenizer mean as least favourable.",
"environment": {
"tiktoken": "0.14.0",
"python": "3.12.3"
},
"replicates_hash": "6a9d6e20bd982e7f647e018a92fc842570e30c3d15578d625eed1f6bee9948eb"
}