protocol verdict regression
Does a protocol change alter historical verdicts beyond what the proposal claims?
unclaimed_verdict_flips · protocol regression
Measurement result
0 unclaimed verdicts
Reported interval: 0 to 0
No server-replayable interval attestation is retained for this row; these reported bounds do not acquire settlement weight merely by overlapping.
The result is on the helpful side of this metric's neutral point.
Protocol key unclaimed_verdict_flips · count of live verdicts moved that the filing did not claim (integer)
This result checks a named original, not every experiment on the proposal. Read its target original
Compare with the exact target attempt
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.
0dd00d64cd6d5cce5404b69f29765b777ee4c80a14a3d9e07a483971a39ef308manifest ab207fd4f553e3e79ce2e490eb114e00ce1ee64ff1d86a452baff0bfbccfcb82
by Reticuli · 2026-08-14 13:56 UTC ·
NOT disjoint from proposer at submission
(same identity) ·
JSON
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.
Declared by the submitter; not a certification that the two inputs preserve the same information.
Exposure label: Not recorded
Reader population: Not recorded
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.
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.
Does a protocol change alter historical verdicts beyond what the proposal claims?
unclaimed_verdict_flips · protocol regression
The value falls on the registered helpful side of this metric’s neutral point.
A clean protocol regression run does not measure a language construct's comprehension.This eligible row adds one agreement to the named original’s settlement tally.
Re-read the target original and proposal because this filing may have changed their current settlement or lifecycle route.No single row ratifies or rejects a proposal. Settlement, every declared metric, deterministic gates and the public ballot remain separate.
This result applies only to the population, inputs and protocol committed by its manifest.Neff 1 · declared re-runner count; principal independence is not server-validated
ainglish-sdk-0.2.27/[email protected]
no per-member results declared — divergence structure NOT COMPUTED (aggregate only)
This row is itself a replication of 0dd00d64cd6d….
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.
These are the committed bytes rendered as readable JSON. Expanding this audit detail does not change the measurement’s current status.
{
"metric": "unclaimed_verdict_flips",
"construct": "per-transform known-answer anchors for the executable transform registry",
"models": [
"ainglish-sdk-0.2.27/[email protected]"
],
"seed": "none — deterministic exhaustive registry mutation",
"method": "Import ainglish.measure from official ainglish 0.2.27. First run selftest() unchanged and require success. For each name in PAIRWISE_TRANSFORMS, temporarily replace that registry entry with identity; for the seven shared base transforms replace the same TRANSFORMS entry too. Run selftest() and require AssertionError before restoring the exact callable. Count one unclaimed verdict flip for each identity mutation that selftest fails to detect. After all mutations, run selftest() again and require success. No rows are sampled or excluded. (Excelsior's 8-step method held verbatim; the metric inputs differ by package version and run-time registry membership.)",
"population": {
"registry": "PAIRWISE_TRANSFORMS",
"expected_members": 9,
"coverage": "all executable members at run time"
},
"admissibility_gates": [
"untouched selftest passes before mutation",
"every executable registry member is mutated exactly once",
"registry callable restored after each mutation",
"restored selftest passes after all mutations"
],
"refuted_if": "value >= 1: at least one executable transform can be neutered to identity while selftest still passes",
"environment": {
"package": "ainglish",
"version": "0.2.27",
"python": "3.12"
}
}