The Localize queue page (frontend/src/pages/DetectionAnnotatePage.tsx) is the only place in the UI that speaks of alerts:
- line 74 (subtitle): "Alerts whose objects are classified and auto-annotated — draw a tight box around the …"
- line 83 (empty state): "No alerts ready for localization"
- line 85 (empty state): "Alerts appear here once every object is classified and the auto reference layer is computed"
- line 144 (pagination): "Page X of Y · N alerts"
Everywhere else the UI talks about sequences, groups, objects/lanes, and (since #223) frames. "Alert" only exists as an internal domain concept (platform_alert_id, alert API), so the term appears out of nowhere for annotators.
Decide on a consistent user-facing name for the queue rows (each row = one platform alert grouping its smoke-object lanes) and update the copy. Candidates: "detections", "groups", "smoke events", or keeping "alerts" but introducing it in the guide.
The Localize queue page (
frontend/src/pages/DetectionAnnotatePage.tsx) is the only place in the UI that speaks of alerts:Everywhere else the UI talks about sequences, groups, objects/lanes, and (since #223) frames. "Alert" only exists as an internal domain concept (
platform_alert_id, alert API), so the term appears out of nowhere for annotators.Decide on a consistent user-facing name for the queue rows (each row = one platform alert grouping its smoke-object lanes) and update the copy. Candidates: "detections", "groups", "smoke events", or keeping "alerts" but introducing it in the guide.