Typorithm · hard

Event Verification

event-verificationosintverificationcorroboratedebunk
Saved on this device
Full lesson · 8 learning steps Open any exercise for focused practice
1

Step 1 of 8 · intro card

Learn Event Verification

0%

Conflict Monitoring

Open-source conflict monitoring verifies whether a claimed incident actually happened: corroborate independent public posts, geolocate and chronolocate footage, and debunk staged or recycled media. The purpose is journalism and accountability — documenting the record from public sources, never operational or targeting use.

Conflict monitoring in the Bellingcat tradition is retrospective verification. An incident is claimed in public media; investigators ask whether it really happened and document the answer for the journalistic, legal, and historical record — they never act on it in real time.

Corroboration is the core method: a lone post is treated as unverified, while multiple independent public sources that agree raise confidence. Geolocation (matching landmarks, shadows, and skylines to public maps and imagery) and chronolocation (dating footage from weather, sun position, and visible markers) anchor a clip to a place and time.

Debunking is equally important. Staged scenes, mislabeled archive footage, and recycled clips from other conflicts are flagged and corrected. This protects civilians and sources by stopping false claims, and keeps the verified record honest.

01

Verify whether a claimed incident truly happened.

02

Corroborate with multiple independent public posts.

03

Geolocate and chronolocate to anchor the record.

# verify a claimed incident from public media
# corroborate: multiple independent posts
# geolocate + chronolocate the footage
# debunk staged or recycled media

Read the implementation

Connect each part of the code to the concept before you type.

1. Start from a public claim

Verification begins with a claim circulating in public media — the goal is to document for the journalistic and legal record whether it actually happened, never to act on it operationally.

# verify a claimed incident from public media

2. Corroborate independently

A single post proves nothing; multiple independent public sources that agree raise confidence the event is real.

# corroborate: multiple independent posts

3. Place and time it

Geolocation fixes where footage was filmed and chronolocation fixes when, anchoring it to the verifiable record from public imagery alone.

# geolocate + chronolocate the footage

4. Debunk fakes

Verification protects civilians by debunking staged or recycled media that would otherwise spread false claims.

# debunk staged or recycled media

A complete learning loop

01

Understand

Read the concept map and follow the code breakdown.

02

Reconstruct

Type the implementation, repair mistakes and work through every recall exercise.

03

Verify

Use the final check without hints; revisit weak concepts in short practice sessions.

Event Verification: Lesson & Practice · Typorithm | ApplyDjinn