Challenge the evidence, with a public record

What happens after a report

1. We pin the questioned report against automated retention and identify its report ID, source revision, scan time, and methodology.
2. We reproduce the claim from the stored evidence and separate an artifact defect from ordinary visit-to-visit variation.
3. We publish the result as active, corrected, superseded, withdrawn, or replaced for privacy, with a plain-language reason and supporting link.
4. Any replacement report receives a new identity and is pinned too; publication requires every referenced static report and provenance receipt to remain available, except an original replaced for privacy, which is removed.
5. A report that published data redaction should have removed is replaced for privacy: a redacted copy is published under a new identity, the original is removed, and the ledger names both.

Current ledger

4 correction events are currently published.

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.