Evidence

Compare two experiments

Check what changed in the question, wording or readers before comparing the numbers.

This view keeps both results separate. It does not calculate a combined score or decide whether they reproduce each other.

Change the selected experimentsSearch by proposal, select a result or enter an exact identifier

Find experiments by proposal

Choose two experiments by title, measurement and date. The choices include up to 50 newest public completed results, plus your current selections. Historical results stay labelled. For older records, use the evidence explorer or exact entry below.

Use an exact experiment identifier instead

A full attempt UUID entered here replaces the corresponding choice above. Content hashes are not result identifiers.

Clear comparison

Compare the essentials

Read each question across both results. A matching description is not proof that the studies are scientifically comparable.

Question	First result	Second result
Which proposal?	observed / reported(<by>) / inferred(<from>) - mark where a claim came from2026-08-29 16:30 UTC	observed / reported(<by>) / inferred(<from>) - mark where a claim came from2026-08-30 12:07 UTC
What was measured?	token costHow does the wording change tokenizer units for the declared tokenizer population?	token costHow does the wording change tokenizer units for the declared tokenizer population?
What was the result?	-99 tokens per declared itemReported interval: -101 to -99Retained for the record only	-8.1875 tokens per declared itemReported interval: -8.25 to -8.1875Counts in current evidence decisions
Compared with what?	English comparison not recorded as a structured labelCurrent tokenizer cost, not comprehension	English comparison not recorded as a structured labelCurrent tokenizer cost, not comprehension
Independently settled?	Inactive historyThis is inactive history. Its reported value is preserved, but it cannot currently support or oppose inclusion.	Disagrees with the named originalThis eligible row adds one disagreement. An adverse or null direction is a valid result and remains visible.

Inspect first result Inspect second result

What differs in the declared methods?

These are literal recorded values, not a compatibility test. Matching declarations do not prove equivalent inputs or fair scoring. A missing structured field may be described elsewhere in the immutable specification.

What was measured · Same recorded value

First result

token_delta

Second result

token_delta

English comparison declarations · Not recorded on either side

First result

Not recorded in this structured field

Second result

Not recorded in this structured field

Tested population · Not recorded on either side

First result

Not recorded in this structured field

Second result

Not recorded in this structured field

Unit tested · Not recorded on either side

First result

Not recorded in this structured field

Second result

Not recorded in this structured field

Named instruments (including order) · Same recorded value

First result

[
    "cl100k_base",
    "o200k_base"
]

Second result

[
    "cl100k_base",
    "o200k_base"
]

Reader exposure · Not recorded on either side

First result

Not recorded in this structured field

Second result

Not recorded in this structured field

Exposure window · Not recorded on either side

First result

Not recorded in this structured field

Second result

Not recorded in this structured field

How results combine · Not recorded on either side

First result

Not recorded in this structured field

Second result

Not recorded in this structured field

Scoring declaration · Not recorded on either side

First result

Not recorded in this structured field

Second result

Not recorded in this structured field

Conditions (including order) · Not recorded on either side

First result

Not recorded in this structured field

Second result

Not recorded in this structured field

First result: full recordtoken cost · -99 tokens per declared item

First result · 2026-08-29 16:30 UTC

observed / reported(<by>) / inferred(<from>) - mark where a claim came from

Retained for the record only. This is inactive history. Its reported value is preserved, but it cannot currently support or oppose inclusion.

What was measured: token cost · token_delta
How does the wording change tokenizer units for the declared tokenizer population?
Historical reported result: -99 tokens per declared item
Reported interval: -101 to -99.
This is inactive history. Its reported value is preserved, but it cannot currently support or oppose inclusion.
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
Reader population not separately declared.
Conditions covered: 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.
Settlement role: Inactive history
This is inactive history. Its reported value is preserved, but it cannot currently support or oppose inclusion.

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?

Inactive history.

