Models, drift and fleet

The Operations area keeps the system trustworthy over time: which models assessed each sortie, whether the cameras are still seeing well, and what needs maintenance.

The model registry#

Every component that can change an assessment is registered: segmentation, pose estimator, tracker, platform classifier, presence gate, sanitizer and scoring rubric. Versions move from candidate to staging to production to retired.

• Evaluate runs a candidate against the validation set. Rubric changes can be re-scored in seconds; perception and sanitizer changes reprocess the validation videos.
• Gates: category agreement ≥ 95%, grade agreement ≥ 80%, phase agreement ≥ 95%, and every allow-list decision correct. An administrator can override a failed gate only with a written reason.
• Promote writes a new configuration version. Every sortie carries a release tag (cfg-N) that says exactly what assessed it.
• Rollback by re-activating an older configuration version on the System page; the models that were in production with it come back too.

Drift#

Each sortie records four quality signals: tracking valid fraction, silhouette fit (IoU), position uncertainty and processing time. Drift compares the last eight sorties with the period before:

• a shift on one camera points at the sensor and opens an Image quality degraded work order automatically;
• a shift across all cameras points at a model regression or changed conditions and raises a fleet alert.

After a calibration a camera shows rebaselining until eight new sorties are in.

Cameras and maintenance#

Cameras carry tail, position, model, firmware, calibration date and interval, status and their last built-in test. A failed BIT marks the camera failed and opens a replacement order; recording a calibration closes the calibration and image-quality orders. Calibration overdue or due within 14 days raises an alert.

Receiver onboarding#

A new receiver type is added from a specification under Fleet scale → Receiver onboarding, then qualified with a test plan before it goes on the allow-list. Until then, sorties with that receiver are refused and purged.

Mishap and damage#

Operations → Mishap & damage keeps public mishap costs, your own damage reports, the exposure of each assessed deviation and the savings estimate (low, base and high cases).