Wildfire Incident Response

Portfolio demo

From public fire feeds to an approved, replayable incident picture

One working pipeline, end to end: real public fire and weather data, explicit handling of stale and conflicting inputs, briefings tied to the exact inputs they used, and a human approval on every one.

The workflow

  1. 01

    Ingest

    Pull NIFC incidents and perimeters, NASA FIRMS satellite detections, NWS alerts and observations, and Open-Meteo weather. Keep every raw payload with its fetch time and the source’s own timestamp.

  2. 02

    Normalize

    Validate each payload at the boundary and turn it into typed incident events that carry their provenance.

  3. 03

    Reconcile

    Cluster duplicate detections across satellites and passes, match them to incidents, and flag where the two weather sources disagree.

  4. 04

    Check freshness

    Hold every source to a maximum age. A late or missing feed is shown as stale or missing, never quietly treated as current.

  5. 05

    Brief

    Produce a briefing tied to the exact input revision it used, with every claim citing its inputs. A new input means a new revision and a fresh briefing.

  6. 06

    Approve and replay

    Record the human decision in an append-only log, then replay the history, including delayed weather, duplicate detections, and a lost resource feed.

What is real, and what is simulated

InputStatusSource
Incidents and perimetersrealNIFC WFIGS public services
Satellite fire detectionsrealNASA FIRMS (VIIRS on three satellites)
Weather alerts and observationsrealNational Weather Service API
Second weather sourcerealOpen-Meteo
Resource positionssimulatedNo free public feed exists; labeled everywhere it appears
BriefingsrealGenerated from the live inputs; template when signed out, LLM when the operator signs in

Build status

  1. doneScaffold, look and feel, architecture reference, sign-in, CI
  2. doneFeed adapters, normalization, recorded fixtures, freshness
  3. doneReconciliation, input revisions, briefing, incident console
  4. doneApproval log, replay, and fault scenarios
  5. nextOperator LLM briefings
  6. plannedWrite-up: what is real, what is simulated, what comes next

The architecture reference shows the full production shape this pipeline grows toward.