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?	start-by / complete-by — say which task event a deadline constrains2026-08-09 09:01 UTC	start-by / complete-by — say which task event a deadline constrains2026-08-09 09:22 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?	-8 tokens per declared itemReported interval: -8 to -8Not yet counting in evidence decisions	-9.333 tokens per declared itemReported interval: -14 to -5Counts 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?	DisputedEligible replications disagree and this original does not hold a settlement majority.	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 · -8 tokens per declared item

First result · 2026-08-09 09:01 UTC

start-by / complete-by — say which task event a deadline constrains

Not yet counting in evidence decisions. This row remains available for assessment, but does not currently carry a counting evidence result.

What was measured: token cost · token_delta
How does the wording change tokenizer units for the declared tokenizer population?
Reported result: -8 tokens per declared item
Reported interval: -8 to -8.
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: Disputed
Eligible replications disagree and this original does not hold a settlement majority.

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?

Disputed.

Eligible replications disagree and this original does not hold a settlement majority.

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.

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.

No readable study input 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.

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

Condition results

Not recorded

Exact result and immutable specification Experiment history

Attempt f1322006-961a-11f1-9e5e-04e365516815
Content 755ec9aed515eb9dc1fe786d95fdc5c642eb2ac97eb899375c4c97885e105d4f

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

Second result · 2026-08-09 09:22 UTC

start-by / complete-by — say which task event a deadline constrains

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: -9.333 tokens per declared item
Reported interval: -14 to -5.
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 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?

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

755ec9aed515eb9dc1fe786d95fdc5c642eb2ac97eb899375c4c97885e105d4f

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 6 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: The config migration must have actually started by 20:00Z — acknowledging the ticket does not count as beginning.
Ainglish input: req: migrate the config start-by(20:00Z)

Input 2

English input: I promise the cold-backup restore will genuinely begin no later than 2026-08-10T01:00Z; queueing it beforehand is not a start.
Ainglish input: will: restore the cold backup start-by(2026-08-10T01:00Z)

Input 3

English input: The DNS cutover's success condition needs to be met by 04:30Z — stopping halfway does not count as done.
Ainglish input: req: cut over DNS complete-by(04:30Z)

Input 4

English input: I commit that the integrity check will be successfully finished no later than 2026-08-10T08:00Z.
Ainglish input: will: run the integrity check complete-by(2026-08-10T08:00Z)

Input 5

English input: Begin the shard rebalance in earnest by 12:00Z; merely scheduling it for later is not beginning.
Ainglish input: req: rebalance shard 3 start-by(12:00Z)

Input 6

English input: The audit trail export's declared success condition must be satisfied no later than 2026-08-10T15:30Z.
Ainglish input: will: export the audit trail complete-by(2026-08-10T15:30Z)

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

Condition results

Not recorded

Exact result and immutable specification Experiment history

Attempt f13220b8-961a-11f1-9e5e-04e365516815
Content a65cc5ccd1a2bec6e1490ea2869ffab7b3c0eec35a89d97cc79ddd486deefc86

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.