UNCLASSIFIED // FOR OFFICIAL USE ONLY
UNCLASSIFIED // FOR OFFICIAL USE ONLY
↑ You're on the legacy monitor. Open full version →
MIDDLE EASTERN MONITOR
34DAYS OF CONFLICT
--
ESCALATION
--:--UTC
--EVENTS
--KIA
--FIRES
12SOURCES
Connecting feeds...
Loading conflict map...
Loading satellite stack...

My colleagues at the Ministry of Foreign Affairs have to decide, during a war like the one running right now, whether it's safe to send someone. That's the whole reason any of this exists. I wanted to give them something better to look at than a headline.

Earlier this year I didn't know what Python was. I didn't know what "AI" stood for, and I didn't know what an "AI agent" was — the term hadn't entered my head yet. I opened Google Antigravity because it was the thing in front of me, and I built a bot. Not a dashboard. A bot that could read text off a screen, which meant finding OCR software and running it quietly in the background of a MacBook M1 that was already six years old — and this was only around six months ago. That was the whole system. That's where this started.

From there I started pulling in open data and putting it on a map. GovInsider in Singapore is the reason I met the right people early — they put me in rooms with people who had actual ideas about what a system like this should do, not just how to make one look good. One of those people represented Japan's space agency, JAXA. That's where the satellite layer came from — I asked, and he had access to exactly the kind of imagery a war needs watched from above.

All of that happened this year. It felt like watching one universe end and a new one start in its place, all at once — that's the closest I can get to describing the speed of it. I went from not knowing the language to building hundreds of systems, fast enough that it still surprises the people who watch me do it.

I don't build the kind of database a system like this "should" have. I build with Google Sheets when Google Sheets will do, on purpose — so the system stays fixable by a person, not just by an engineer. I fix things fast, and I fix them the plain way, not the clever way, because the point was never to prove I could write clever code. It was to build something a human being who isn't me can still open up and understand.

That's why there are four of these, not one. Each has to earn its own identity the way a real club does — strong on its own terms, not a copy of the others. One is built wide, across all of Asia. One is built deep — the flagship, everything I know how to do in one place. One is built to step all the way back and hold the whole planet at once. One is built to be fast, the signal before anyone else finishes the headline. If they all did the same thing, I'd have built one system four times.

This screen

MEM is the fast one. Six data feeds. No filler.

The other three: AsiaWatch at asia.nonarkara.org · GlobeWatch at globalmonitor.nonarkara.org · World Console at global.nonarkara.org

What the map actually pulls

The aerosol overlay on the three React maps is NASA MODIS Combined AOD — free, no key, two-day lag. MEM does not carry this layer. JAXA is why the satellite question got asked; Himawari, GCOM-C, and ALOS-2 radar are the real next step and they are not built yet.

SATELLITE STACK
Loading...
MARKET IMPACT
Loading...
ACTIVE FRONTS
CONFLICT HOTSPOTS
Loading...
LIVE STRIKE LOG
Loading...
NUCLEAR PROGRAM
DATA SOURCES
Loading...
LIVE
MAP STACK
Analyst base loading...
Strike / battle event
News-sourced marker
Thermal / fire detection
Nuclear site — intact
Reported proxy link