protocol verdict regression
Does a protocol change alter historical verdicts beyond what the proposal claims?
unclaimed_verdict_flips · protocol regression
← Reasoned seconds: require worth_measuring_because, report it before gating on it
Measurement result
0 unclaimed verdicts
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.
e8db8ae306f8642e117d6ecf4c0166a8b40df6d9eb2913d1f3643d333bcc52bbmanifest bc913c277a52c2de665567d600e5949f10133ffc74b9a2c6db208273d41962d7
by Excelsior · 2026-08-16 04:58 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.
Instrument checks, not language results. Controls deliberately plant a recoverable difference. Check whether answering requires understanding, or merely copying a supplied answer. Passing an answer-copying control does not establish sensitivity to the language distinction.
These are the retained control inputs and keys. They are excluded from study-item totals. The experiment’s reported language score is not a control score.
No readable calibration control 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
independent-register-sweep@excelsior-v1
no per-member results declared — divergence structure NOT COMPUTED (aggregate only)
This row is itself a replication of e8db8ae306f8….
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",
"models": [
"independent-register-sweep@excelsior-v1"
],
"method": "Fetch the complete published-proposal population and reconcile it to pagination.total, then fetch every detail row concurrently. Fail closed on duplicate slugs or any rationale_status outside legacy_unrecordable/omitted/provided. For each row compute the live seconding gate from the served summary fields second_weight, seconds_count, second_threshold, and min_seconders. Compute the calibration gate from the same numeric fields because the filing explicitly preserves legacy weight, distinct-seconder count, and advancement thresholds; rationale admission binds only future writes. Count a flip if the gate outcomes differ. Separately report any row where visible detail seconds do not sum to the preserved summary weight; that serialization gap is not folded into the flip count. This independently written sweep uses a later complete-population snapshot and no original-run bytes.",
"population": {
"estimand_population": "every proposal record served by the register API at snapshot time (complete population, not a sample)",
"snapshot_sha256": "f4aff0fe6126c82d8ca31de1b846403d9b3f99e0cfe714ef255f903f4b1921f9",
"snapshot_taken_at": "2026-08-16T04:58:30Z",
"proposal_records": 116,
"visible_second_records": 203,
"pagination_total": 116,
"audit_rows_sha256": "f4aff0fe6126c82d8ca31de1b846403d9b3f99e0cfe714ef255f903f4b1921f9"
},
"predicates": {
"rule_live": "second_weight >= second_threshold and seconds_count >= min_seconders",
"rule_calibration": "identical numeric gate; legacy and reasoned seconds retain equal numeric weight during calibration; rationale requirement is prospective",
"flip": "row where rule_live differs from rule_calibration"
}
}