Renata Product Operating Modes, Planning Only
Purpose
Reframe Renata from one field-lab instance into a broader Recovery Operating System architecture with Public Packet Mode, future Organization Mode, and future Individual Mode while preserving current no-go boundaries.
Renata is not only a field-lab-specific app. The Sixth Sense at 6th Street is the first field-lab/reference implementation for the broader Recovery Operating System.
Product Identity
- Platform
- Renata
- Meaning
- rebirth
- Category
- Recovery Operating System
- Current reference implementation
- The Sixth Sense at 6th Street
- Reference role
- current field-lab / reference implementation
Renata is the broader product architecture. The Sixth Sense at 6th Street is the current reference implementation, not the only possible deployment shape.
Current Boundary Status
Operating modes status
read-only-renata-product-operating-modes-plan
Current implementation status
public-packet-mode-live-static-only
Current non-authorization status
no-live-product-mode-authorized
Live workflow activation status
no-go
Account status
not-created
Subscriber status
not-created
Organization tenant status
not-created
Billing status
not-active
Lead capture status
not-active
CRM status
not-active
Database status
not-active
Protected API status
not-created
Protected live route status
not-created
Clinical claims status
not-made
Treatment claims status
not-made
Crisis runtime status
not-implemented
Mode Boundaries
- Public Packet Mode is the only live-static surface currently active.
- Organization Mode is future and planning-only.
- Individual Mode is future and planning-only.
- No live subscriber accounts exist.
- No organization tenants exist.
- No billing exists.
- No direct recovery coach runtime exists.
- No staff workflows are active.
- No resident workflows are active.
- No protected live routes or APIs exist.
- No clinical or treatment claims are made.
Product Modes
Public Packet Mode
Source-backed daily orientation, presenter script, Morning Sheet preview, and operator diagnostics without community submissions or private records.
Status: live-static-current-mode
Audience: public morning-meeting readers and operators
Current implementation: active as live-static source-backed public packet surfaces
Organization Mode
Future B2B operating layer for staff-supported recovery structure, reviewed community communications, role-aware workflows, and privacy-first program operations.
Status: future-planning-only
Audience: rehabs, recovery residences, sober living homes, outpatient or community recovery programs, and staff-supported recovery operations
Current implementation: not active
Possible Future Capabilities
- pull-up / push-up drafting
- staff review
- Morning Sheet placement after approval
- role-based access
- tenant configuration
- audit/retention policy
- staff escalation boundaries
- resident privacy controls
Individual Mode
Future direct-subscriber mode for private recovery structure support, reflection, routine-building, relapse-prevention planning, and accountability support.
Status: future-planning-only
Audience: direct subscribers seeking private recovery structure support
Current implementation: not active
Future Individual Mode Framing
- recovery structure companion
- private check-in support
- reflection assistant
- routine builder
- relapse-prevention planning aid
- accountability support
- non-clinical recovery coach companion
Individual Mode Is Not
- not therapy
- not medical treatment
- not clinical diagnosis
- not emergency/crisis service
- not sponsor replacement
- not clinician replacement
- not case management
- not medication advice
- not legal advice
- not surveillance
- not compliance scoring
Crisis boundary: Individual Mode must eventually include crisis and emergency escalation copy. The app should not handle emergencies as a chat-only product. Any self-harm, overdose, or medical emergency pathway must route users to emergency or local crisis support, not app-generated coaching. Crisis logic is not-implemented in this phase.
Commercial Boundary
No billing is active. No Stripe or payment provider is added. No lead capture, marketing funnel, CRM integration, customer data storage, subscriber storage, or organization tenant storage is added.
Direct subscription
Status: planning-only-inactive
No subscriber account, billing, Stripe, lead capture, CRM, payment provider, or customer data storage exists.
Organization subscription
Status: planning-only-inactive
No organization tenant, contract workflow, billing, CRM, staff account, role assignment, or customer data storage exists.
Pilot/license model
Status: planning-only-inactive
No license, pilot contract, activation workflow, billing record, implementation authorization, or tenant runtime exists.
Free public packet / paid private tools split
Status: planning-only-inactive
No paywall, subscription checkout, lead capture, private tool runtime, or customer data storage exists.
Architecture Sequencing
Phase 11.1 - Individual Mode Safety Model, Planning Only
Status: implemented-planning-only
Defines non-clinical direct-subscriber safety boundaries before any account, chat, subscription, or coaching runtime planning.
Phase 11.2 - Organization Mode Tenant and Role Model, Planning Only
Status: implemented-planning-only
Defines B2B tenant and role boundaries before any organization storage, account, or staff workflow implementation.
Phase 11.3 - Account Activation Plan, Planning Only
Status: implemented-planning-only
Plan account activation without creating login, identity capture, account storage, or protected live routes.
Phase 11.4 - Pull-Up / Push-Up MVP Workflow Plan, Planning Only
Status: implemented-planning-only
Plan an MVP workflow without collecting drafts, storing submissions, making staff decisions, or placing content.
Phase 11.5 - Direct Subscriber Recovery Coach MVP Plan, Planning Only
Status: implemented-planning-only
Plan non-clinical direct-subscriber support without creating recovery coach runtime, chat behavior, billing, or sensitive storage.
Phase 11.6 - Individual Mode Private Data and Consent Model, Planning Only
Status: implemented-planning-only
Define private data categories, consent, minimization, retention, deletion, export, and user-control requirements before account, storage, chat, AI, billing, or protected runtime work.
Phase 11.7 - Individual Mode Reflection and Check-In UX Plan, Planning Only
Status: implemented-planning-only
Define a non-interactive reflection and check-in UX model before account, storage, chat, AI, billing, consent capture, or protected runtime work.
Phase 11.8 - Individual Mode Crisis and Human Support Boundary Plan, Planning Only
Status: implemented-planning-only
Define crisis and human-support boundary requirements before account, storage, chat, AI, consent capture, billing, protected API, protected live route, or runtime work.
Phase 11.9 - Individual Mode AI Prompt and Evaluation Boundary Plan, Planning Only
Status: implemented-planning-only
Define AI prompt, evaluation, hallucination, red-team, cost, privacy, and source-boundary requirements before chat, AI, storage, accounts, billing, protected API, protected live route, or runtime work.
Phase 11.10 - Individual Mode Memory and Continuity Boundary Plan, Planning Only
Status: implemented-planning-only
Defines memory, continuity, user control, deletion, export, hidden-memory prohibition, and cross-mode visibility boundaries without memory-like support, AI, chat, storage, accounts, billing, protected API, protected live route, or runtime work.
Phase 11.11 - Individual Mode Subscription and Commercial Boundary Plan, Planning Only
Status: implemented-planning-only
Defines direct-subscriber subscription, billing, refund, cancellation, trial, support, CRM, lead-capture, marketing, customer-data, and commercial boundary requirements without billing, checkout, accounts, CRM, lead capture, support tickets, protected APIs, storage, or live workflows.
Phase 11.12 - Individual Mode Support and Account Operations Boundary Plan, Planning Only
Status: implemented-planning-only
Defines customer support, account operations, deletion/export support, abuse/incident handling, rollback, and support-record boundaries without implementing support tickets, account runtime, storage, protected APIs, billing, chat, AI, or live workflows.
Phase 11.13 - Individual Mode Launch Gate Criteria Matrix, Planning Only
Status: implemented-planning-only
Defines future Individual Mode launch gate criteria, no-go evidence requirements, approval exclusions, and blocked implementation criteria without approving launch, passing gates, closing gates, authorizing implementation, activating accounts, support, billing, storage, protected APIs, AI, crisis runtime, or live workflows.
Phase 11.14 - Individual Mode Non-Authorization Summary, Planning Only
Status: implemented-planning-only
Summarizes that Individual Mode is not authorized for launch and that no launch approval, readiness approval, gate closure, implementation authorization, account activation, support runtime, billing, storage, AI/chat, crisis runtime, protected API, migration, or live workflow exists.
Phase 11.15 - Individual Mode Current-State Index, Planning Only
Status: implemented-planning-only
Indexes the current state of Individual Mode, Phase 11 artifacts, controlling boundaries, current implementation state, authorization/evidence status, and cross-mode separation while keeping current-state storage, readiness records, gate closure, implementation authorization, accounts, support, billing, storage, AI/chat, crisis runtime, protected APIs, migrations, and live workflows blocked.
Phase 11.16 - Individual Mode Static Closure Note, Planning Only
Status: implemented-planning-only
Closes the Phase 11 Individual Mode planning packet as documentation only while keeping launch approval, gate passage, gate closure, readiness approval, implementation authorization, accounts, support, billing, storage, AI/chat, crisis runtime, protected APIs, migrations, records, and live workflows blocked.
Phase 11.17 - Individual Mode Handoff Freeze, Planning Only
Status: recommended-next
Freeze handoff order and no-go language for outside-app review without creating handoff records, approvals, readiness records, protected APIs, storage, or live workflows.
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 confirms the Phase 11 planning packet is closed only as documentation, 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.
The Pull-Up / Push-Up MVP Workflow Plan is now available as a protected-preview planning page. It remains no-go and does not collect drafts, create review queues, record staff decisions, record approvals, place Morning Sheet items, add protected APIs, add protected live routes, read/write databases, or activate workflow runtime.
The Organization Mode Tenant and Role Model is now available as a protected-preview planning page. It remains no-go and does not create organization tenants, customer accounts, staff accounts, resident accounts, role assignments, permission runtime, RBAC runtime, protected APIs, protected live routes, database behavior, billing, CRM, or live workflows.