Skip to content
// signal 03 · zones · in the pipeline

One polygon.
One rule.

Zone intelligence is the in-the-pipeline layer that turns any camera into a virtual fence. Time-aware polygon rules are designed to trigger a local alert the instant a boundary is crossed, on the box, with no cloud and no per-camera subscription.

03
// signal 03 · zones
restricted
one polygon · one rule
  • in the pipeline
  • in the pipeline
  • in the pipeline
  • in the pipeline
  • in the pipeline
  • in the pipeline
// zones · in one paragraph

Zones are how a perimeter actually thinks. A loading bay is restricted after 9 pm. The pool deck is empty after midnight. The CFO's parking slot is one car.

Atlas is designed to let you draw those rules visually, store them locally, and have them enforced on every frame of every camera, all on the same edge box you deploy for vehicles.

// draw a zone

One polygon. One rule. One alert.

// draw a zone

One polygon. One rule.

For illustrative purposes only.

rec · gate cam 0214:02:37 IST
click to drop corners · dashed = example zone
zone consoleready

01 · time-of-day rule

window21:00 – 24:00
scene clock14:02 · active

02 · zone

cornersexample
statususe example
evalpoint-in-polygon · on-box

Draw a zone over the gate, pick a rule, then Run. If the dot enters the zone while the rule is active, Atlas trips a local breach. For illustrative purposes only.

// capabilities

What Atlas does
for zones.

01
Polygon authoring

Click corners on the camera image to draw any zone shape. Per-camera, per-time-of-day, per-day-of-week rules.

02
Rule engine

If <object> enters <zone> during <window>, then <action>. Actions: log, alert the guard, webhook, or society-app integration.

03
Multi-zone composition

Zones can be nested or exclusive. A car entering the visitor lane that drifts into the resident-only ramp triggers a different rule.

04
Local alerting

From boundary cross to guard-station ping over the local network: no cloud hop, no Indian-internet variance, no outage downtime.

05
Audit chain per rule

Every rule edit is signed and timestamped. An auditor can see who changed what, and when.

06
Replay & tuning

Replay any incident frame-by-frame to tune the polygon, reducing false positives without re-training a model.

// what the pilot proves

Built for the conditions, measured in the pilot.

The pilot protocol →
By design · local-first
The boom doesn't wait for the cloud.

Because rules run on the edge box, a breach is detected and a guard is pinged over the local network, even when the site's internet link is down. The cloud is for the dashboard, never for the gate alert.

on-boxrule evaluation, no cloud hop
By design · access-controlled
Every rule edit is on the record.

Zone definitions and edits are part of the same access-controlled audit log as vehicle events, so a change to who-can-go-where is itself auditable. That is the difference between a policy and a paper SOP.

signedrule history in the audit chain
// see it run

An interactive walk-through,
no sign-up.

An interactive zone-and-person breach preview, on the same edge platform.