IRANWAR.AI

Signal and Noise

Modern information warfare is not about censorship. It is about volume. Bury the signal in noise. Overwhelm the citizen with so much conflicting data that comprehension becomes impossible and apathy becomes rational.

This dashboard is an attempt at the opposite: take the chaos of a war — airstrikes, market swings, refugee columns, diplomatic posturing — and make it legible. Not simple. Legible. Every data point sourced, every chart connected to the human reality it represents.

The Space Between Data and Understanding

There is a gap between knowing a number and understanding what it means. Between reading "165 killed" and grasping that each was a child who had a favorite color and a laugh their parents will never hear again. Most information systems are designed to keep you on the abstract side of that gap.

This dashboard is designed to pull you across. Not by manipulating you — by attending. By placing every data point in context until the picture becomes too coherent to dismiss and too human to ignore.

Who Has the Right to Know

Intelligence briefings were once prepared exclusively for presidents and generals — the people who start wars. The public that funds them, fights them, and dies in them was given press conferences and talking points.

This dashboard exists on a simple premise: the people who pay for a war have the right to understand it. The real version. With the dollar amounts and the body counts and the displacement figures all in one place, connected, contextualized, and impossible to look away from.

A Note on Violence

This project is fundamentally antiwar. Not strategically, not politically — morally. The act of killing human beings in organized fashion, no matter how justified the stated objective, demands relentless scrutiny rather than patriotic celebration.

We do not take sides between combatants. We take the side of the people caught between them — the families in Minab, the displaced in Lebanon, the service members at Port Shuaiba, the gas station worker in Ohio who doesn't know why her commute suddenly costs $30 more a month.

Data Fidelity

Honesty about what this is and what it isn't:

• Financial baselines are cross-referenced against FRED, Yahoo Finance, ICE/NYMEX, Treasury FiscalData, COMEX, and EIA. Pre-war values are independently sourced with confidence levels documented in the audit trail. These are the hardest numbers on the dashboard.
• Conflict data is sourced from ACLED, CENTCOM, DoD press releases, CRS reports, OSINT analysts, and verified satellite imagery. Strike coordinates are approximate. Casualty figures draw from multiple sources that frequently contradict each other — because that is the nature of war reporting.
• Humanitarian data comes from UNHCR, OCHA, ICRC, WHO, the Iranian Red Crescent, and the Lebanese Health Ministry. Displacement figures are conservative estimates by design.
• AI-generated content includes timeline descriptions, daily briefings, and some enrichment calculations. These are audited by the creator, but models hallucinate with total confidence — errors survive audits. A detailed correction and verification trail is maintained in the project repository.
• Update cadence is daily. Each update cycle includes a full audit of all JSON data files against primary sources.
• No data on this dashboard should be used for financial, military, or life-safety decisions. It is built for comprehension, not action.

The Experiment

This project — a dashboard built largely by AI, citing sources that are themselves contested, published into the same information ecosystem it critiques — is an artifact of the very system it seeks to clarify. That is either a fatal contradiction or the only honest place to start.

Can open-source transparency, radical citation, and good faith produce genuine understanding? Can data, presented with enough context and enough humanity, actually change how someone understands what their government is doing with their money and in their name? The experiment is running. You are part of it now.

Contribute

This project is open source. Every line of code, every data pipeline, every editorial decision is public and auditable on GitHub. That is not a feature. It is the point.

If you have domain expertise — conflict data, financial modeling, humanitarian reporting, OSINT, infrastructure, design — we want your eyes on this. Fork the repo. Open an issue. Tell us what we got wrong.

If you don't code, you can still help. Share it. Send it to someone who thinks they understand the war because they watched a panel show, or to someone who stopped paying attention entirely.

Contribute, correct, or just make contact: [email protected]