Concepts
Trust ladder
The rules that decide when an owner has to prove themselves again, and what happens if they don't.
What starts a re-verification
- A model asks for it. For example,
owner-change/v1sees the device sleeping somewhere new. - The owner’s identity score reaches its threshold.
- A scheduled check comes due. These only start after 20 uses.
Straight away the device temp-locks, the owner gets an SMS, and they have 3 days.
Pass or fail
| Outcome | What happens |
|---|---|
| Pass | Back to active. Trust grows, more so for a quick answer: the score threshold rises from 5 up to 25, and scheduled checks space out from every 90 days to every 365. |
| Fail | A new 3-day window. |
| 3 fails, or deadline passed | Hard lock. Cleared by a location check plus a new face check, or by support. |
Where it runs
The trust ladder is one pure function with no database or clock. Ingest applies it right after the realtime models; owner-check applies it every morning, which is how deadlines fire even when a device is silent. School-zone locks are kept separate from it and combined at the end.