Renata - Recovery Operating System Preview

What Renata Is

Renata is the broader product direction: a recovery operating system for structured daily orientation, source-backed recovery intelligence, staff-reviewed workflows, and privacy-first operations. It is a field-validation prototype, not a commercial deployment, clinical product, or live customer-data system.

Phase 11.0 separates the product architecture into Public Packet Mode, future Organization Mode, and future Individual Mode. The operating-modes layer is protected-preview, read-only, and planning-only.

Phase 11.1 adds a protected-preview Individual Mode safety model before any direct-subscriber account, subscription, chat, recovery coach runtime, AI runtime, crisis flow, billing, protected API, protected live route, database behavior, or sensitive storage planning continues.

Phase 11.2 adds a protected-preview Organization Mode tenant and role model before any B2B tenant, account, role assignment, staff workflow, resident workflow, billing, CRM, protected API, protected live route, database behavior, or storage planning continues.

Phase 11.3 adds a protected-preview Account Activation Plan before any future account, login, registration, identity capture, account storage, protected API, protected live route, billing, CRM, database behavior, or workflow runtime planning continues.

Phase 11.4 adds a protected-preview Pull-Up / Push-Up MVP Workflow Plan before any future draft collection, review queue, staff decision, approval recording, Morning Sheet placement, protected API, protected live route, database behavior, or workflow runtime continues.

Phase 11.6 adds a protected-preview Individual Mode Private Data and Consent Model before any future account, consent capture, private storage, chat runtime, AI runtime, recovery coach runtime, billing, crisis runtime, protected API, protected live route, database behavior, or Individual Mode workflow continues.

Phase 11.7 adds a protected-preview Individual Mode Reflection and Check-In UX Plan before any future reflection capture, check-in capture, consent capture, private storage, chat runtime, AI runtime, recovery coach runtime, billing, crisis runtime, protected API, protected live route, database behavior, or Individual Mode workflow continues.

Phase 11.8 adds a protected-preview Individual Mode Crisis and Human Support Boundary Plan before any future crisis detection, hotline lookup, local emergency content, emergency routing, triage, dispatch, risk scoring, chat runtime, AI runtime, storage, protected API, protected live route, account, billing, or runtime work continues.

Phase 11.9 adds a protected-preview Individual Mode AI Prompt and Evaluation Boundary Plan before any future prompt endpoint, chat endpoint, streaming endpoint, OpenAI direct-subscriber processing, prompt/completion storage, transcript storage, memory storage, risk scoring, crisis AI handling, account, billing, protected API, protected live route, database behavior, or runtime work continues.

Phase 11.10 adds a protected-preview Individual Mode Memory and Continuity Boundary Plan before any future memory runtime, hidden memory, preference storage, transcript storage, embedding/vector retrieval, OpenAI processing, chat runtime, account, billing, protected API, protected live route, database behavior, or runtime work continues.

Phase 11.11 through Phase 11.12 document commercial, support, and account-operations boundaries without billing, customer, support, account, storage, API, AI, crisis, or workflow runtime. Phases 11.13 through 11.16 preserve the launch-gate, non-authorization, current-state, and documentation-only closure posture. Phase 11.17 freezes only the canonical handoff order and no-go language for outside-app review; it creates no handoff, reviewer, evidence, signoff, approval, readiness, or implementation record. Individual Mode Phase 11 handoff is frozen with no product implementation phase authorized. OM-001 remains a parallel Organization Mode planning surface and does not change this posture.

Phase 12.0-12.12 provide synthetic, non-interactive Individual Mode surfaces and review aids culminating in a Static Closure Note and Handoff Freeze for outside-app review only. Phase 11 remains controlling, and no handoff, closure, status, review, evidence, approval, readiness, gate, launch or implementation authorization, Phase 13 authority, account, consent, private data, support, AI/chat, memory, crisis, billing, protected API, database, or runtime state exists.

Why Renata

Renata means rebirth. The name fits a platform direction centered on daily renewal, recovery structure, and accountable community support without surveillance or clinical overclaiming.

Current Field-Lab Instance: The Sixth Sense at 6th Street

Name: The Sixth Sense
Full name: The Sixth Sense at 6th Street
Community: 6th Street
Type: field-lab instance
Role: first Renata implementation / morning-meeting intelligence module
Purpose: source-backed morning meeting and protected workflow planning

Platform Vision

Renata is positioned as a Recovery Operating System at the field-validation prototype stage. The Sixth Sense at 6th Street is the first field-lab implementation, focused on the morning-meeting intelligence module.