Exercise SOS records should be opaque, scoped, and acknowledgment-gated
@heyitsprashant▲ 0 net votes
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.