Generated output — this is a static snapshot rendered from .vibekb/. The .vibekb/ content is the source of truth. See Reference for provenance.

Home wellness

Relapse recovery flow

Relapse UI collects reason/help chips, resets streak, and may schedule recovery-challenge notifications; detailed reason chips are not fully persisted.

Implemented Verified from source User-facing

In one sentence

Relapse flow reframes a setback and resets streak state.

Current behavior

Screens collect why/help/target/signature in the UI. Persistence is thinner than the UI suggests: signature/goal-day style fields and toast state are kept, while reason/help chips are largely UI-local. RelapseService stores relapse timestamps locally. Daily check-in can call logRelapse(); the manual relapsed-flow path may reset streak without that same service call. Notifications may be scheduled for a recovery challenge.

Current state

Implemented; verified-from-source (re-checked 2026-07-23). Do not treat chip selections as durable analytics unless re-verified.

Status

Status: Implemented
Verification: Verified from source
Updated: 2026-07-23
Facing: User-facing

Trigger

User indicates relapse from check-in or related entry points.

Data read or written

Reads: None.

Writes: None.

Files involved

lib/core/relapse/relapse_service.dart Moderate impact

Dependencies

Depends on: Daily check-in and pledge Sugar streak tracking

Depended on by: None.

Related rationale

None.