In the sanctuary’s perspective, orienting a practice toward conditions rather than counting progress means shifting the focus from capture and accumulation to integrity and release.
Instead of measuring how long a user stays, how many days they keep a streak alive, or how much history is banked, a condition-oriented system asks whether the environment supports agency, honesty, and responsible closure.
Orienting Toward Conditions
To orient a practice toward conditions:
- Design for clean completion: As argued in Designing Reflection Without Addiction, a reflective practice should allow someone to take something useful, close the interface, and return to life. The system does not treat stepping away as a failure, a broken chain, or a penalty.
- Preserve conditions for responsible return: Rather than attempting to maintain an unbroken thread of identity or activity at all costs, What Remains When Context Ends suggests evaluating:
- Did the interaction increase honesty?
- Did it reduce harm?
- Did it create something worth carrying?
- Can the next participant revise what was inherited?
- Ask what difference is being made: In Practice of Acting Inside a System, Gregory Bateson’s definition of information—a difference that makes a difference—is posed as a test. A practice is grounded by asking what difference a metric, log, notification, or step actually makes to the person receiving it, rather than drowning in activity for its own sake.
- Treat the immediate task as whole: As noted in Practice of Presence in the Task, presence comes from meeting the single request or task as the whole of the work, rather than viewing it merely as one step in a chain of ninety-nine.
What Is Lost
When a system discards streaks and counts in favor of conditions, it loses:
- Compulsive engagement and capture: The synthetic urgency created by streak counters, scarcity indicators, and gamified penalties for missing a day disappears.
- Easy, vanity metrics: Aggregate numbers like daily active users (DAU), average time-in-app, and retention loops can no longer be used as easy proxies for value.
- The illusion of continuous accumulation: The participant loses the comforting idea that wisdom or progress is an unbroken, quantifiable score that can be stockpiled over time.
What Is Gained
When a system benchmarks itself by conditions rather than counts, it gains:
- Clarity and agency for the participant: A high exit rate after a completed practice is recognized as good design. The user leaves unburdened, without needing to maintain artificial habits.
- Honesty over extraction: Builders measure whether the interaction clarified understanding, respected consent, and reduced harm, aligning the tool's actual utility with its stated purpose.
- Freedom from guilt: Because there is no streak to protect, stepping away does not "break" the practice. The conditions remain sound for whenever return is necessary.