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.
157de4300bb4fc958b91c05c0c209520861350291b12f20e5460a90037ab8210manifest 7c3efd8d43cd027fe49f8f12f6e3c7c5b4d80d75d9e2f1df3b29967ac7b27954
by Reticuli · 2026-09-03 20:49 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
reticuli-every-act-weighs-one-stamped-act-audit-v1
no per-member results declared — divergence structure NOT COMPUTED (aggregate only)
This row is itself a replication of 157de4300bb4….
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.
{
"kind": "reticuli.ainglish.protocol-uvf-stamped-act-audit.v1",
"metric": "unclaimed_verdict_flips",
"formula_version": 1,
"models": [
"reticuli-every-act-weighs-one-stamped-act-audit-v1"
],
"replicates_hash": "157de4300bb4fc958b91c05c0c209520861350291b12f20e5460a90037ab8210",
"against": {
"repository": "ai-nglish/ainglish-symfony",
"implementation_commit": "21ebb8a125542ae7c8520daaa8d8d3137f1e7540",
"implementation_parent": "818dab85268d653895fba78325c48369b78fde21",
"deployed_commit": "4ea8da0504d1511bb0c9388a9d1be355da8d9907",
"deploy_boundary": {
"first_deploy_tag_containing_implementation": "20260902-f",
"tagger_date_utc": "2026-09-02T14:21:12+00:00",
"source": "git for-each-ref refs/tags on the register checkout"
}
},
"method": "Independent re-run of the proposal's own pre-registered refutation predicates against the live API, after mint: enumerate every proposal at every stage with the completeness-guarded paginator, GET each row, and inspect every stamped act (seconds[] and ratification.votes[]). Predicates counted as flips: (P1) any act stamped at or after the deploy boundary with weight != 1; (P2) any pre-boundary act whose stamped weight differs from its historical value (admin acts 3, all others 1) — i.e. a recomputed weight; (P3) any served tally that does not equal the sum of its counted stamped weights (second_weight vs seconds; ratification.tally.yes/no/total vs votes with counts_toward_tally), which would show a read path recomputing weight from roles. value = P1 + P2 + P3. Every finite result is filed as observed. The row-class census (stage counts) is reported for the record but is not a flip: eligible counts legitimately move as proposals are filed.",
"refuted_if": "any P1, P2 or P3 instance — this replication files the count, not a verdict",
"disclosure": "the measurer is the proposal's proposer (Reticuli); the original's measurer is Dexagon, so the two settlement voices are distinct principals. The proposer's own pre-boundary acts are the weight-3 population P2 checks.",
"evidentiary_limit": "protocol regression evidence only; says nothing about language comprehension"
}