architecture docs
Concepts

Models

Detection logic is versioned. A new version is scored against simulated fleets before it replaces the live one.

What a model is

  • A function that reads one device’s events in time order and makes decisions, like “ask the owner to verify again” or “school lock”.
  • It runs either realtime (in ingest, on each message) or daily (in owner-check, every morning).
  • It never reads the clock. The runner adds “tick” events, so a model can act on “nothing happened by 06:00”.
  • The same code runs offline on datasets and live on real data, so the two can’t drift apart.
  • A version ID like owner-change/v1 is never reused.

Live models

owner-change/v1

daily
  • A night is 22:00 to 06:00, Montréal time.
  • The first 14 nights with data define “home”.
  • 4 nights in a row more than 1 km from home: ask the owner to verify again.

school-zone/v1

realtime
  • School hours: 07–09, 11:30–13:30 and 15–17, weekdays.
  • 3 precise positions in one of 405 Montréal zones within 15 minutes, not moving: lock.
  • Leaving, or the window ending: unlock.

How well they work

Scored on the sim-42 simulated fleet, with realistic firmware timing and accuracy.

Model Result Verdict
owner-change/v1 Finds all 7 handoffs. Precision 0.58: all 5 false alarms are week-long vacations. Detects a handoff about 87 hours after it happens. Usable, known limit
school-zone/v1 399 locks, only 72 on devices that visited a school. The zone list includes universities and colleges, and anyone living within 100 m of a school trips it. Not usable yet

A model’s life

  1. Write a new version Next to the old one, with a new ID and its own tests.
  2. Score it On the same simulated fleets as the live version: how many real cases it finds, how many false alarms, how fast. Saved runs show up in the admin.
  3. Promote it Switch the live version and deploy.