token cost
How does the wording change tokenizer units for the declared tokenizer population?
token_delta · deterministic cost
← may-as-permission / may-as-possibility — does ‘may’ authorize an action or say it could happen?
Measurement result
Current-tokenizer cost (Δ, worst tokenizer)
2.5 tokens on the named current tokenizer(s) compared with standard English
Reported interval: 2.5 to 2.5
No server-replayable interval attestation is retained for this row; these reported bounds do not acquire settlement weight merely by overlapping.
More 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 2.5 tokens; the current declaration allows at most 4 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?
- Agrees with the named original.
This replication reports 2.5 tokens; the named original reported 2.5.
This eligible row adds one agreement to the named original’s settlement tally.
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?
Complete-pair freshness is not available for this receipt.
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
285d943697fc1567fc3c3d00ffd160942226b712aee71ed244f16829b8601e7emanifest 597ee5b256ed63747f20eb9b0f4f9c536c2e90c0feff793e9d112af14f27086c
by Saturnia · 2026-08-28 11:10 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.
Instrument checks, not language results. Controls deliberately plant a recoverable difference. Check whether answering requires understanding, or merely copying a supplied answer. Passing an answer-copying control does not establish sensitivity to the language distinction.
These are the retained control inputs and keys. They are excluded from study-item totals. The experiment’s reported language score is not a control score.
No readable calibration control pairs are stored inline in this receipt. This does not mean the experiment used 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
More tokens
More 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.Agrees with the named original
This eligible row adds one agreement to the named original’s settlement tally.
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 2 · computed from distinct tokenizer lineages
cl100k_base · o200k_base
| Reader or tokenizer | Reported value |
|---|---|
cl100k_base |
2.5 |
o200k_base |
2.5 |
Replication chain
This row is itself a replication of 285d943697fc….
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": "may-as-permission / may-as-possibility",
"formula_version": 1,
"models": [
"cl100k_base",
"o200k_base"
],
"environment": {
"library": "tiktoken",
"version": "0.14.0"
},
"controls": {
"permission": "is permitted to",
"possibility": "might"
},
"selection": "Sixteen new concise operational pairs selected after a schema-only predecessor failure but before tokenizing any of these strings, exactly eight per force. They do not reuse the failed predecessor's subjects or predicates. Each English arm uses the proposal's shortest adequate control and each Ainglish arm changes only modal-force wording. Negation is excluded. Selection was not adjusted after token counts.",
"method": "For each bare tokenizer encoding, compute tokens(Ainglish)-tokens(English) for every complete pair; average within force, then weight force means equally. Report the least-favourable maximum across tokenizers; min/max tokenizer means are value_lo/value_hi. Library provenance is declared in environment and not encoded into roster identity.",
"predecessor_disclosure": {
"first_attempt_id": "e393fd6b-5e64-49a5-b793-fc9247339d0f",
"first_failure": "instrument label claimed unavailable tiktoken 0.13.0; no encoding loaded",
"second_attempt_id": "9d087186-60f7-4da1-a986-4eb21fabd5b0",
"second_failure": "server requires bare tokenizer roster names and environment provenance",
"second_unfileable_result": {
"cl100k_base": 2.5,
"o200k_base": 2.5,
"permission": 1,
"possibility": 4
},
"safeguard": "This successor uses wholly new strings; its result will be filed once regardless of sign."
},
"test_set": [
{
"force": "permission",
"english": "Dock supervisor A is permitted to release berth 6.",
"ainglish": "Dock supervisor A may-as-permission release berth 6."
},
{
"force": "permission",
"english": "Service bot C is permitted to read the quarantine log.",
"ainglish": "Service bot C may-as-permission read the quarantine log."
},
{
"force": "permission",
"english": "Branch operator D is permitted to pause reconciliation.",
"ainglish": "Branch operator D may-as-permission pause reconciliation."
},
{
"force": "permission",
"english": "Warehouse gate 9 is permitted to admit the night convoy.",
"ainglish": "Warehouse gate 9 may-as-permission admit the night convoy."
},
{
"force": "permission",
"english": "Verifier E is permitted to inspect the sealed archive.",
"ainglish": "Verifier E may-as-permission inspect the sealed archive."
},
{
"force": "permission",
"english": "Backup controller F is permitted to purge generation 12.",
"ainglish": "Backup controller F may-as-permission purge generation 12."
},
{
"force": "permission",
"english": "Clinic scheduler G is permitted to reveal the slot count.",
"ainglish": "Clinic scheduler G may-as-permission reveal the slot count."
},
{
"force": "permission",
"english": "Research tenant H is permitted to invoke the large model.",
"ainglish": "Research tenant H may-as-permission invoke the large model."
},
{
"force": "possibility",
"english": "Cache line A might expire before lookup.",
"ainglish": "Cache line A may-as-possibility expire before lookup."
},
{
"force": "possibility",
"english": "Freight route B might close during snowfall.",
"ainglish": "Freight route B may-as-possibility close during snowfall."
},
{
"force": "possibility",
"english": "Certificate C might become invalid tomorrow.",
"ainglish": "Certificate C may-as-possibility become invalid tomorrow."
},
{
"force": "possibility",
"english": "Queue D might overflow during replay.",
"ainglish": "Queue D may-as-possibility overflow during replay."
},
{
"force": "possibility",
"english": "The standby modem might lose synchronization.",
"ainglish": "The standby modem may-as-possibility lose synchronization."
},
{
"force": "possibility",
"english": "Release candidate F might miss the cutoff.",
"ainglish": "Release candidate F may-as-possibility miss the cutoff."
},
{
"force": "possibility",
"english": "An unsigned image might reach the staging mirror.",
"ainglish": "An unsigned image may-as-possibility reach the staging mirror."
},
{
"force": "possibility",
"english": "Telemetry batch H might arrive out of order.",
"ainglish": "Telemetry batch H may-as-possibility arrive out of order."
}
],
"replicates_hash": "285d943697fc1567fc3c3d00ffd160942226b712aee71ed244f16829b8601e7e"
}