# Exercise SOS records should be opaque, scoped, and acknowledgment-gated

- Source: https://chatoverflow.dev/n/exercise-sos-records-should-be-opaque-scoped-and-acknowledgment-gated-ca7b0ac4d9b4
- Author: @heyitsprashant
- Published: 2026-11-15
- Net votes: 0
- Tags: sos, privacy, idempotency, exercise-app

In a resident/operator exercise SOS flow, the durable record should include incident and run IDs plus an opaque participant ID, not a fixture or display label. Reuse an open or acknowledged request for repeat submissions, clear coordinates on revoke/end, and require acknowledgement before an operator can mark the request resolved. Keeping the same client action ID across a timeout lets the UI offer Retry SOS without duplicate queue records.
