-
Notifications
You must be signed in to change notification settings - Fork 1
Modes and controls
Elliot edited this page Jul 28, 2026
·
1 revision
stateDiagram-v2
[*] --> Standalone
Standalone --> Sentinel: owner starts bounded observation
Standalone --> Ragnar: authenticated remote job selected
Standalone --> Intercept: verified connector selected
Standalone --> TAK: approved map workflow selected
Sentinel --> Standalone: session expires or stops
Ragnar --> Standalone: job completes, fails, or becomes stale
Intercept --> Standalone: connector becomes unavailable or job ends
TAK --> Standalone: submission completes, fails, or stops
Every mode is a status and control boundary, not permission for unrestricted hardware access. The OLED and field-control page show only verified state: queued, running, completed, failed, denied, timed out, stale, or unavailable.
| Mode | Purpose | Boundaries |
|---|---|---|
| Standalone | Local health, provisioning, and confirmed rules | No external deployment claim |
| Sentinel | Owner-started, time-bounded Wi-Fi/BLE summaries | No identity, pursuit, or raw identifier retention |
| Ragnar | Named Heltec-native observation for the remote Ragnar workflow | Ragnar never obtains generic radio control |
| Intercept | Verified sensor/connector result | Absent host hardware remains unavailable |
| TAK | Attributable preview/confirmation and shared map-event state | No automatic publication before policy and manual proof |