| Boundary | Proposed control | Evidence required | Status |
|---|---|---|---|
| Mechanical trap / aircraft | Capture and retention independent of cloud/app | Single-fault and power-loss tests | Concept only |
| Safety supervisor / mission planner | Independent containment, arm and ground-release checks | Common-cause and watchdog analysis plus HIL | Unimplemented |
| Phone/BLE/Wi-Fi | Phone requests mission; cannot bypass hardware safety envelope | Signed-command, pairing and link-loss tests | Unimplemented |
| Cloud/account | Minimal event history; no precise location uploaded by default | Privacy flow/deletion review | No account or service exists |
| Updates/configuration | Signed firmware and route/configuration version pinning | Rollback, integrity and regression evidence for each build | No firmware exists |
Sample — fictitious company. All numbers and people are invented scenario assumptions. This is draft concept paperwork; no physical testing, customer evidence, certification, filing or sign-off has occurred.