Renata Direct Subscriber Recovery Coach MVP Plan, Planning Only
Future MVP Purpose
Future Direct Subscriber Recovery Coach MVP is a non-clinical recovery structure companion concept. These are future product intentions only; no live support, chat, AI runtime, account, storage, billing, protected API, or protected live route exists.
What This Is Not
Current Boundary Status
Individual Mode status
future-planning-only
Public Packet Mode status
only-live-static-current-mode
Direct subscriber account status
not-created
Subscriber storage status
not-stored
Billing status
not-active
Checkout/payment provider status
not-active
Chat runtime status
not-implemented
AI runtime status
not-implemented
Recovery coach runtime status
not-implemented
Prompt endpoint status
not-created
Chat endpoint status
not-created
Protected API status
not-created
Protected live route status
not-created
Database status
not-active
Migration status
not-added
Crisis runtime status
not-implemented
Emergency-service runtime status
not-implemented
Private reflection storage status
not-stored
Check-in storage status
not-stored
Relapse-plan storage status
not-stored
Memory storage status
not-stored
Chat transcript storage status
not-stored
Clinical claims status
not-made
Treatment claims status
not-made
Diagnosis claims status
not-made
Live workflow activation status
no-go
Future MVP Capability Lanes
These lanes are planning labels only. They do not create chat, coaching behavior, storage, endpoints, accounts, or billing.
daily check-in / orientation
Future intent: May later help a subscriber orient the day around recovery structure, commitments, and practical next steps.
Safe use: Non-clinical reflection prompt and structure reminder owned by the subscriber.
Blocked interpretation: Not mood diagnosis, risk scoring, surveillance, compliance proof, or treatment monitoring.
Required future gate: Individual Mode safety, account, consent, privacy, data minimization, AI, crisis, and storage gates.
Current implementation effect: planning-only-not-active
evening reflection / review
Future intent: May later help a subscriber review the day, notice patterns, and plan a gentler next step.
Safe use: Private self-reflection support without judgment, clinical interpretation, or stored notes in this phase.
Blocked interpretation: Not therapy notes, clinical progress notes, case management, or staff-visible reporting.
Required future gate: Consent, retention/deletion/export, private data, and non-clinical language gates.
Current implementation effect: planning-only-not-active
routine builder
Future intent: May later help a subscriber shape simple routines around sleep, meals, meetings, movement, chores, and support contact.
Safe use: Optional structure suggestions that remain user-controlled and non-prescriptive.
Blocked interpretation: Not medical advice, medication advice, compliance checklist, or treatment plan.
Required future gate: Product safety, privacy, consent, user-control, and clinical-claims gates.
Current implementation effect: planning-only-not-active
values and commitment reminders
Future intent: May later help a subscriber remember personal values, recovery commitments, and chosen reasons for staying connected.
Safe use: Subscriber-owned language that supports agency without coercion.
Blocked interpretation: Not authority over recovery status, shame pressure, sponsor replacement, or staff instruction.
Required future gate: Autonomy, consent, deletion, private data, and language/confusion-risk gates.
Current implementation effect: planning-only-not-active
urge / trigger reflection
Future intent: May later help a subscriber name urges or triggers and choose a safe next action or human-support step.
Safe use: Reflection and support planning only, with clear escalation boundaries.
Blocked interpretation: Not relapse prediction, risk score, clinical triage, emergency handling, or medical advice.
Required future gate: Crisis/escalation, safety, clinical-claims, privacy, AI evaluation, and human-support gates.
Current implementation effect: planning-only-not-active
relapse-prevention planning aid
Future intent: May later help a subscriber outline personal prevention steps, warning signs, and support choices.
Safe use: Planning aid that encourages external support and user control.
Blocked interpretation: Not clinical treatment plan, relapse prediction, emergency service, or guarantee of recovery outcomes.
Required future gate: Non-clinical scope, crisis/escalation, data minimization, retention/deletion/export, and legal/privacy gates.
Current implementation effect: planning-only-not-active
repair and accountability writing support
Future intent: May later help a subscriber draft private repair-oriented language before sharing anything with a person or program.
Safe use: Private writing support focused on accountability, consent, tone, and harm reduction.
Blocked interpretation: Not legal advice, grievance process, punitive compliance, public shaming, or staff decision surface.
Required future gate: Language safety, privacy, consent, storage, legal-boundary, and Organization/Individual separation gates.
Current implementation effect: planning-only-not-active
human-support planning prompts
Future intent: May later remind a subscriber to contact sponsor, peer, clinician, emergency support, or other human support when appropriate.
Safe use: Encourages human connection while avoiding app-only crisis pathways.
Blocked interpretation: Not sponsor replacement, clinician replacement, emergency dispatch, or crisis handler.
Required future gate: Crisis/escalation copy, safety review, privacy review, and support-resource policy gates.
Current implementation effect: planning-only-not-active
recovery learning / psychoeducation boundary
Future intent: May later provide source-aware educational prompts or links about recovery structure where appropriate.
Safe use: General educational framing with transparent limitations and no treatment advice.
Blocked interpretation: Not clinical instruction, diagnosis, medication advice, legal advice, or invented resources.
Required future gate: Source policy, AI evaluation, clinical-claims, legal/privacy, and content governance gates.
Current implementation effect: planning-only-not-active
continuity / memory-like support boundary
Future intent: May later help a subscriber carry forward chosen goals, routines, preferences, and commitments.
Safe use: User-controlled continuity with clear consent, deletion, export, and minimization rules.
Blocked interpretation: Not hidden memory, surveillance, staff-visible tracking, risk scoring, or permanent sensitive storage.
Required future gate: Private data, consent, retention/deletion/export, security, and user-control gates.
Current implementation effect: planning-only-not-active
user-owned progress review
Future intent: May later let a subscriber privately reflect on what helped, what was hard, and what they want to try next.
Safe use: Private self-review that avoids grades, rankings, compliance metrics, or performance judgments.
Blocked interpretation: Not clinical outcome measurement, compliance scoring, relapse score, staff dashboard, or patient monitoring.
Required future gate: Privacy, data minimization, clinical-claims, analytics prohibition, and user-control gates.
Current implementation effect: planning-only-not-active
AI and Prompt Boundary
Status: not-implemented
Boundary status: future-gate-required
Future AI use is only a separately gated possibility. No AI runtime, prompt endpoint, chat endpoint, saved prompt, saved completion, transcript storage, or memory storage exists.
Blocked Now
- no OpenAI processing for direct-subscriber content
- no prompt endpoint
- no chat endpoint
- no streaming response endpoint
- no recovery coach runtime
- no saved prompts
- no saved completions
- no transcript storage
- no memory storage
- no risk scoring
- no clinical judgment
- no diagnosis/treatment advice
- no hallucinated facts or invented resources
Future Requirements
- non-clinical language
- source-aware only where appropriate
- transparent limitations
- user autonomy
- escalation-aware behavior
- privacy/consent review
- prompt evaluation
- red-team/safety testing
- cost/budget gating
- data minimization
- deletion/export rights before storage
Crisis / Emergency Boundary
Status: not-implemented
Boundary status: future-gate-required
This phase documents only the future safety boundary. It adds no crisis detection, hotline lookup, crisis workflow, risk scoring, clinical triage, or emergency dispatch.
Non-Scope
- No crisis detection is implemented.
- No local hotline lookup is implemented.
- No country-specific emergency content is implemented.
- No crisis workflow is implemented.
- No crisis triage, risk scoring, clinical judgment, or emergency dispatch exists.
Future Runtime Rules
- The app must not be the sole crisis pathway.
- Future runtime must stop normal coaching for self-harm, overdose, withdrawal emergency, violence, immediate danger, medical emergency, or emergency legal danger.
- Future runtime must direct users to emergency services or separately reviewed crisis resources through a reviewed safety flow.
- Future runtime must not frame AI-generated coaching as emergency support.
Private Data and Consent Boundary
These are future private data labels only. No private Individual Mode data is collected, stored, exported, downloaded, or shared.
check-ins
Current storage status: not-stored
Future storage requires explicit consent, data minimization, retention/deletion/export policy, security review, and user control before runtime.
reflections
Current storage status: not-stored
Future storage requires explicit consent, data minimization, retention/deletion/export policy, security review, and user control before runtime.
relapse-prevention plans
Current storage status: not-stored
Future storage requires explicit consent, data minimization, retention/deletion/export policy, security review, and user control before runtime.
craving/trigger notes
Current storage status: not-stored
Future storage requires explicit consent, data minimization, retention/deletion/export policy, security review, and user control before runtime.
values/commitment notes
Current storage status: not-stored
Future storage requires explicit consent, data minimization, retention/deletion/export policy, security review, and user control before runtime.
routines
Current storage status: not-stored
Future storage requires explicit consent, data minimization, retention/deletion/export policy, security review, and user control before runtime.
chat transcripts
Current storage status: not-stored
Future storage requires explicit consent, data minimization, retention/deletion/export policy, security review, and user control before runtime.
memory-like continuity
Current storage status: not-stored
Future storage requires explicit consent, data minimization, retention/deletion/export policy, security review, and user control before runtime.
support contacts or human-support plans
Current storage status: not-stored
Future storage requires explicit consent, data minimization, retention/deletion/export policy, security review, and user control before runtime.
Direct Subscriber Commercial Boundary
Status: planning-only-inactive
Individual Mode may later support direct subscription only after separate commercial, privacy, safety, legal, product, and technical review.
Organization Mode Separation
Status: separated-by-default
Direct-subscriber private content is separated from Organization Mode by default.
- Direct Subscriber Recovery Coach content is separate from Organization Mode by default.
- Organization Mode must not see Individual Mode private reflections, check-ins, relapse plans, memories, or coach transcripts by default.
- Any future sharing requires separate explicit consent, privacy review, legal review, product review, and technical review.
- No cross-mode sharing bridge is implemented.
- No organization tenant, staff dashboard, review queue, or analytics surface can inspect direct-subscriber private data.
Stop Conditions
- someone asks to add chat boxes, textareas, inputs, forms, or submit controls
- someone asks to create subscriber accounts, login, signup, or identity capture
- someone asks to add billing, checkout, Stripe/payment provider, lead capture, or CRM
- someone asks to store check-ins, reflections, relapse plans, memories, support contacts, or chat transcripts
- someone asks to add OpenAI processing for direct-subscriber content
- someone asks to add prompt/chat endpoints or protected APIs
- someone asks to add protected live routes
- someone asks to add migrations or database reads/writes
- someone asks to add crisis detection, hotline lookup, crisis routing, or emergency workflows
- someone asks to frame the coach as therapy, treatment, diagnosis, emergency support, sponsor replacement, clinician replacement, case management, or recovery authority
- someone asks to bridge Individual Mode private content into Organization Mode without separate consent/legal/privacy review
What Remains Blocked
Recommended Next Phase
Phase 11.17 - Individual Mode Handoff Freeze, Planning Only
Status: planning-only
After the Individual Mode static closure note is documented as a no-go planning artifact, future planning should freeze the handoff order and no-go language for outside-app review without creating handoff records, approvals, readiness records, protected APIs, storage, or live workflows.