How do I read a corrections entry?

Four words

• Marked

  The list of marked events holds what is shown now as Disputed or Debunked, the newest change first, each with its place, its first report and its last change.

• Disputed

  Sources contradict each other about whether it happened, where, or what it was. That does not make it false, and it does not mean either side is right. A disputed report stays on the map and in the list.

• Debunked

  The reports point to this being false or misattributed, so it is kept for the record. It is a judgement from the available evidence and can be revised. It is taken off the map when it is judged false, unless a person reviewed it, and one taken off is not named in the list, so its claim does not spread.

• Set aside or withdrawn

  No longer shown: merged into another event, out of scope, removed on review, or debunked. The log calls the event withdrawn and does not name it.

One line of the audit log

• Time

  When the state changed, in UTC. It is not when the event happened.

• Change

  The state before and the state after, such as Single source to Corroborated. A first rating is not a change and is not in the log.

• Cause

  When one was recorded, one of ten: new report; merged with a duplicate; new evidence link; reports of another incident taken out; rules changed (reclassification); a source rating changed (reclassification); a scoring setting changed (reclassification); automated review; on review; cause not recorded.

• New evidence or the same evidence

  The first four causes mean something was added or taken out. A reclassification means the same reports were rated again under changed rules, ratings or settings. An automated review means the review read the same reports again.

A worked example

An event's page links to its own entry, which lists every change from the first. Read from the top, one could say:

1. 1. First rated Unverified

   Every event is stored as Unverified until the rules have rated it, so the entry of an event stored since the log began starts with this line.

2. 2. Unverified to Single source

   The rules' own first rating: one credible origin had reported it.

3. 3. Single source to Corroborated

   A second independent origin joined. In the audit log this line carries the cause new report.

4. 4. Corroborated to Disputed

   A report that contradicts the others joined, or the review found the sources at odds. The event stays on the map, half filled.

5. 5. (set aside)

   Added to a line when the event was hidden with that change. In the audit log the same change reads Withdrawn from the site.

None of these lines is a retraction. The entry itself ends by saying that a change of state is a new rating on newer reports or rules.

The counts above the log

• Settled incidents

  Incidents of the last 30 days by state, leaving out the last 12 hours while they settle. An aftermath report linked to an attack counts with that attack, not on its own.

• Debunked and taken down

  Counted apart from the chart. The chart counts only what is still on the map, so its Debunked bar can read 0 when reports were debunked.

• Do early reports hold up?

  Every event first reported in the window, by where it stands now. One that reached Corroborated only by a reclassification is not counted as having held up.

• Changes to the rules

  Each change of the rules that rated stored events again, with how many it moved up and down.

Questions

• What do Unverified, Single source, Corroborated and Confirmed mean?
• How do I read the map?
• Is a siren or an official alert the same as a confirmed strike?
• How are sources weighed?
• How is the tension index built, and what can it not tell you?
• Methodology: how sitmap.live works

Page built 2026-11-13 21:49 UTC · Last updated 2026-11-13 00:00 UTC