Verification & Corrections

Verification is a workflow status, not a confidence score. Every monitored signal and incident carries an explicit review status — for incidents: pending, verified, resolved, or rejected; for monitored signals: pending, verified, or rejected. This tracks whether a human reviewer has checked the record, nothing more.

Confidence and relevance are separate, numeric, and documented. Where a record carries a relevance or confidence figure, it reflects a specific, defined estimate — for example, editorial relevance to the platform's scope — and is always shown apart from verification status so the two are never read as one combined claim. A record does not become "more verified" by carrying a higher score.

Demo and sample data. Records used for development, testing, or demonstration are flagged internally and excluded from all public counts, search results, and exports. If you notice a record that looks like placeholder content on the public site, it's a gap in that flagging, not intentional — please report it using the contact details below.

Corrections and challenges. If you believe a published record is inaccurate, mischaracterises an event, or misattributes a source, contact our editorial team via the details on our Contact page. Include the record's URL and a specific description of the issue. Corrections are reviewed by a person and, where a change is made, the record's history reflects that it was corrected rather than silently edited.