[ INTEROPERABILITY ]
A fire agency doesn't need another app, and it doesn't need to install our hardware first. AD.OS runs on the data California already publishes: CAL FIRE incident feeds, the ALERTCalifornia camera network and FIRIS perimeters come in, and tracks go out to the screens your teams already watch. Watchtower adds your own early detection on top. It is never a prerequisite.
↳ 01
FEED IN
The state's own incident feeds land directly in Fire Watch: active incidents, location, size and containment, refreshed continuously. This is the layer that means an agency can run the fleet on day one, before a single piece of Veridis hardware is mounted anywhere.
CAL FIRE · PUBLIC FEED
↳ 02
TRACK OUT
Every swarm track, detection, and status publishes as CoT. If your agency runs TAK (and it does), AD.OS is already another feed on the screen your teams watch, with zero new software at the edge.
CoT · TAK / ATAK
↳ 03
FEED IN
Live incident perimeters from the FIRIS intelligence aircraft render directly in Fire Watch, layered with the swarm's own mapping: the state's picture and the fleet's picture, reconciled on one map.
FIRIS FEED · GEOJSON
↳ 04
FEED IN
The system listens for crewed aviation continuously and computes closest point of approach. Air attack inbound means the swarm alerts, yields, and grounds by procedure: deconfliction as an architectural feature, not a promise.
ADS-B 1090ES · CPA
↳ 05
FEED IN
The state's wildfire camera network joins the intel picture on demand, giving visual context on any detection, opt-in by design and off by default, respecting the network's terms.
ALERTCALIFORNIA · OPT-IN
↳ 06
TRACK OUT
One action produces a time-stamped situation report: positions, actions, detections and timeline, formatted for incident command and after-action review.
SITREP · TIMESTAMPED
No rip-and-replace, no new screens to learn. AD.OS joins the picture your agency already trusts, and puts aircraft behind it.