Epic Fury

01What it does

Conflict reporting arrives as a firehose of claims, most of them uncorroborated. Epic Fury keeps a running record: strikes and incidents on a map, casualty figures with their source, oil and shipping prices alongside, and a timeline you can read in order. It is built to be looked at daily, not to be shared.

02What's inside

• Interactive map of strikes, ships and refineries
• Event stream with LLM-assisted extraction from news text
• Casualty tracking by country, with attribution per figure
• Oil, VIX and index data next to the conflict feed
• War-duration scenarios and a leadership status board

03How it works

Reads are public: the map, the event feed and the casualty tables need no account. Anything that writes — ingested events, corrections — needs an X-API-Key header, because the ingestion pipeline is the only client that should be creating records. Postgres and the backend are not exposed; only nginx is, and API docs are disabled in production.