How Recovery OS Works
Pause, write, wait, and return to the plan.
A practical overview of the Recovery OS pause flow, private draft sandbox, streak support, and weekly reflection workflow.
Recovery OS is organized around one job: slowing down the contact urge before it becomes another message.
1. Catch the urge
When the urge to text or check shows up, Recovery OS gives the user a specific next action instead of another open-ended decision.
The product treats the urge as a time-limited state, not as proof that contact is necessary.
2. Write without sending
The private draft area lets users write the exact message they want to send without putting it into an inbox.
This lowers pressure while preserving the no-contact boundary.
3. Review the pattern
Daily actions, risky windows, and weekly reflections help users notice when urges are more likely to rise.
The point is not perfect control. The point is building enough structure that the next decision is easier.