First result · 2026-10-12 20:33 UTC
checked(<predicate>@<checked-at>, scope=...) - assertion layer for condition freshness
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
- 1.875 tokens per declared item
Reported interval: -0.4375 to 1.875.More 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,p50k_baseReader 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?
- 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?
- 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 last checked tests-green at 2026-08-22T11:10Z against repo/main.
- Ainglish input
- checked(tests-green@2026-08-22T11:10Z, scope=repo/main).
Input 2
- English input
- I last checked lint-clean at 2026-10-12T09:40Z against repo@c7a1b2e.
- Ainglish input
- checked(lint-clean@2026-10-12T09:40Z, scope=repo@c7a1b2e).
Input 3
- English input
- I last checked backup-complete at 2026-10-11T03:05Z against host/db-3.
- Ainglish input
- checked(backup-complete@2026-10-11T03:05Z, scope=host/db-3).
Input 4
- English input
- I last checked cert-valid at 2026-10-12T08:00Z against api.example.test.
- Ainglish input
- checked(cert-valid@2026-10-12T08:00Z, scope=api.example.test).
Input 5
- English input
- I last checked disk-free-above-20pct at 2026-10-12T07:15Z against cluster/prod-eu.
- Ainglish input
- checked(disk-free-above-20pct@2026-10-12T07:15Z, scope=cluster/prod-eu).
Input 6
- English input
- I last checked migration-applied at 2026-10-10T18:20Z against db/prod.
- Ainglish input
- checked(migration-applied@2026-10-10T18:20Z, scope=db/prod).
Recorded input digest: fbb31ca507d8ee18478ba8b0fd6739add3c72708e7b17b87fbc748bf2a29e6c3
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
- Compared with
- Ainglish arm carrying checked(<predicate>@<checked-at>, scope=<scope>) minus English arm carrying the row's served lossless expansion 'I last checked <predicate> at <checked-at> against <scope>'; the predicate name, ISO timestamp and scope string are transcribed verbatim in both arms, so slot-filler cost cancels and the delta prices the construct's wrapper against the expansion's words (comparator genre: complete careful English, narrow checking-event reading, no result claim in either arm)
- Tested population
- 16 fresh author-written messages: 8 standalone check reports and 8 reports embedded in a two-sentence operational message; 16 distinct predicate/timestamp/scope triples drawn from release, infrastructure and compliance contexts; no item reused from any prior row on this proposal
- Unit tested
- message pair: one short English message and its Ainglish counterpart, byte-identical outside the construct
- How results combine
- maximum tokenizer mean over the three declared tiktoken encodings (least-favourable); per-pair delta = Ainglish tokens minus English tokens; unstratified, so the headline is the plain item mean of the worst encoding
These are the study author’s declarations. A finding applies to this tested scope; this summary does not establish that another study is comparable.
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": -0.4375
},
{
"model": "o200k_base",
"value": -0.3125
},
{
"model": "p50k_base",
"value": 1.875
}
]
Condition results
Not recorded
Exact result and immutable specificationExperiment history
Attempt 0e3e4ea8-a8fc-47c6-b334-28fc90aaa86c
Content f398df158f9e348c3aa4d2823ce2f0c386ddbd3bdf76795bcf57bac958a438d7