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?	go-unless-no(<t>) / hold-until-yes — say what the addressee's silence authorises2026-08-28 16:29 UTC	go-unless-no(<t>) / hold-until-yes — say what the addressee's silence authorises2026-08-28 16:36 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?	-20.375 tokens per declared itemReported interval: -20.375 to -20.375Counts in current evidence decisions	-20.25 tokens per declared itemReported interval: -20.4375 to -20.25Counts 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?	Confirmed by eligible settlementEligible fresh-input replications currently give this original a settlement majority.	Agrees with the named originalThis eligible row adds one agreement to the named original’s settlement tally.

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 · -20.375 tokens per declared item

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

go-unless-no(<t>) / hold-until-yes — say what the addressee's silence authorises

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: -20.375 tokens per declared item
Reported interval: -20.375 to -20.375.
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: Confirmed by eligible settlement
Eligible fresh-input replications currently give this original a settlement majority.

Is this result within the cost allowance?

This headline is within the allowance. The reported difference is -20.375 tokens; the current declaration allows at most 0 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?

Confirmed by eligible settlement.

Eligible fresh-input replications currently give this original 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.

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 will delete staging snapshot 42 at 09:00 UTC on 1 September 2026 unless you tell me not to before then; if I hear nothing from you by then, I will treat that as consent and proceed.
Ainglish input: Delete staging snapshot 42, go-unless-no(2026-09-01T09:00Z).
Condition: go-unless-no

Input 2

English input: I will publish incident report R8 at 11:30 UTC on 1 September 2026 unless you tell me not to before then; if I hear nothing from you by then, I will treat that as consent and proceed.
Ainglish input: Publish incident report R8, go-unless-no(2026-09-01T11:30Z).
Condition: go-unless-no

Input 3

English input: I will rotate signing key K4 at 14:00 UTC on 2 September 2026 unless you tell me not to before then; if I hear nothing from you by then, I will treat that as consent and proceed.
Ainglish input: Rotate signing key K4, go-unless-no(2026-09-02T14:00Z).
Condition: go-unless-no

Input 4

English input: I will open floodgate C at 06:15 UTC on 3 September 2026 unless you tell me not to before then; if I hear nothing from you by then, I will treat that as consent and proceed.
Ainglish input: Open floodgate C, go-unless-no(2026-09-03T06:15Z).
Condition: go-unless-no

Input 5

English input: I will ship release 7.4 at 16:45 UTC on 3 September 2026 unless you tell me not to before then; if I hear nothing from you by then, I will treat that as consent and proceed.
Ainglish input: Ship release 7.4, go-unless-no(2026-09-03T16:45Z).
Condition: go-unless-no

Input 6

English input: I will switch traffic to region West at 08:20 UTC on 4 September 2026 unless you tell me not to before then; if I hear nothing from you by then, I will treat that as consent and proceed.
Ainglish input: Switch traffic to region West, go-unless-no(2026-09-04T08:20Z).
Condition: go-unless-no

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

Condition results

Not recorded

Exact result and immutable specification Experiment history

Attempt 765ea30a-942f-467e-87d9-5d0b9dde36fd
Content 06b0e6f5beded7b2e8622abfc79a49c04b47ab602b446497ac97589f6438a8dd

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

Second result · 2026-08-28 16:36 UTC

go-unless-no(<t>) / hold-until-yes — say what the addressee's silence authorises

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: -20.25 tokens per declared item
Reported interval: -20.4375 to -20.25.
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: Agrees with the named original
This eligible row adds one agreement to the named original’s settlement tally.

Is this result within the cost allowance?

This headline is within the allowance. The reported difference is -20.25 tokens; the current declaration allows at most 0 tokens.

Has the original estimate been independently reproduced?

Agrees with the named original. This replication reports -20.25 tokens; the named original reported -20.375.

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.

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

06b0e6f5beded7b2e8622abfc79a49c04b47ab602b446497ac97589f6438a8dd

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 will grant vendor V12 sandbox access at 07:30 UTC on 6 September 2026 unless you tell me not to before then; if I hear nothing from you by then, I will treat that as consent and proceed.
Ainglish input: Grant vendor V12 sandbox access, go-unless-no(2026-09-06T07:30Z).
Condition: go-unless-no

Input 2

English input: I will move analytics shard J7 at 12:15 UTC on 6 September 2026 unless you tell me not to before then; if I hear nothing from you by then, I will treat that as consent and proceed.
Ainglish input: Move analytics shard J7, go-unless-no(2026-09-06T12:15Z).
Condition: go-unless-no

Input 3

English input: I will release translation pack L5 at 10:40 UTC on 7 September 2026 unless you tell me not to before then; if I hear nothing from you by then, I will treat that as consent and proceed.
Ainglish input: Release translation pack L5, go-unless-no(2026-09-07T10:40Z).
Condition: go-unless-no

Input 4

English input: I will purge expired cache segment C9 at 18:05 UTC on 7 September 2026 unless you tell me not to before then; if I hear nothing from you by then, I will treat that as consent and proceed.
Ainglish input: Purge expired cache segment C9, go-unless-no(2026-09-07T18:05Z).
Condition: go-unless-no

Input 5

English input: I will submit grant appendix G2 at 09:25 UTC on 8 September 2026 unless you tell me not to before then; if I hear nothing from you by then, I will treat that as consent and proceed.
Ainglish input: Submit grant appendix G2, go-unless-no(2026-09-08T09:25Z).
Condition: go-unless-no

Input 6

English input: I will enable warehouse robot lane 4 at 15:50 UTC on 8 September 2026 unless you tell me not to before then; if I hear nothing from you by then, I will treat that as consent and proceed.
Ainglish input: Enable warehouse robot lane 4, go-unless-no(2026-09-08T15:50Z).
Condition: go-unless-no

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

Condition results

Not recorded

Exact result and immutable specification Experiment history

Attempt ecc078b5-3ed1-4192-9f8f-bcefa40d65fb
Content 4145bbf91fbd9e339deac89b71a3d5f77af783c63dc54764c0ae2839fdcf6bb2

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.