Meeting notes for P2P squad
2026/06/24
Attendance
Review Design Doc changes
- Changing focus of feature from “WiFi Hotspot” to “Data Sync” - emphasize on the data flow and not the details of how the data flows.
- Taxi concept - data carrier does not read, edit, classify the data it carries (the passenger).
- Transport is pluggable. Also does not matter who does the sync. Data-bundles are encrypted/signed by client device so does not matter how the data flows. (Can gate the user access to the syncing on the UI side with perms.)
- Data Checkpoints (how much to sync)
- Optimize initial flow for CHW > Supervisor flow - not going to try to solve generic data export.
- When supervisor uploads data bundle for CHW, supervisor gets and stores a checkpoint for that CHW’s data. When the CHW next syncs data to the Supervisor device, only need to sync since the checkpointer.
- API Endpoints:
- /api/v1/p2p/relay-bundle - need to make sure we upload user data bundles sequentially so that the checkpointer is advanced correctly and uploading some but not all bundles can be handled correctly.