Object-level trigger inputs
Detector trigger choices come from the effective detector model for that source, with the runtime mapping raw detector classes into stable live trigger IDs such as `PERSON` and `BAG`.
Trigger Library
Set the rules that decide when to act.
The Trigger Zoo describes the event types that the Rules page can convert into alerts and downstream actions. It sits between raw model output and the operators or systems that need to respond.
Trigger Families
Simple, editable time triggers
The current docs describe detector-driven and anomaly-driven triggers as the primary examples, with room for more trigger families to appear after restart.
Behavior and object alerts
Anomaly object and activity choices come from the saved anomaly prompt settings, and each anomaly rule now owns its own `1-10` cutoff.
Stable operator-facing selections
The web UI presents saved rule choices as stable operator-facing options instead of making the browser parse registry files directly.
Why it matters
Triggers decide when raw vision becomes an operational event.
The Trigger Zoo controls when the system decides something important happened. It is deliberately separate from model selection and connector delivery so each concern can evolve independently.
New trigger families can appear after restart
The docs explicitly call out that Trigger Zoo entries are plugin-backed, which keeps the UI contract stable even as the runtime grows new event types.
Current Semantics
Normalized trigger IDs keep rule behavior readable.
For the default COCO-trained YOLOX detector family, raw detector classes are broader than the live trigger IDs the runtime emits. That is intentional.
Detector-side normalization
- `person` maps to `PERSON`
- `backpack`, `handbag`, and `suitcase` map to `BAG`
- Rule surfaces use the normalized IDs that the runtime actually emits
Saved alert-rule inputs
Detector choices come from the active model metadata for that source, while anomaly choices come from the saved prompt payload rather than from the browser reading YAML.
Repository Guide
Read the runtime’s catalog explanation and the separation between the three zoos.
Read the guideInitialization Guide
Review how rules, prompts, and detector class options appear in the control plane.
Read the guide