I1
Reported
1 New incidents awaiting a full response laneIncident reports
Incident reporting turns case flow into a clear operational summary.
ReportsStatus breakdowns, case counts, and district-level records give command a reporting layer on top of the active incident queue.
I2
Triaged
1 Incidents that already passed intake validationI3
Responding
1 Response cells currently engagedI4
Settled
2 Cases no longer active on the command boardReporting table
Incident distribution
| Incident | Category | Status | Priority | District | Reporter |
|---|---|---|---|---|---|
| Monorail derailment scarePanic cluster detected; crowd spillover is the main risk, not structural failure. | Transit | Responding | Critical | City B Skyline Loop | Transit control |
| Harbor chemical flareThermal plume is localized. Response escalates only if wind shifts inland. | Industrial | Triaged | High | City C South Harbor | Dock supervisor |
| District-wide blackoutSabotage probability dropped after backup nodes came online without further loss. | Infrastructure | Contained | High | City A Old Grid | Grid authority |
| Evacuation route congestionCongestion was driven by contradictory alert messages instead of a live attacker. | Civilian safety | Resolved | Routine | City Q Riverside | Ward volunteer lead |
| Rooftop bio-signal anomalyPattern resembles a mimic nest. Confidence is low, but escalation cost is unacceptable. | Recon | Reported | Critical | City Z Sector 3 | Recon drone |