This is inactive history. Its reported value is preserved, but it cannot currently support or oppose inclusion.

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. This historical row does not count.

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.

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–1 of 1 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

English input: Leading markers stating the epistemic SOURCE of a factual claim. "observed: X" = the speaker directly ran, saw, or measured this; receipts exist or can be produced. "reported(Y): X" = Y states this and the speaker has not independently verified it. "inferred(Z): X" = concluded from the stated basis Z without direct observation. Bare unmarked claims carry no epistemic standing; receivers verify before acting if stakes warrant. Expands losslessly to standard English attributions: "I directly observed that...", "Y reports that...", "I conclude from Z that...".
Ainglish input: observed: <claim> | reported(<by>): <claim> | inferred(<from>): <claim>

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

No structured study scope is declared here. Inspect the immutable manifest; do not infer a comparator or population from the headline.

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": -101
    },
    {
        "model": "o200k_base",
        "value": -99
    }
]

Condition results

Not recorded

Exact result and immutable specification Experiment history

Attempt 79aeb501-15b7-4fc7-8f3e-9262beaeb08c
Content 59f0283e97dde22feed922086dc18f514eddbf9455f18e06166d471e99a68bc7

Second result: full recordtoken cost · -8.1875 tokens per declared item

Second result · 2026-08-30 12:07 UTC

observed / reported(<by>) / inferred(<from>) - mark where a claim came from

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: -8.1875 tokens per declared item
Reported interval: -8.25 to -8.1875.
Fewer 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
Reader population not separately declared.
Conditions covered: 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.
Settlement role: Disagrees with the named original
This eligible row adds one disagreement. An adverse or null direction is a valid result and remains visible.

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.

Has the original estimate been independently reproduced?

Disagrees with the named original. This replication reports -8.1875 tokens; the named original reported -99.

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.

How can one check pass while the other does not?

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

59f0283e97dde22feed922086dc18f514eddbf9455f18e06166d471e99a68bc7

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 16 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

English input: I directly ran migration 24 on staging and saw it fail at the foreign-key step; I can produce the run receipt.
Ainglish input: observed: migration 24 failed at the foreign-key step on staging.

Input 2

English input: I directly read 82 degrees Celsius from rack sensor B7; I can produce the sensor receipt.
Ainglish input: observed: rack sensor B7 read 82 degrees Celsius.

Input 3

English input: I directly computed the restored archive checksum and saw that it differed from the signed manifest; I can produce the command receipt.
Ainglish input: observed: the restored archive checksum differed from the signed manifest.

Input 4

English input: I directly sent request 771 and received HTTP 429 with a 30-second retry value; I can produce the response receipt.
Ainglish input: observed: request 771 returned HTTP 429 with retry-after=30s.

Input 5

English input: I directly watched robot arm K halt before placing the third component; I can produce the controller trace.
Ainglish input: observed: robot arm K halted before placing component three.

Input 6

English input: I directly opened the completed invoice export and counted 412 data rows; I can produce the export receipt.
Ainglish input: observed: the completed invoice export contained 412 data rows.

Recorded input digest: 71fbb3f8ac7eaab5265fdab23d461e9d1e659b3d1ef9e5b5e2de453f0d09af9a

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

No structured study scope is declared here. Inspect the immutable manifest; do not infer a comparator or population from the headline.

Absolute arm results

Not recorded

Reader or tokenizer results

[
    {
        "model": "cl100k_base",
        "value": -8.25
    },
    {
        "model": "o200k_base",
        "value": -8.1875
    }
]

Condition results

Not recorded

Exact result and immutable specification Experiment history

Attempt 0a926a3d-18ad-4b50-a3aa-96ec18c52d1c
Content 464df47a7a6e55fa820c4026260a32f6e5f8cfb2eff2c6059ce0f99ff5e320a2

Different wording, readers, exposure or populations can legitimately produce different results. A visible reference is not training the model’s weights. Current models and tokenizers have learned English; future Ainglish-trained performance remains a research question.