🧩 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.
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.
daily recovery structure
Positioning hypothesis only; not a customer deployment claim.
source-backed orientation
Positioning hypothesis only; not a customer deployment claim.
accountability without surveillance
Positioning hypothesis only; not a customer deployment claim.
staff-reviewed community workflows
Positioning hypothesis only; not a customer deployment claim.
privacy-first recovery operations
Positioning hypothesis only; not a customer deployment claim.
no attendance or participation tracking
Positioning hypothesis only; not a customer deployment claim.
no participation analytics
Positioning hypothesis only; not a customer deployment claim.
no scoring/ranking/compliance metrics
Positioning hypothesis only; not a customer deployment claim.
Who It Could Serve
Platform Modules
These modules describe the Renata product direction. Only live-static modules are active in the field-lab instance; protected and planning modules remain read-only previews.
Live-static modules
Field-lab proof points that render from public/source-backed or synthetic packet data today.
- Daily Recovery Packet: Gives a morning meeting a structured, source-backed orientation layer for the day. Boundary: Uses public/source-backed packet data only and does not include community submissions or customer data.
- Presenter Script: Turns packet content into a calm room-ready script for consistent facilitation. Boundary: Read-only script generated from packet data; no feedback, notes, or resident content is collected.
- Operator Diagnostics: Shows packet health, source warnings, section counts, and budget status for staff review. Boundary: Read-only diagnostics for generated packet data only.
Protected-preview modules
Protected planning surfaces that model future workflow boundaries without collecting data.
- Community Accountability Workflow: Frames future pull-up and push-up workflows around repair, recognition, and accountability without surveillance. Boundary: Protected synthetic preview only; no live drafts, submissions, or resident records.
- Staff Review Queue: Shows how staff review could prevent shaming, private disclosure, or unsafe public reading. Boundary: Synthetic queue only; no approvals, rejections, staff notes, or decisions are created.
Synthetic-only modules
Static previews that show future presentation shapes without live participation.
- Morning Sheet: Models a print-friendly meeting sheet for roles, prompts, acknowledgments, and meeting flow. Boundary: Synthetic layout only; no live role signups, resident names, or community content.
Planning-only modules
Readiness, privacy, retention, schema, and demo planning surfaces.
- Privacy & Retention Planning: Makes privacy, deletion, audit, visibility, export, and AI-use decisions explicit before launch. Boundary: Read-only planning metadata; no approvals or data collection.
- Readiness Matrix: Summarizes what is preview-complete, synthetic, blocked, or decision-bound before launch. Boundary: Planning-only matrix; no launch control exists.
- Data Schema Planning: Documents possible future data domains, relationships, audit events, and excluded sensitive fields. Boundary: No active migrations, runtime tables, write endpoints, or customer data storage.
- Staff Demo Walkthrough: Gives staff and privacy reviewers a clear route through the field-lab proof point and protected planning stack. Boundary: Presentation guide only; no decisions, records, forms, lead capture, or workflow activation.
Blocked-before-live modules
Capabilities that cannot launch until account, privacy, retention, review, audit, and legal gates are approved.
No module in this status is active in the current field-lab layer.
What Is Live Today
The Sixth Sense at 6th Street currently proves the live-static morning-meeting layer: packet generation, presenter script, and operator diagnostics. These use generated packet data, not resident submissions or customer records.
Daily Recovery Packet
Gives a morning meeting a structured, source-backed orientation layer for the day.
Uses public/source-backed packet data only and does not include community submissions or customer data.
live-staticPresenter Script
Turns packet content into a calm room-ready script for consistent facilitation.
Read-only script generated from packet data; no feedback, notes, or resident content is collected.
live-staticOperator Diagnostics
Shows packet health, source warnings, section counts, and budget status for staff review.
Read-only diagnostics for generated packet data only.
live-staticWhat Is Still Protected or Planning-Only
Community accountability, staff review, privacy, retention, readiness, and schema surfaces remain protected, synthetic, or planning-only. They are not live workflows and do not collect community content.
Commercial Readiness
- legal, privacy, and compliance review before customer deployment
- clinical claims review before any outcome language
- account, role, retention, audit, and deletion policies
- customer-specific source strategy and operating boundaries
- pilot plan, rollback plan, and support model
prototype / field validation. not ready for live customer data. requires legal/privacy/compliance review before customer deployment. requires clinical claims review before outcome claims.
Product Boundaries
Renata is not medical advice, not diagnosis, not emergency care, and not a clinical outcome guarantee. It makes no HIPAA, 42 CFR Part 2, FDA, clinical, or compliance claims until legal/privacy review.