Follow a generated perimeter across a fictional response area, see the weather context attached to each scenario horizon, and inspect what is known or still missing.
Illustrative map and fire progression — no live incident data
This fictional scenario is generated for interface demonstration. The map, perimeter, weather, reports, and event times are not current conditions, a real fire, a forecast, or an estimate for any location. It is not for use during an active incident and does not provide tactical or evacuation guidance.
Scenario map · generated base layer
Incident area and current scenario perimeter
The shaded polygon advances only when the selected synthetic event horizon changes. It does not represent a measured burn scar, acreage, or predicted fire edge.
Fictional Pine Ridge response areaSCENARIO MAP · NOT GEOGRAPHICALLY LOCATED
Fictional, non-geographic basemap drawn for this demo. The perimeter changes are authored scenario steps, not sensor observations, a fire-spread model, acreage estimate, or guidance.
Candidate response options · scenario timing only
Which candidate options remain within their assumed horizon?
This fictional replay shows generic candidate response categories against authored timing cutoffs. It does not select, rank, or recommend tactics. The countdown is the percentage of each assumed scenario window remaining along this playback timeline.
Read this carefully: The percentage is a synthetic timeline countdown, not a probability, real-time countdown, or measure of operational availability. A 0% reading means only that the authored scenario cutoff has been reached. Feasibility, safety, staffing, authorization, real perimeter, time to impact, route conditions, and incident priorities remain unknown.
Event horizon sequence · scenario only
What changes across the response window
Choose a horizon to update the map and inspect its generated report and weather context. These are playback markers, not incident deadlines, impact times, or response recommendations.