Offline Operation
When SOASAP Cloud or the network is unavailable, evaluation continues from the last local snapshot.
Most competitors document happy-path sync well but leave offline behavior vague. SOASAP treats offline as a first-class production scenario.
During an outage
- Reads use the last known snapshot — same O(1) path as online.
- Code-defined defaults apply only for keys that were never synced.
- SSE reconnects in the background when connectivity returns.
What to plan for
Document which flags are safe to freeze during extended outages (kill switches should default to off). Test by blocking outbound traffic to SOASAP in staging.
See Outages and Production Safety.