Technical Investor Briefing

SL8 Architecture
Blueprint

Visualizing the complete lifecycle of an interaction in an ADHD-friendly, offline-first productivity platform built around an infinite canvas.

10-Stage System Funnel

flowchart TD %% Styling Configuration classDef default fill:#1e293b,stroke:#475569,stroke-width:1px,color:#f8fafc,font-family:Inter; classDef highlight fill:#0ea5e9,stroke:#0284c7,stroke-width:2px,color:#ffffff,font-weight:bold; classDef offline fill:#b45309,stroke:#92400e,stroke-width:2px,color:#ffffff; classDef fail fill:#9f1239,stroke:#881337,stroke-width:2px,color:#ffffff; classDef db fill:#0f172a,stroke:#38bdf8,stroke-width:2px,stroke-dasharray: 5 5; %% Stage 1: Input S1Input["1. User Input (Text, Voice, Canvas)"]:::highlight --> S2Capture["Input Capture"] %% Stage 2: Local Workspace subgraph Stage2 ["2. Local Workspace & Persistence"] S2Capture --> S2LocalDB[("IndexedDB (Local State)")]:::db S2Capture --> S2ConnCheck{"Connectivity"} S2ConnCheck -->|"Online"| S3Intent["3. Intent Classification"] S2ConnCheck -->|"Offline"| S2Queue["Local Sync Queue"]:::offline S2LocalDB -.-> S2Queue end %% Stage 3: Intent & Context subgraph Stage3 ["3. Intent & Context Resolution"] S3Intent --> S3Context["Context Retrieval"] end %% Stage 4: Orchestration subgraph Stage4 ["4. Orchestration Engine"] S3Context --> S4Router["Request Routing"] S4Router --> S4Select["Model & Tool Selection"] S4Select --> S4Perms["Permission & Limits Check"] end %% Stage 5: Knowledge & Connectors subgraph Stage5 ["5. Knowledge & Connectors"] S5KB[("SL8 Knowledge DB")]:::db S5ExtAI["External AI Providers"] S5Gateway["3rd-Party API Gateway"] end S4Perms <--> S5KB S4Perms -.-> S5Gateway %% Stage 6: AI Execution subgraph Stage6 ["6. AI Execution"] S4Perms --> S6Exec["Model Inference & Tools"] S6Exec <--> S5ExtAI S6Exec -.-> S5Gateway S6Exec --> S6Check{"Provider OK?"} S6Check -->|"Unavailable"| S6Fail["Preserve in Retry Queue"]:::fail S6Fail -.-> S2Queue end %% Stage 7: Validation subgraph Stage7 ["7. Response Validation"] S6Check -->|"Available"| S7Validate["Validate Tool Results"] S7Validate --> S7Confirm["Action Permission Control"] end %% Stage 8: Delivery subgraph Stage8 ["8. Response Delivery"] S7Confirm --> S8UI["UI Stream (Chat/Canvas)"]:::highlight end %% Stage 9: Memory Updates subgraph Stage9 ["9. Memory & Workspace Updates"] S8UI --> S9Update["Save: Raw, Derived, Actions"] S9Update --> S5KB end %% Stage 10: Cloud Sync subgraph Stage10 ["10. Cloud Sync & Recovery"] S2Queue -.-> S10SyncEngine["Sync Engine (Idempotent)"] S10SyncEngine <--> S10Cloud[("Cloud Backend")]:::db S10SyncEngine --> S10Conflict["Conflict Resolution (CRDT)"] end

Core Product Promise

Capture everything. Organize automatically. Think with your own AI.

Frictionless Capture

Users drop thoughts into the system without deciding where they belong. The interface removes the cognitive load of categorization, crucial for ADHD-friendly design.

Automated Organization

SL8 progressively connects related information, surfaces context, and automates mundane tasks in the background without rigid schemas.

Personal Intelligence

Your AI contextualizes your unique knowledge base. It is a thinking partner that acts on your behalf across connected applications safely.

The Offline-First Principle

Capture never waits. Core functionality relies on local IndexedDB storage. Network drops route operations to a robust pending queue. The canvas remains fluid and editable offline. Cloud sync resumes idempotently when connectivity returns, utilizing CRDTs to prevent destructive conflicts.

Decoupled AI & Privacy

SL8 separates the persistent knowledge layer from the LLM provider. Bring your own API key or use supported OAuth integrations. The system maintains its own strict memory typology (Raw vs. Derived), ensuring AI hallucinations never silently overwrite your ground truth.

Modular Connector API

An n8n-inspired background engine integrates Teams, Slack, Notion, and Jira. Actions undergo strict permission controls inside the Orchestration Engine. Consequential mutations require user approval, while background webhooks continuously ingest relevant context seamlessly.