Alerts, rules, and analysis

Alerts are shared records of conditions that need attention. Acknowledge an alert to show it has been seen, then resolve it when the condition has been handled. Events provide the surrounding time-ordered activity, including command outcomes.

Proposals

Automation can propose an action for a person to accept or decline. Pending proposals appear in Alerts and the statusbar. Read the proposed aircraft, mission, and reason before deciding. A declined auto-operator proposal cools the mission down temporarily; an expired proposal can be proposed again if the gap remains.

Core rule autonomy and auto-operator mode are separate settings. Core defaults to suggestions. Staging explicitly enables automatic mission dispatch only for the serial-filtered virtual fleet.

Watch rules

Rules evaluate connected state and detections. Open Rules to inspect enabled conditions, actions, cooldowns, and fire counts. Use the live preview to see what would match before enabling a change.

Possible actions include alerts, review items, and tasking proposals or commands according to configuration. Rules are shared documents. An enabled rule can continue operating when your panel is closed because Core owns its evaluation.

Analysis and review

The optional detections module analyzes authorized camera feeds with the configured vision models. Analysis sessions have concurrency, duration, and interval limits. The module needs an API key and may incur model charges. Opening the panel does not establish that a model is available or that an inference has succeeded.

Review collects detection items for human triage. Inspect the frame, time, and proposed interpretation before recording a decision. Review metadata lives in Postgres and associated stills live in the blob bucket.

Use Charts, Fleet Timeline, and Activity to compare a suspected event with battery, flight state, link quality, and prior sorties. Recorded measurements and operator review remain the evidence when an automated interpretation is wrong.