Skip to content

Change tracking model

Recovery model

General Audience capability boundary

The General Audience build keeps the generic change-tracking model while removing the built-in Alcohol and Pornography/compulsive-sexual-behavior profiles, the SPAA section and Twelve-Step or literature-prompt resources. General or custom change areas remain compatible with counters, triggers, urges, resets and history.

flowchart TD
    CFG[Change-tracking configuration] --> A1[Change area]
    CFG --> A2[Another area]
    A1 --> C1[Counter]
    A1 --> C2[Counter]
    A2 --> C3[Counter]
    E[Urge or trigger] --> A1
    E --> A2

A counter belongs to exactly one stable change area. An urge or trigger event can refer to one or more areas. General daily data is not duplicated per area. When no change area is selected, the change-tracking view and related Today inputs are hidden.

Counter logic

Counter states are calculated from start and reset timestamps and the current time rather than being stored every day.

  • A counter starts only after a start point has been set explicitly.
  • The start date can be adjusted manually.
  • A reset is created only by a confirmed manual action or an urge explicitly stored as a relapse.
  • Reset history is retained.
  • A relapse can reset none, one or several counters.
  • Each counter can configure whether it is preselected in the relapse dialog.

An urge with a relapse and its selected counter resets are stored atomically. Either the complete operation succeeds or none of it is committed.

Urges, triggers and explicit zero check-ins

Triggers and urges are separate event types. A trigger records a possible cue and can exist without an urge. An actual urge has an intensity from 1 to 10.

  • At intensity 4 or above, reason, reaction and outcome are offered as optional details; the urge can still be saved immediately without them.
  • Only previous urge reasons are offered as reason suggestions. A newly entered reason is added to this separate local catalog; triggers remain separate.
  • Possible outcomes are subsided, weaker, unchanged, stronger or relapse.
  • Several selected change areas can be assigned to the same event.

Deliberate zero check-in

An explicitly stored intensity of 0 is not an urge event. It is a positive recovery check-in: “deliberately no urge.”

Important:

  • Only this explicitly stored zero check-in means “no urge.”
  • A completed day without a zero check-in remains unknown.
  • A completely missing day also remains unknown.
  • A later actual urge for the same day and change area atomically replaces the zero check-in.
  • A later stored zero does not silently delete an existing actual urge.
flowchart TD
    D[Day] --> Z{Explicit check-in?}
    Z -->|0 stored| F[no urge]
    Z -->|1–10 stored| U[urge event]
    Z -->|nothing stored| N[unknown]

History and Life Wheel interpretation

The history view can filter by change area and time range. It includes urge intensity, explicit zero check-ins, triggers, responses, outcomes, relapses and counter resets. Events assigned to several areas are not duplicated in the combined view.

A change-related Life Wheel signal is not a counter. It is a current product score derived from enabled fields and events in the analysis window. A relapse can supply a zero signal for that day, an explicit no-urge check-in supplies a positive signal, and actual urges use the strongest event of the day with a bounded outcome adjustment. The Life Wheel detail view keeps quality, quantity and momentum separate.

Sources