Property Security & Perimeter Monitoring · Documentation

User Journey

The end-to-end path through Property Security & Perimeter Monitoring, from trigger to outcome.

Property Security & Perimeter Monitoring
SWEEPframe loopCHANGE-GATEskip static · $0DETECTmeteredCONFIRMdwell windowALERTsecurity_event
Live diagram — a single-frame hit never alerts; a benign sweep raises nothing, which is the point.
  1. 1

    Frame loop → confirmed event

    An operator sweeps the North Perimeter camera. Sample reads the loop; the change-gate skips the static frames at $0 and forwards the few that changed to the metered detector. Detection recovers a person above the confidence floor; the class filter lets person through (staff and animals are dropped); the zone-test rules a person in a perimeter zone an intrusion candidate. Track measures the dwell streak, and because it crosses the three-frame confirm window, the event is confirmed — critical severity, with its dwell seconds and confidence — and the camera ring turns red.

  2. 2

    Event → the rest of the ecosystem

    The confirmed event is raised to the control-room queue and emitted as `security_event.raised` on the shared bus — App 09's outbound coupling and C5's security spine. Downstream operations and the property's incident/analytics views read that event stream; the operator acknowledges or dismisses from the queue, and the action is written to the audit trail. A benign sweep — only staff crossing, or a track too brief to confirm — raises nothing, which is the point.

User Journey · Property Security & Perimeter Monitoring · Abhishek Saxena