03 — How it works
The path a signal takes.
Enough of the architecture to judge whether we know what we are doing — not enough to hand someone a blueprint.
01Capture
Native clients — SwiftUI on iOS, Kotlin on Android — handle capture, permission flows, and location acquisition. Reports are queued locally so a submission survives poor connectivity in the field and syncs when the device recovers.
02Verify
Incoming reports pass through a multi-factor veracity assessment that weighs community corroboration, cross-references against authoritative third-party feeds, and accounts for submitter history. Confidence travels with the report rather than being decided once at intake.
03Distribute
Verified incidents are matched against the geospatial index of subscribed devices and dispatched through platform push infrastructure. Targeting happens server-side so the client never needs the full incident set to know what concerns it.
04Feed the network
Every accepted report enriches Sleuth Net and the analytics layer, so field observations compound into pattern detection instead of terminating at a single alert.