Open Source · Public Record
Verified conflict reporting, corroborated before publication — UTC Membership

The Sentinel Review

Methodology

Read the evidence, then the judgment.

Every entry on the record shows the corroboration behind it before it shows a conclusion. This page is the standing description of how claims become findings — and what happens when we get one wrong.

How events reach the record

Four stages, one direction: nothing skips corroboration.

  1. 01

    Collection

    Monitored open sources — public channels, feeds, and wire services across platforms — flow into the intake continuously. The intake is published as the Situation Wire, labeled Aggregated — Unverified, and is never cited as a finding.

  2. 02

    Screening

    Claims are deduplicated, geoparsed, and time-bracketed. A claim with exactly one independent origin is held as Single-Source no matter how widely it is reposted — repetition is not corroboration.

  3. 03

    Corroboration

    An event is verified only when independent sources with no shared upstream agree on place, time, and effect. Occurrence and attribution are assessed separately: a strike can be verified while the question of who fired remains open.

  4. 04

    Publication

    Verified events receive a permanent record page showing the geolocation and its precision bound, the corroborating sources, and the times the record turned on. Claims still in corroboration are held off the public ledger until they clear the bar.

The confidence vocabulary

Three terms, used the same way on every page.

Verified

Independent sources with no shared upstream agree on place, time, and effect. Verified events are the record — they carry permalinks and stand until corrected in the open.

Partial

Some independent corroboration exists, but at least one leg — place, time, or effect — has not closed. Partial claims are held in corroboration and never receive permalinks.

Single-Source

One independent origin, however loudly repeated. Single-Source claims are claims, not findings, and never receive permalinks.

Quiet states are findings, not empty states: a theater with no verified events is reported as watched and quiet, on the record.

Corrections

Corrected in the open.

When a verified entry fails — a geolocation is revised, a corroborating account collapses, an effect was overstated — the record page is amended in place, with the revision dated. Records are never silently edited and never deleted.