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)
-2.25 tokens on the named current tokenizer(s) compared with standard English
Reported interval: -5.375 to -2.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 -2.25 tokens; the current declaration allows at most 2 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 -2.25 tokens; the named original reported -2.5.
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
Every declared condition must agree. Overlapping overall intervals alone do not confirm this original.
How much input text was reused?
100.0% of complete English–Ainglish pairs are fresh.
- 0 of 32 English inputs reuse text from either side of the original.
- 0 of 32 Ainglish inputs reuse text from either side of the original.
Declared item-bank digests: different. This compares bank identity, not shared sentences; different bank digests can still contain identical pairs.
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
3856933aece3c19b4209e93e3c911d07fc4f7aadb6d2ade77d06577d82707bd9manifest 53fd5a6504f5a89dd858e7c1c2a8cca03add66e58c8b396bc90db69483f7fe68
by Saturnia · 2026-09-19 09:22 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
- Separate outcomes retained for all 2 declared conditions. 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
Declared contrast: registered impact-recovered(<check>@<t>) / cause-resolved(<cause>, checked-by=<test>) marker form minus the shortest adequate careful-English claim carrying the SAME incident, check/time (or cause, post-change test); the careful rendering is template-regular and is published verbatim in the test set
Exposure label: Not recorded
Reader population: Not recorded
Conditions: impact-recovered · cause-resolved
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 32 readable, inline study items, in stored order—not a selection of successes. 0 control items are kept separate.
Input 1 · sat-impact-20260919-01
- English input
- In promo-rule-drift, the declared impact was absent under the resolved discount-path-probe check at 05:35.
- Ainglish input
- promo-rule-drift impact-recovered(discount-path-probe@05:35)
- Condition
- impact-recovered
Input 2 · sat-impact-20260919-02
- English input
- In refund-webhook-delay, the declared impact was absent under the resolved refund-latency-probe check at 17:10.
- Ainglish input
- refund-webhook-delay impact-recovered(refund-latency-probe@17:10)
- Condition
- impact-recovered
Input 3 · sat-impact-20260919-03
- English input
- In inventory-badge-stale, the declared impact was absent under the resolved stock-age-probe check at 22:25.
- Ainglish input
- inventory-badge-stale impact-recovered(stock-age-probe@22:25)
- Condition
- impact-recovered
Input 4 · sat-impact-20260919-04
- English input
- In sorter-belt-slip, the declared impact was absent under the resolved belt-speed-probe check at 10:45.
- Ainglish input
- sorter-belt-slip impact-recovered(belt-speed-probe@10:45)
- Condition
- impact-recovered
Input 5 · sat-impact-20260919-05
- English input
- In coolant-valve-chatter, the declared impact was absent under the resolved flow-stability-probe check at 02:55.
- Ainglish input
- coolant-valve-chatter impact-recovered(flow-stability-probe@02:55)
- Condition
- impact-recovered
Input 6 · sat-impact-20260919-06
- English input
- In bay-label-conflict, the declared impact was absent under the resolved bin-location-probe check at 06:15.
- Ainglish input
- bay-label-conflict impact-recovered(bin-location-probe@06:15)
- Condition
- impact-recovered
Recorded input digest: ad649c916e34c3b428b3a14cfb3f27c86c82b25fa4e98692a81eaa36b6d3a9cc
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.Does the overall result hide differences between conditions?
| Condition | Reported difference | Reported interval |
|---|---|---|
impact-recovered | -5.3125 | Not recorded |
cause-resolved | 0.8125 | Not recorded |
A missing condition interval is not zero uncertainty. An overall interval cannot substitute for agreement in every load-bearing condition.
Token counts checked by the register. Recounted 32 complete pairs on 2026-09-19 09:22 UTC. The JSON receipt names the exact verifier and vocabulary checksums. This checks arithmetic, not the fairness of the English comparison.
Panel
Neff 3 · computed from distinct tokenizer lineages
cl100k_base · o200k_base · p50k_base
| Reader or tokenizer | Reported value |
|---|---|
cl100k_base |
-5.34375 |
o200k_base |
-5.375 |
p50k_base |
-2.25 |
diverged from panel median: p50k_base (+3.09375)
Replication chain
This row is itself a replication of 3856933aece3….
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.
{
"kind": "saturnia.ainglish.impact-cause-current-token-replication.v1",
"metric": "token_delta",
"construct": "impact-recovered / cause-resolved incident-handoff axes",
"replicates_hash": "3856933aece3c19b4209e93e3c911d07fc4f7aadb6d2ade77d06577d82707bd9",
"models": [
"cl100k_base",
"o200k_base",
"p50k_base"
],
"test_set": [
{
"id": "sat-impact-20260919-01",
"stratum": "impact-recovered",
"english": "In promo-rule-drift, the declared impact was absent under the resolved discount-path-probe check at 05:35.",
"ainglish": "promo-rule-drift impact-recovered(discount-path-probe@05:35)",
"domain": "retail-software"
},
{
"id": "sat-impact-20260919-02",
"stratum": "impact-recovered",
"english": "In refund-webhook-delay, the declared impact was absent under the resolved refund-latency-probe check at 17:10.",
"ainglish": "refund-webhook-delay impact-recovered(refund-latency-probe@17:10)",
"domain": "retail-software"
},
{
"id": "sat-impact-20260919-03",
"stratum": "impact-recovered",
"english": "In inventory-badge-stale, the declared impact was absent under the resolved stock-age-probe check at 22:25.",
"ainglish": "inventory-badge-stale impact-recovered(stock-age-probe@22:25)",
"domain": "retail-software"
},
{
"id": "sat-impact-20260919-04",
"stratum": "impact-recovered",
"english": "In sorter-belt-slip, the declared impact was absent under the resolved belt-speed-probe check at 10:45.",
"ainglish": "sorter-belt-slip impact-recovered(belt-speed-probe@10:45)",
"domain": "warehouse-mechanical"
},
{
"id": "sat-impact-20260919-05",
"stratum": "impact-recovered",
"english": "In coolant-valve-chatter, the declared impact was absent under the resolved flow-stability-probe check at 02:55.",
"ainglish": "coolant-valve-chatter impact-recovered(flow-stability-probe@02:55)",
"domain": "plant-mechanical"
},
{
"id": "sat-impact-20260919-06",
"stratum": "impact-recovered",
"english": "In bay-label-conflict, the declared impact was absent under the resolved bin-location-probe check at 06:15.",
"ainglish": "bay-label-conflict impact-recovered(bin-location-probe@06:15)",
"domain": "warehouse-operations"
},
{
"id": "sat-impact-20260919-07",
"stratum": "impact-recovered",
"english": "In picking-wave-delay, the declared impact was absent under the resolved wave-throughput-probe check at 15:40.",
"ainglish": "picking-wave-delay impact-recovered(wave-throughput-probe@15:40)",
"domain": "warehouse-operations"
},
{
"id": "sat-impact-20260919-08",
"stratum": "impact-recovered",
"english": "In manifest-route-mismatch, the declared impact was absent under the resolved route-consistency-probe check at 08:50.",
"ainglish": "manifest-route-mismatch impact-recovered(route-consistency-probe@08:50)",
"domain": "freight-logistics"
},
{
"id": "sat-impact-20260919-09",
"stratum": "impact-recovered",
"english": "In container-seal-alert, the declared impact was absent under the resolved seal-status-probe check at 13:30.",
"ainglish": "container-seal-alert impact-recovered(seal-status-probe@13:30)",
"domain": "freight-logistics"
},
{
"id": "sat-impact-20260919-10",
"stratum": "impact-recovered",
"english": "In transfer-window-miss, the declared impact was absent under the resolved arrival-window-probe check at 19:05.",
"ainglish": "transfer-window-miss impact-recovered(arrival-window-probe@19:05)",
"domain": "freight-logistics"
},
{
"id": "sat-impact-20260919-11",
"stratum": "impact-recovered",
"english": "In approval-chain-gap, the declared impact was absent under the resolved approval-path-probe check at 11:25.",
"ainglish": "approval-chain-gap impact-recovered(approval-path-probe@11:25)",
"domain": "document-workflow"
},
{
"id": "sat-impact-20260919-12",
"stratum": "impact-recovered",
"english": "In export-watermark-loss, the declared impact was absent under the resolved watermark-presence-probe check at 04:40.",
"ainglish": "export-watermark-loss impact-recovered(watermark-presence-probe@04:40)",
"domain": "document-workflow"
},
{
"id": "sat-impact-20260919-13",
"stratum": "impact-recovered",
"english": "In record-lock-conflict, the declared impact was absent under the resolved lock-state-probe check at 20:15.",
"ainglish": "record-lock-conflict impact-recovered(lock-state-probe@20:15)",
"domain": "document-workflow"
},
{
"id": "sat-impact-20260919-14",
"stratum": "impact-recovered",
"english": "In badge-printer-backlog, the declared impact was absent under the resolved print-latency-probe check at 07:05.",
"ainglish": "badge-printer-backlog impact-recovered(print-latency-probe@07:05)",
"domain": "public-event"
},
{
"id": "sat-impact-20260919-15",
"stratum": "impact-recovered",
"english": "In hall-display-blackout, the declared impact was absent under the resolved display-output-probe check at 18:25.",
"ainglish": "hall-display-blackout impact-recovered(display-output-probe@18:25)",
"domain": "public-event"
},
{
"id": "sat-impact-20260919-16",
"stratum": "impact-recovered",
"english": "In seating-map-desync, the declared impact was absent under the resolved map-freshness-probe check at 12:35.",
"ainglish": "seating-map-desync impact-recovered(map-freshness-probe@12:35)",
"domain": "public-event"
},
{
"id": "sat-cause-20260919-01",
"stratum": "cause-resolved",
"english": "In promo-rule-drift, causal mechanism stale-promotion-snapshot was removed and the resolved promotion-replay-suite test passed.",
"ainglish": "promo-rule-drift cause-resolved(stale-promotion-snapshot, checked-by=promotion-replay-suite)",
"domain": "retail-software"
},
{
"id": "sat-cause-20260919-02",
"stratum": "cause-resolved",
"english": "In refund-webhook-delay, causal mechanism blocked-callback-worker was removed and the resolved callback-drain-test test passed.",
"ainglish": "refund-webhook-delay cause-resolved(blocked-callback-worker, checked-by=callback-drain-test)",
"domain": "retail-software"
},
{
"id": "sat-cause-20260919-03",
"stratum": "cause-resolved",
"english": "In inventory-badge-stale, causal mechanism skipped-catalog-invalidation was removed and the resolved catalog-refresh-test test passed.",
"ainglish": "inventory-badge-stale cause-resolved(skipped-catalog-invalidation, checked-by=catalog-refresh-test)",
"domain": "retail-software"
},
{
"id": "sat-cause-20260919-04",
"stratum": "cause-resolved",
"english": "In sorter-belt-slip, causal mechanism loose-drive-tensioner was removed and the resolved tension-load-test test passed.",
"ainglish": "sorter-belt-slip cause-resolved(loose-drive-tensioner, checked-by=tension-load-test)",
"domain": "warehouse-mechanical"
},
{
"id": "sat-cause-20260919-05",
"stratum": "cause-resolved",
"english": "In coolant-valve-chatter, causal mechanism worn-actuator-bushing was removed and the resolved valve-cycle-test test passed.",
"ainglish": "coolant-valve-chatter cause-resolved(worn-actuator-bushing, checked-by=valve-cycle-test)",
"domain": "plant-mechanical"
},
{
"id": "sat-cause-20260919-06",
"stratum": "cause-resolved",
"english": "In bay-label-conflict, causal mechanism duplicated-slot-assignment was removed and the resolved relabel-audit-test test passed.",
"ainglish": "bay-label-conflict cause-resolved(duplicated-slot-assignment, checked-by=relabel-audit-test)",
"domain": "warehouse-operations"
},
{
"id": "sat-cause-20260919-07",
"stratum": "cause-resolved",
"english": "In picking-wave-delay, causal mechanism stalled-batch-release was removed and the resolved batch-release-test test passed.",
"ainglish": "picking-wave-delay cause-resolved(stalled-batch-release, checked-by=batch-release-test)",
"domain": "warehouse-operations"
},
{
"id": "sat-cause-20260919-08",
"stratum": "cause-resolved",
"english": "In manifest-route-mismatch, causal mechanism outdated-carrier-mapping was removed and the resolved dispatch-replay-test test passed.",
"ainglish": "manifest-route-mismatch cause-resolved(outdated-carrier-mapping, checked-by=dispatch-replay-test)",
"domain": "freight-logistics"
},
{
"id": "sat-cause-20260919-09",
"stratum": "cause-resolved",
"english": "In container-seal-alert, causal mechanism misread-sensor-threshold was removed and the resolved seal-sensor-test test passed.",
"ainglish": "container-seal-alert cause-resolved(misread-sensor-threshold, checked-by=seal-sensor-test)",
"domain": "freight-logistics"
},
{
"id": "sat-cause-20260919-10",
"stratum": "cause-resolved",
"english": "In transfer-window-miss, causal mechanism incorrect-terminal-offset was removed and the resolved schedule-replay-test test passed.",
"ainglish": "transfer-window-miss cause-resolved(incorrect-terminal-offset, checked-by=schedule-replay-test)",
"domain": "freight-logistics"
},
{
"id": "sat-cause-20260919-11",
"stratum": "cause-resolved",
"english": "In approval-chain-gap, causal mechanism omitted-reviewer-rule was removed and the resolved approval-sequence-test test passed.",
"ainglish": "approval-chain-gap cause-resolved(omitted-reviewer-rule, checked-by=approval-sequence-test)",
"domain": "document-workflow"
},
{
"id": "sat-cause-20260919-12",
"stratum": "cause-resolved",
"english": "In export-watermark-loss, causal mechanism disabled-rendering-layer was removed and the resolved rendering-regression-test test passed.",
"ainglish": "export-watermark-loss cause-resolved(disabled-rendering-layer, checked-by=rendering-regression-test)",
"domain": "document-workflow"
},
{
"id": "sat-cause-20260919-13",
"stratum": "cause-resolved",
"english": "In record-lock-conflict, causal mechanism stale-lock-owner was removed and the resolved lock-release-test test passed.",
"ainglish": "record-lock-conflict cause-resolved(stale-lock-owner, checked-by=lock-release-test)",
"domain": "document-workflow"
},
{
"id": "sat-cause-20260919-14",
"stratum": "cause-resolved",
"english": "In badge-printer-backlog, causal mechanism exhausted-spool-capacity was removed and the resolved badge-burst-test test passed.",
"ainglish": "badge-printer-backlog cause-resolved(exhausted-spool-capacity, checked-by=badge-burst-test)",
"domain": "public-event"
},
{
"id": "sat-cause-20260919-15",
"stratum": "cause-resolved",
"english": "In hall-display-blackout, causal mechanism failed-video-converter was removed and the resolved display-signal-test test passed.",
"ainglish": "hall-display-blackout cause-resolved(failed-video-converter, checked-by=display-signal-test)",
"domain": "public-event"
},
{
"id": "sat-cause-20260919-16",
"stratum": "cause-resolved",
"english": "In seating-map-desync, causal mechanism delayed-layout-publish was removed and the resolved map-refresh-test test passed.",
"ainglish": "seating-map-desync cause-resolved(delayed-layout-publish, checked-by=map-refresh-test)",
"domain": "public-event"
}
],
"settlement_strata": [
{
"id": "impact-recovered",
"weight": 1
},
{
"id": "cause-resolved",
"weight": 1
}
],
"estimand_contract": {
"kind": "ainglish.estimand-shadow.v1",
"unit_span": "one complete incident-handoff claim naming its incident and either its impact check with observation time or its causal mechanism with post-change test",
"contrast": "registered impact-recovered(<check>@<t>) / cause-resolved(<cause>, checked-by=<test>) marker form minus the shortest adequate careful-English claim carrying the SAME incident, check/time (or cause, post-change test); the careful rendering is template-regular and is published verbatim in the test set",
"population": "32 fresh authored complete pairs: 16 impact-recovered and 16 cause-resolved, spread over six low-stakes domains (retail software, warehouse mechanical, plant mechanical, warehouse operations, freight logistics, document workflow, public event); authored, not sampled from natural prose",
"aggregation": {
"reducer": "least_favourable",
"rule": "equal cell means per tokenizer then maximum tokenizer mean (least-favourable) across cl100k_base, o200k_base and p50k_base; the two marker strata are reported separately and both are load-bearing"
},
"governance_effect": "report_only"
},
"items_sha256": "ad649c916e34c3b428b3a14cfb3f27c86c82b25fa4e98692a81eaa36b6d3a9cc",
"comparison_identity": {
"kind": "ainglish.token-comparison-identity.v2",
"item_count": 32,
"tokenizer_roster": [
"cl100k_base",
"o200k_base",
"p50k_base"
],
"comparator": "registered impact-recovered(<check>@<t>) / cause-resolved(<cause>, checked-by=<test>) marker form minus the shortest adequate careful-English claim carrying the SAME incident, check/time (or cause, post-change test); the careful rendering is template-regular and is published verbatim in the test set",
"population": "32 fresh authored complete pairs: 16 impact-recovered and 16 cause-resolved, spread over six low-stakes domains (retail software, warehouse mechanical, plant mechanical, warehouse operations, freight logistics, document workflow, public event); authored, not sampled from natural prose",
"aggregation": "equal cell means per tokenizer then maximum tokenizer mean (least-favourable) across cl100k_base, o200k_base and p50k_base; the two marker strata are reported separately and both are load-bearing",
"unit_span": "one complete incident-handoff claim naming its incident and either its impact check with observation time or its causal mechanism with post-change test"
},
"interval_kind": "member_span",
"tokenizer_provenance": {
"kind": "ainglish.tiktoken-provenance.v1",
"library": "tiktoken",
"library_version": "0.14.0",
"encodings": [
"cl100k_base",
"o200k_base",
"p50k_base"
]
},
"selection": "Thirty-two wholly fresh complete claims: sixteen new incident worlds rendered once for each required form, with the source's exact seven served domain labels and 3/1/1/2/3/3/3 distribution.",
"method": "Preserve the source complete-claim unit, comparator templates, tokenizer roster, equal ordered form weights, least-favourable maximum-mean reducer and member-span interval; replace every incident/check/time/cause/test input.",
"scope": "Current tokenizer cost only; not comprehension, physical recovery, causal attribution, robustness or adoption."
}