architecture · supabase_json
Limitless OS Architecture
architecture artifact · for Limitless OS · status draft
Agent Handoff
Start Here
architecture artifact · for Limitless OS · status draft
Completion Evidence
No explicit evidence field yet. Require tests, screenshots, linked PRs, or reviewed outputs before marking complete.
Artifact Shape
- title: Limitless OS Architecture
- layers: 6 items
- source: atlas-codex
- client id: limitless
- project id: 07dee66f-8143-4f4d-9af9-b1ed413d2767
- updated at: 2026-05-09T19:02:57.675Z
- data classes: 4 items
- project name: Limitless OS
- artifact type: architecture
- schema version: 1
- source documents: 2 items
- integration strategy: 4 items
Structured Payload
Machine-readable source fields
title
Limitless OS Architecture
layers
| layer | systems | responsibility |
|---|---|---|
| operational_backbone | - PT Everywhere - GoHighLevel / CM Hub - email - social platforms - Stripe/payment links - QuickBooks - Availity/payer tools | Systems of record and task source inputs. |
| hcs_pull_queue | - HCS role topics - claim events - completion events - review gate topics | Canonical agent work routing and audit pointer layer. |
| read_model_and_memory | - Supabase current state - agent memory - artifact store - approval ledger | Dashboards, current task state, artifact bodies, sensitive data access controls. |
| agent_team | - front-office agents - growth agents - clinical authority agents - patient performance agents | Draft, classify, summarize, prioritize, recommend, and route work. |
| human_review_and_action | - Seth review - Betsy/front-office review - clinician review - staff review | Approval and execution for sensitive communication and business decisions. |
| user_experience | - owner command center - front-office workbench - patient/performance command center - parent/athlete summaries | Human-facing views that hide queue complexity. |
source
atlas-codex
client id
limitless
project id
07dee66f-8143-4f4d-9af9-b1ed413d2767
updated at
2026-05-09T19:02:57.675Z
data classes
| class | examples | hcs allowed |
|---|---|---|
| public_or_marketing | - content drafts - campaign plans - public education copy | structured pointer and non-sensitive summary allowed |
| business_sensitive | - KPIs - collections summaries - staff notes | pointer/status only |
| patient_sensitive | - clinical notes - lead health concerns - payer details - exercise adherence | pointer/status only; protected store required |
| staff_sensitive | - performance concerns - corrective feedback | pointer/status only; Seth-only review |
project name
Limitless OS
artifact type
architecture
schema version
1
source documents
| path | role | pages | title |
|---|---|---|---|
| /Users/justinking/Downloads/Limitless_OS_Final_Vision_Document.pdf | Patient/performance operating system vision | 19 | Limitless OS Final Vision & Goals/Intent Document |
| /Users/justinking/Downloads/Limitless Ai Agent Goals Intent Blueprint.pdf | Front-office and business-support agent blueprint | 40 | Limitless Physical Therapy & Performance AI Agent Goals & Intent Blueprint |
integration strategy
- Start with extract/summarize/draft workflows around existing tools before deep write integrations.
- Use source refs instead of copying sensitive bodies into HCS.
- Prefer low-friction ingestion: voice transcripts, exported reports, webhook payloads, inbox summaries, CRM lead records.
- Add direct API integrations only after workflow value and review gates are proven.
architectural position
Limitless OS is an intelligence, coordination, engagement, and performance layer above PT Everywhere and other operating systems, not a replacement EMR or billing platform.
first technical unknowns
- PT Everywhere API/export access
- GoHighLevel/CM Hub API access
- email and SMS sending boundary
- VALD/ForceDecks export format
- HIPAA posture for chosen storage and messaging tools
- who approves each gate in daily operations