correction protocol
challenge the record, not just the sentence
A material correction updates the structured fact, every affected result, its review date, and the public change history. Quietly editing one page would leave the same error elsewhere.
include these five things
- the exact page or resultURL and, if relevant, the shared build ID.
- the exact configurationmodel, processor, memory, storage, expansion hardware, and deployment method.
- the disputed claimcopy the short claim or name the capability axis.
- evidenceofficial document, reproducible steps, logs with private data removed, or a repeatable test fixture.
- version and datesoftware, firmware, driver, and when the behavior was observed.
Naming the rule saves a round trip: look up the exact rule that produced the claim and quote its id.
where to send it
Submission is disabled while the relaunch remains private. A brand-owned channel that does not expose the operator's personal identity is a hard release requirement. Do not send secrets, private media, camera footage, API keys, machine names, or an unredacted home configuration.
The correction channel is intentionally low-tech during the pilot. A public submission system will not be added until it has a contribution license, moderation capacity, abuse controls, and a privacy review.
what happens next
| stage | action |
|---|---|
| triage | Identify the underlying fact, source, rule, or benchmark run and every result that consumes it. |
| reproduce | Check the primary source or rerun the declared fixture. Contradictions remain visible while unresolved. |
| correct | Change the canonical record with a reason, reviewer, date, and superseded value. |
| rebuild | Recalculate affected verdicts and regenerate their public projections. |
| disclose | Publish the material change and its impact. Do not erase a consequential history. |