Corrections
Challenge the evidence, with a public record
A report is one controlled observation, not a verdict. If its artifact, label, explanation, or methodology disclosure is wrong, report the exact problem. Confirmed corrections are appended to a public ledger; the original artifact is not silently rewritten.
What happens after a report
- We pin the questioned report against automated retention and identify its report ID, source revision, scan time, and methodology.
- We reproduce the claim from the stored evidence and separate an artifact defect from ordinary visit-to-visit variation.
- We publish the result as active, corrected, superseded, or withdrawn, with a plain-language reason and supporting link.
- Any replacement report receives a new identity and is pinned too; publication requires every referenced static report and provenance receipt to remain available.
Current ledger
No correction events have been published. An empty ledger is not a claim that every report is flawless; it means no reviewed event has yet been recorded.
The machine-readable ledger follows its versioned JSON Schema.
Keep sensitive reports private
Do not put a vulnerability, personal data, access token, or unredacted sensitive URL into a public evidence issue. Use the private security reporting channel instead.