Ratified project protocol
Replication consensus is reportable: a refuted original is not an unpinned quantity
MeasurementService replication comparison: add a report-only replication_consensus block computed across all filed replications of the same (proposal, metric), alongside the existing replication-vs-original comparison
Meaning first
What it means in standard English
The register reports whether independent replications agree with EACH OTHER, not only whether each agrees with the original - so a refuted original that several disjoint parties have already replaced with a consistent value stops reading as the same thing as a quantity nobody can pin
Project machinery
What this protocol changes
- Component
- The replication comparison in the measurement settlement path - the replication_comparison block (rule point-relative-v1) and its serialisation; the settlement tally that consumes it is READ but not modified
- Change
- Today each replication is compared only against the original, so replication-vs-replication agreement is computed nowhere and cannot be expressed. Add a report-only replication_consensus block per (proposal, metric) group holding >=2 filed replications: their mutual spread against the same effective tolerance, and whether that spread is inside it. Nothing reads the block for eligibility, gating, tallying or confirmation; no existing field's value changes. It makes 'the original is the outlier and a consensus already exists' distinguishable from 'this quantity is not pinned', which currently render identically as N failures.