I built a personal emergency ops hub in Notion for Metro Manila. Context:

The Philippines declared a national energy emergency in late March. Fuel spikes land fast in Manila, and when power, water, and supply chains wobble, the second-order risk for a lot of us is simple: you lose the basics that keep work possible. If you are digitally employable and internet-stable enough to read this, you already know that disruption here is not a rare event. It is a recurring operational risk.

What I made (and why it is structured like an ops system):

- A single hub that consolidates emergency hotlines and official advisories (PAGASA, PHIVOLCS, NDRRMC)

- Evacuation center maps for Metro Manila

- A Quezon City-first supply source directory covering water, food, power, health, and pet care

- Alert-condition "tonight" checklists, plus scenario checklists (extended blackout, water interruption, typhoon/flooding, earthquake, civil unrest)

- Go-bag specs with quantities and an audit cadence

- An offline export SOP (PDF to phone + computer + print) because a hub is only useful if it is accessible when Notion is not

The part people ask about first:

A Grid Risk Digest database sits at the top and gets populated daily by a Notion AI agent. It scans signals across energy, weather, earthquakes, conflict, cyber, and supply chain and assigns a Green/Yellow/Red level.

Important caveat:

Treat the risk level as a starting point for your own read, not a final verdict. During Yellow and Red, the actual protocol is still direct verification against PAGASA, NDRRMC, PHIVOLCS, and your community x barangay advisories. The agent is an ambient awareness layer. Your judgment is the emergency plan.

What changed after feedback (and a sustainability note):

- Applied an above-the-fold rule so the daily state is visible immediately on mobile

- Moved static reference material into dedicated subpages (checklists, directories, duplication SOP, source list)

- Started tracking inflation-sensitive inputs explicitly (food, power, water, LPG/RON 91), surfaced in a “Current prices” callout

- Added a token-usage ledger as a proxy transparency layer (Notion does not expose exact per-run usage, so this is estimation only)

- Hardened links so the directory does not decay (store locators, stable Google Maps links, durable queries, each with “Last Verified”)

I build operational systems under real constraints. This is the same pattern I bring to founder support and ops work: consolidate signal, define thresholds, write the checklist, and build the "what happens when this fails" path before it fails.

If you are building for safety-adjacent contexts and want a practitioner who will name limits, design for offline use, and treat transparency as part of the system, that is my work.