Assumptions and Constraints
This document consolidates the operating assumptions and hard technical constraints that shape SAPOT's architecture. Each item already exists in an ADR, the threat model, or another architecture doc — this page exists so they can be read as one list instead of rediscovered piecemeal. Where a fuller rationale exists elsewhere, this page links to it rather than repeating it.
Component Map
Runtime topology
Data Flows
This document describes the key data flows in SAPOT. For the communication matrix see system-overview.md. For service topology see component-map.md.
Networking and LAN Model
SAPOT operates entirely on a local-area network without internet connectivity. This document describes how the network is structured and how devices communicate on it.
Security Architecture
---
System Overview
SAPOT is a LAN-first disaster-response communications platform. It is designed to operate entirely on a local-area network (LAN) managed by a MikroTik router, with no dependency on internet connectivity for its core functions.
Threat Model
SAPOT is deployed at disaster-response incident sites: a MikroTik router creates a standalone LAN, a laptop/server runs the FastAPI backend, and rescuers/civilians join with Android phones running the mobile app. This document defines the trust boundaries, in-scope attack surfaces, and known risks for that deployment shape.