Renata Individual Mode Current-State Index, Planning Only
Purpose and No-Go Status
Create a single current-state orientation index for the Individual Mode Phase 11 planning stack. The index helps reviewers see which artifacts exist, which boundary each artifact governs, what is currently live, what is not implemented, what remains not authorized, and what future outside-app evidence would be required before any runtime work could be considered.
This page is a current-state orientation/index only. It does not create authoritative state, store state, approve launch, pass or close gates, authorize implementation, activate accounts, or create runtime.
Current Operating-Mode Summary
Public Packet Mode status
only-live-static-current-mode
Individual Mode status
future-planning-only
Organization Mode status
future-planning-only
Individual Mode launch status
not-authorized
Launch approval status
not-approved
Readiness approval status
not-approved
Gate closure status
none-closed
Implementation authorization status
not-authorized
Runtime activation status
no-go
Current-state record status
not-created
Status storage status
not-stored
Readiness record status
not-created
Evidence record status
not-created
Approval record status
not-created
All values are static labels only. They are not loaded from or written to a database, status record, account, session, API, or runtime system.
Phase 11 Artifact Index
11.0. Renata Product Operating Modes
Defines Renata as the broader Recovery Operating System with Public Packet, Organization, and Individual Mode planning boundaries.
- Controlling boundary
- Product-mode separation
- Current posture
- implemented-planning-only / read-only / no-go
- Does not authorize
- Does not authorize accounts, subscribers, tenants, billing, protected APIs, protected live routes, storage, or runtime activation.
- Relationship to this index
- Indexed as a static orientation reference only; this index does not make the artifact authoritative runtime state, approval evidence, gate closure, or implementation authorization.
11.1. Individual Mode Safety Model
Defines non-clinical Individual Mode safety domains, crisis boundary needs, privacy reminders, and stop conditions.
- Controlling boundary
- Individual Mode safety and non-clinical scope
- Current posture
- implemented-planning-only / read-only / no-go
- Does not authorize
- Does not authorize therapy, treatment, diagnosis, crisis service, AI runtime, chat, accounts, billing, or storage.
- Relationship to this index
- Indexed as a static orientation reference only; this index does not make the artifact authoritative runtime state, approval evidence, gate closure, or implementation authorization.
11.2. Organization Mode Tenant and Role Model
Defines future Organization Mode tenant labels, role labels, staff-supported boundaries, and Organization/Individual separation.
- Controlling boundary
- Organization Mode tenant and role boundaries
- Current posture
- implemented-planning-only / read-only / no-go
- Does not authorize
- Does not create tenants, accounts, role assignments, permission runtime, RBAC, billing, CRM, protected APIs, protected live routes, or storage.
- Relationship to this index
- Indexed as a static orientation reference only; this index does not make the artifact authoritative runtime state, approval evidence, gate closure, or implementation authorization.
11.3. Account Activation Plan
Defines account category labels, identity/auth questions, cross-mode account boundaries, and future protected route/API sequencing.
- Controlling boundary
- Account activation sequencing
- Current posture
- implemented-planning-only / read-only / no-go
- Does not authorize
- Does not create accounts, login, signup, identity capture, permissions, RBAC, protected APIs, protected live routes, migrations, or storage.
- Relationship to this index
- Indexed as a static orientation reference only; this index does not make the artifact authoritative runtime state, approval evidence, gate closure, or implementation authorization.
11.4. Pull-Up / Push-Up MVP Workflow Plan
Defines future Organization Mode pull-up/push-up draft, review, visibility, consent, and safety boundaries.
- Controlling boundary
- Pull-up/push-up workflow boundaries
- Current posture
- implemented-planning-only / read-only / no-go
- Does not authorize
- Does not collect pull-ups, push-ups, drafts, submissions, names, review queues, staff decisions, approvals, Morning Sheet placement, tracking, scoring, or storage.
- Relationship to this index
- Indexed as a static orientation reference only; this index does not make the artifact authoritative runtime state, approval evidence, gate closure, or implementation authorization.
11.5. Direct Subscriber Recovery Coach MVP Plan
Defines future non-clinical direct-subscriber recovery structure companion intent and blocked runtime capabilities.
- Controlling boundary
- Direct-subscriber MVP intent
- Current posture
- implemented-planning-only / read-only / no-go
- Does not authorize
- Does not create recovery coach runtime, AI runtime, chat, subscriber accounts, billing, private storage, protected APIs, protected live routes, or crisis runtime.
- Relationship to this index
- Indexed as a static orientation reference only; this index does not make the artifact authoritative runtime state, approval evidence, gate closure, or implementation authorization.
11.6. Individual Mode Private Data and Consent Model
Defines private data labels, consent/user-control requirements, minimization, retention, deletion, export, AI, crisis, commercial, and cross-mode sharing boundaries.
- Controlling boundary
- Private data, consent, minimization, and cross-mode sharing
- Current posture
- implemented-planning-only / read-only / no-go
- Does not authorize
- Does not capture consent, create consent records, store private recovery data, process AI content, create billing, or expose Individual Mode data to Organization Mode.
- Relationship to this index
- Indexed as a static orientation reference only; this index does not make the artifact authoritative runtime state, approval evidence, gate closure, or implementation authorization.
11.7. Individual Mode Reflection and Check-In UX Plan
Defines non-interactive future reflection/check-in UX anatomy, prompt-language boundaries, autonomy rules, and privacy reminders.
- Controlling boundary
- Reflection/check-in UX anatomy
- Current posture
- implemented-planning-only / read-only / no-go
- Does not authorize
- Does not render forms, inputs, chat boxes, check-ins, reflections, consent capture, storage, AI runtime, crisis runtime, billing, or live workflows.
- Relationship to this index
- Indexed as a static orientation reference only; this index does not make the artifact authoritative runtime state, approval evidence, gate closure, or implementation authorization.
11.8. Individual Mode Crisis and Human Support Boundary Plan
Defines urgent-risk categories, human-support pathways as labels, normal coaching stop rules, and crisis boundary preservation.
- Controlling boundary
- Crisis and human-support boundaries
- Current posture
- implemented-planning-only / read-only / no-go
- Does not authorize
- Does not implement crisis detection, hotline lookup, local emergency content, triage, dispatch, emergency routing, risk scoring, support-contact storage, or crisis runtime.
- Relationship to this index
- Indexed as a static orientation reference only; this index does not make the artifact authoritative runtime state, approval evidence, gate closure, or implementation authorization.
11.9. Individual Mode AI Prompt and Evaluation Boundary Plan
Defines AI capability labels, prompt constraints, evaluation/red-team requirements, hallucination/source boundaries, and privacy gates.
- Controlling boundary
- AI prompt, evaluation, hallucination, and source boundaries
- Current posture
- implemented-planning-only / read-only / no-go
- Does not authorize
- Does not create AI runtime, OpenAI processing, prompt endpoints, chat endpoints, streaming endpoints, model calls, eval scripts, prompt storage, completion storage, or transcript storage.
- Relationship to this index
- Indexed as a static orientation reference only; this index does not make the artifact authoritative runtime state, approval evidence, gate closure, or implementation authorization.
11.10. Individual Mode Memory and Continuity Boundary Plan
Defines memory-like category labels, user control, deletion/export requirements, hidden-memory prohibition, and cross-mode visibility boundaries.
- Controlling boundary
- Memory, continuity, user control, and hidden-memory prohibition
- Current posture
- implemented-planning-only / read-only / no-go
- Does not authorize
- Does not create memory runtime, memory storage, hidden memory, embeddings, retrieval memory, saved preferences, saved routines, saved transcripts, or OpenAI processing.
- Relationship to this index
- Indexed as a static orientation reference only; this index does not make the artifact authoritative runtime state, approval evidence, gate closure, or implementation authorization.
11.11. Individual Mode Subscription and Commercial Boundary Plan
Defines direct-subscriber subscription, billing, refund, cancellation, support, CRM, lead-capture, marketing, and customer-data boundaries.
- Controlling boundary
- Subscription, commercial, billing, and CRM separation
- Current posture
- implemented-planning-only / read-only / no-go
- Does not authorize
- Does not create billing, checkout, Stripe/payment provider integration, customer portal, trial signup, CRM, lead capture, support tickets, customer records, or commercial runtime.
- Relationship to this index
- Indexed as a static orientation reference only; this index does not make the artifact authoritative runtime state, approval evidence, gate closure, or implementation authorization.
11.12. Individual Mode Support and Account Operations Boundary Plan
Defines future support/account-operations labels, support-record confidentiality, abuse/incident handling, rollback, and account-support boundaries.
- Controlling boundary
- Support, account operations, confidentiality, and rollback boundaries
- Current posture
- implemented-planning-only / read-only / no-go
- Does not authorize
- Does not create support tickets, support inboxes, account access, impersonation, deletion/export workflows, abuse/incident workflows, rollback execution, support records, or account runtime.
- Relationship to this index
- Indexed as a static orientation reference only; this index does not make the artifact authoritative runtime state, approval evidence, gate closure, or implementation authorization.
11.13. Individual Mode Launch Gate Criteria Matrix
Defines future launch gate labels, outside-app evidence requirements, approval exclusions, and blocked implementation criteria.
- Controlling boundary
- Launch gate criteria and evidence requirements
- Current posture
- implemented-planning-only / read-only / no-go
- Does not authorize
- Does not approve launch, pass gates, close gates, record approvals, authorize implementation, activate runtime, or create evidence repositories.
- Relationship to this index
- Indexed as a static orientation reference only; this index does not make the artifact authoritative runtime state, approval evidence, gate closure, or implementation authorization.
11.14. Individual Mode Non-Authorization Summary
Summarizes that the complete planning stack is not launch approval, not readiness approval, not gate closure, and not implementation authorization.
- Controlling boundary
- Non-authorization posture
- Current posture
- implemented-planning-only / read-only / no-go
- Does not authorize
- Does not authorize launch, runtime, accounts, support, billing, storage, AI/chat, crisis handling, protected APIs, protected live routes, database behavior, migrations, forms, or live workflows.
- Relationship to this index
- Indexed as a static orientation reference only; this index does not make the artifact authoritative runtime state, approval evidence, gate closure, or implementation authorization.
Controlling-Boundary Map
This map is descriptive only. It is not an executable policy registry, permission system, feature flag, runtime gate, or route controller.
Product-mode separation
- Controls
- Phase 11.0 - Renata Product Operating Modes
- Map status
- descriptive-only
- Implementation effect
- Does not act as an executable policy registry, permission system, feature flag, runtime gate, or route controller.
Individual Mode safety/non-clinical scope
- Controls
- Phase 11.1 - Individual Mode Safety Model
- Map status
- descriptive-only
- Implementation effect
- Does not act as an executable policy registry, permission system, feature flag, runtime gate, or route controller.
Organization Mode tenant/role boundaries
- Controls
- Phase 11.2 - Organization Mode Tenant and Role Model
- Map status
- descriptive-only
- Implementation effect
- Does not act as an executable policy registry, permission system, feature flag, runtime gate, or route controller.
Account activation sequencing
- Controls
- Phase 11.3 - Account Activation Plan
- Map status
- descriptive-only
- Implementation effect
- Does not act as an executable policy registry, permission system, feature flag, runtime gate, or route controller.
Pull-up/push-up workflow boundaries
- Controls
- Phase 11.4 - Pull-Up / Push-Up MVP Workflow Plan
- Map status
- descriptive-only
- Implementation effect
- Does not act as an executable policy registry, permission system, feature flag, runtime gate, or route controller.
Direct-subscriber MVP intent
- Controls
- Phase 11.5 - Direct Subscriber Recovery Coach MVP Plan
- Map status
- descriptive-only
- Implementation effect
- Does not act as an executable policy registry, permission system, feature flag, runtime gate, or route controller.
Private data/consent/minimization/cross-mode sharing
- Controls
- Phase 11.6 - Individual Mode Private Data and Consent Model
- Map status
- descriptive-only
- Implementation effect
- Does not act as an executable policy registry, permission system, feature flag, runtime gate, or route controller.
Reflection/check-in UX anatomy
- Controls
- Phase 11.7 - Individual Mode Reflection and Check-In UX Plan
- Map status
- descriptive-only
- Implementation effect
- Does not act as an executable policy registry, permission system, feature flag, runtime gate, or route controller.
Crisis and human-support boundaries
- Controls
- Phase 11.8 - Individual Mode Crisis and Human Support Boundary Plan
- Map status
- descriptive-only
- Implementation effect
- Does not act as an executable policy registry, permission system, feature flag, runtime gate, or route controller.
AI prompt/evaluation/hallucination/source boundaries
- Controls
- Phase 11.9 - Individual Mode AI Prompt and Evaluation Boundary Plan
- Map status
- descriptive-only
- Implementation effect
- Does not act as an executable policy registry, permission system, feature flag, runtime gate, or route controller.
Memory/continuity/user-control/hidden-memory prohibition
- Controls
- Phase 11.10 - Individual Mode Memory and Continuity Boundary Plan
- Map status
- descriptive-only
- Implementation effect
- Does not act as an executable policy registry, permission system, feature flag, runtime gate, or route controller.
Subscription/commercial/billing/CRM separation
- Controls
- Phase 11.11 - Individual Mode Subscription and Commercial Boundary Plan
- Map status
- descriptive-only
- Implementation effect
- Does not act as an executable policy registry, permission system, feature flag, runtime gate, or route controller.
Support/account operations/confidentiality/rollback boundaries
- Controls
- Phase 11.12 - Individual Mode Support and Account Operations Boundary Plan
- Map status
- descriptive-only
- Implementation effect
- Does not act as an executable policy registry, permission system, feature flag, runtime gate, or route controller.
Launch gate criteria/evidence requirements
- Controls
- Phase 11.13 - Individual Mode Launch Gate Criteria Matrix
- Map status
- descriptive-only
- Implementation effect
- Does not act as an executable policy registry, permission system, feature flag, runtime gate, or route controller.
Non-authorization posture
- Controls
- Phase 11.14 - Individual Mode Non-Authorization Summary
- Map status
- descriptive-only
- Implementation effect
- Does not act as an executable policy registry, permission system, feature flag, runtime gate, or route controller.
Current-state orientation only
- Controls
- Phase 11.15 - Individual Mode Current-State Index
- Map status
- descriptive-only
- Implementation effect
- Does not act as an executable policy registry, permission system, feature flag, runtime gate, or route controller.
Current Implementation-State Summary
Accounts and identity
Status: absent-or-inactive
- no Individual Mode account
- no subscriber account
- no login
- no signup
- no identity capture
- no account storage
- no actor storage
- no role assignment
- no permissions or RBAC runtime
- no sessions, cookies, JWTs, tokens, or raw identity-header reads
blocks-runtime
Private data and consent
Status: absent-or-inactive
- no consent capture
- no consent record
- no private recovery data record
- no check-in record
- no reflection record
- no relapse-prevention plan record
- no craving/trigger record
- no values/routine record
- no support-contact record
- no transcript record
- no memory record
- no crisis/escalation record
blocks-runtime
Runtime
Status: absent-or-inactive
- no recovery coach runtime
- no reflection/check-in runtime
- no chat runtime
- no AI runtime
- no OpenAI processing for direct-subscriber content
- no prompt endpoint
- no chat endpoint
- no streaming endpoint
- no model invocation
- no prompt/completion storage
- no memory/embedding/retrieval runtime
- no crisis detection
- no hotline lookup
- no local emergency content
- no triage, dispatch, emergency routing, or risk scoring
blocks-runtime
Commercial and support
Status: absent-or-inactive
- no billing
- no checkout
- no Stripe/payment provider
- no subscription runtime
- no trial signup
- no refund/cancellation workflow
- no customer portal
- no lead capture
- no CRM
- no marketing automation
- no support runtime
- no support ticket
- no support inbox
- no customer record
- no support record
- no account access or impersonation
- no deletion/export workflow
- no abuse/incident workflow
- no rollback execution
blocks-runtime
Technical
Status: absent-or-inactive
- no protected live routes under src/pages/protected
- no protected APIs under src/pages/api/protected
- no database reads/writes for Individual Mode
- no D1 query
- no runtime table
- no storage adapter
- no API handler
- no new active migration
- active migrations remain only migrations/0001_packet_history.sql
blocks-runtime
Authorization and Evidence Status
Future evidence requirements may be indexed, but they remain outside-app requirements only. This page creates no evidence repository, upload, review record, signoff record, approval record, readiness record, implementation record, gate closure, or launch authorization.
Future Outside-App Evidence Requirements
- written privacy/legal review
- explicit consent model
- data minimization model
- retention/deletion/export policy
- crisis escalation safety copy and resource policy
- human-support boundary review
- non-clinical language review
- AI red-team and hallucination review if AI is ever considered
- memory/user-control policy if memory is ever considered
- account/identity architecture review
- support confidentiality and access-control policy
- billing/refund/cancellation policy if commercial runtime is ever considered
- rollback/incident response plan
- accessibility/localization review
- source and content governance review
- security review
- deployment/kill-switch review
Cross-Mode Separation
- Individual Mode private data is hidden from Organization Mode by default.
- Organization Mode cannot inspect direct-subscriber check-ins, reflections, relapse plans, memories, prompts, completions, transcripts, support contacts, or crisis/support information.
- No staff dashboard, tenant admin, organization owner, support admin, review queue, analytics surface, or cross-mode bridge exists.
- Future sharing would require separate explicit consent plus privacy, legal, product, security, and technical review.
- No current cross-mode sharing exists.
Non-Clinical and Anti-Surveillance Boundary
Current-State Index Limitations
- This index is not a source of authoritative runtime state.
- It is not a compliance record.
- It is not a launch checklist completion record.
- It is not an approval registry.
- It is not a feature flag registry.
- It is not an admin console.
- It is not an evidence repository.
- It is not a workflow controller.
- It is not an account/status database.
- It does not become stale-safe merely because it renders.
- Any future runtime state would require a separately reviewed architecture and implementation phase.
Stop Conditions
- Stop if someone asks to store current-state or readiness records.
- Stop if someone asks to persist gate status.
- Stop if someone asks to add evidence upload, review records, signoff records, approval records, or readiness records.
- Stop if someone asks to mark a gate passed or closed.
- Stop if someone asks to authorize launch or implementation.
- Stop if someone asks to create accounts, login, signup, identity capture, storage, billing, support, AI/chat, memory, crisis handling, protected APIs, protected live routes, database behavior, or migrations.
- Stop if someone asks to add forms, inputs, buttons, toggles, controls, downloads, exports, generated PDFs, or generated ZIPs.
- Stop if someone asks to expose Individual Mode private data to Organization Mode.
- Stop if someone asks to add scoring, analytics, tracking, ranking, compliance, or clinical claims.
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.