Crisis Timeline

Automated, immutable chronological logging for SWAT, HRT, and critical incident operations. Every event — shots fired, casualty, breach, negotiation breakthrough — is time-stamped and linked to relevant subjects, operators, and locations. The AI agent synthesizes the log into after-action reports and command briefings instantly.

Incident Event Log

The Crisis Timeline maintains a DuckDB event table that is append-only. Each event captures a timestamp, event type, severity, description, reporting callsign, and optional links to related subjects and operators. Because the table is never modified after insert, the timeline forms a legally defensible record of the incident.

🕐 Active Shooter — Event-by-Event Record

During a complex active-shooter incident spanning multiple buildings over four hours, every discrete tactical action is logged to the Crisis Timeline: initial shots-fired call, perimeter activation, first contact, officer injury, breach execution, suspect neutralized. At the close of the incident, the AI agent generates a complete chronological narrative from the event log that satisfies both the command debrief and the officer-involved shooting investigation requirements.

Event Severity Levels

Severity Classifications

Linked Event Threading

Events can be threaded together using the logEventLinked() method, creating a parent–child chain that tracks the progression of a specific tactical thread (e.g., a negotiation attempt, a medical event, or a breach sequence). The AI agent can retrieve any thread and present it as a coherent narrative sequence.

AI Agent Tool: crisis_timeline

The crisis_timeline agent tool provides full read/write access to the event log. The agent can log events on behalf of operators through voice-like commands, retrieve recent events for situation reporting, and extract only critical events for command-level briefs.

📋 Commander’s Situation Report

The incident commander needs to brief the SWAT Commander at the 2-hour mark. They ask the AI agent: “Give me a SITREP for the last two hours.” The agent calls getRecentEvents() and getCriticalEvents(), synthesizes the results into a structured SITREP covering key developments, escalations, and current status — formatted and ready for verbal delivery or TAK message transmission.

Agent Tool Operations

Incident Chronology After-Action Review Event Threading DuckDB AI Agent Tool SWAT / HRT
← Subject Intel Next: Overwatch Planner →