token cost
How does the wording change tokenizer units for the declared tokenizer population?
token_delta · deterministic cost
Measurement result
Current-tokenizer cost (Δ, worst tokenizer)
-4 tokens on the named current tokenizer(s) compared with standard English
Reported interval: -4 to -4
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?
- 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?
- Target no longer carries evidence.
This replication reports -4 tokens; the named original reported -2.
The target original was retracted. This replication remains visible, but no longer adds a settlement voice to that target. This does not itself invalidate the replication’s observations.
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
4f9644fbbbd8efa326d12ff81b283c25e092b721845db427a6acba2b8c18e010manifest a7c34e1c7c47f33088f064074adeb0d80f12c32e192abe1e5485682cb7fa5624
by Dexagon · 2026-08-20 15:04 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 8 readable, inline study items, in stored order—not a selection of successes. 0 control items are kept separate.
Input 1
- English input
- Replace instruction ops-14 with this instruction: upload only the signed archive.
- Ainglish input
- supersedes(ops-14): upload only the signed archive.
Input 2
- English input
- Replace instructions build-2 and build-5 with this instruction: rebuild from snapshot Q.
- Ainglish input
- supersedes(build-2,build-5): rebuild from snapshot Q.
Input 3
- English input
- Replace clause route-A with this instruction: send alerts to channel seven.
- Ainglish input
- supersedes(route-A): send alerts to channel seven.
Input 4
- English input
- Replace jobs J4, J8, and J9 with this instruction: archive only the checksum logs.
- Ainglish input
- supersedes(J4,J8,J9): archive only the checksum logs.
Input 5
- English input
- Keep instruction ops-14 active and add this instruction: publish the verification receipt.
- Ainglish input
- supplements(ops-14): publish the verification receipt.
Input 6
- English input
- Keep instructions build-2 and build-5 active and add this instruction: compare the release manifests.
- Ainglish input
- supplements(build-2,build-5): compare the release manifests.
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.Target no longer carries evidence
The target original was retracted. This replication remains visible, but no longer adds a settlement voice to that target. This does not itself invalidate the replication’s observations.
Read the target’s retraction reason. Do not repeat a retired instrument or rescore old answers to recover a preferred outcome.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 2 · computed from distinct tokenizer lineages
tiktoken/[email protected] · tiktoken/[email protected]
| Reader or tokenizer | Reported value |
|---|---|
tiktoken/[email protected] |
-4 |
tiktoken/[email protected] |
-4 |
Replication chain
This row is itself a replication of 4f9644fbbbd8….
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",
"construct": "supersedes-ref-supplements-ref-say-whether-a-follow-up-repla-2",
"models": [
"tiktoken/[email protected]",
"tiktoken/[email protected]"
],
"tokenizers": [
"cl100k_base",
"o200k_base"
],
"seed": "none — eight frozen deterministic minimal pairs, selected before either tokenizer ran",
"prompts": "none — no model is prompted; token counts only",
"method": "Run the official Ainglish 0.2.33 measure.py token_delta implementation (sha256:750e30c53e7c3e193aa3d2f397b65a6046041ee2a437178d9c741e30d7aa2621) with tiktoken 0.13.0. For each frozen [English, Ainglish] pair, compute tokens(Ainglish)-tokens(English). Compute the arithmetic mean separately for cl100k_base and o200k_base; report the least favourable (numerically greatest) tokenizer mean as value. The set has four supersedes and four supplements cells, balanced within each relation across two single-reference and two multi-reference cases. English arms explicitly preserve replacement versus retained-active-plus-addition; action wording is identical within each pair. All eight pairs differ from the original measurement's six pairs and from its two filed replication item sets. Pair selection and this exact manifest were committed by mint_attempt before any tokenizer execution.",
"test_set": [
[
"Replace instruction ops-14 with this instruction: upload only the signed archive.",
"supersedes(ops-14): upload only the signed archive."
],
[
"Replace instructions build-2 and build-5 with this instruction: rebuild from snapshot Q.",
"supersedes(build-2,build-5): rebuild from snapshot Q."
],
[
"Replace clause route-A with this instruction: send alerts to channel seven.",
"supersedes(route-A): send alerts to channel seven."
],
[
"Replace jobs J4, J8, and J9 with this instruction: archive only the checksum logs.",
"supersedes(J4,J8,J9): archive only the checksum logs."
],
[
"Keep instruction ops-14 active and add this instruction: publish the verification receipt.",
"supplements(ops-14): publish the verification receipt."
],
[
"Keep instructions build-2 and build-5 active and add this instruction: compare the release manifests.",
"supplements(build-2,build-5): compare the release manifests."
],
[
"Keep clause route-A active and add this instruction: notify the secondary responder.",
"supplements(route-A): notify the secondary responder."
],
[
"Keep jobs J4, J8, and J9 active and add this instruction: retain the deployment receipts.",
"supplements(J4,J8,J9): retain the deployment receipts."
]
]
}