How to Use This Demo

The ecosystem is gated. Sign in as the universal owner (admin / admin@123) to acknowledge and dismiss alerts and to see the pipeline config; or as the read-only viewer, who sees the camera wall and queue but cannot act. From the launcher, open Property Security & Perimeter Monitoring. Unlike the other C5 apps, it brings its OWN dark control-room surface — navy with signal-amber and alert-red — a contained, AA-held rebind of the shared semantic theme tokens, not a design fork; the host header, theme controls and inspector still sit on top.

The camera wall shows each camera with a status ring: clear, watching, confirming, alert, or offline. Press a camera (or "Run all sweeps") to run the perimeter pipeline over its frame loop in the selected Cloud/OSS mode. The schematic frame view then renders the decisive frame as iconographic markers on a top-down field — person/vehicle in alert colour, staff/animal muted — never real footage. A camera whose track dwells past the confirm window flips to "alert" and raises an event.

Confirmed events land in the alert/ack queue with a severity badge (critical / warning / info), the kind (intrusion · vehicle-breach · loiter · tailgating), the zone, the dwell seconds, and the confidence. As owner you can Acknowledge or Dismiss an open event — both actions are audited; a viewer sees the queue read-only. Open "Behind the scenes" to see how a sweep was decided: the nine-stage trace, how many static frames the change-gate skipped at $0, the metered perceive cost and mode. The owner-only pipeline config (confirm window, confidence floor, change-gate delta) is absent from the DOM for viewers.