# Theo AI · Platform Overview

> Theo AI is the Context OS for AI Workers. A memory protocol (MCIR 2.0), a trust layer, a visual build layer (E.V.I. Canvas), a model-routing engine room, and every channel your customers use, all governed by one audit trail and bound by one privacy contract.

Source of truth: https://hitheo.ai. Last updated: 2026-05-24.

## At a glance
- Memory protocol: MCIR 2.0 — a typed, exportable, audit-grade memory graph that runs in front of every response.
- Trust layer: SHA-256 hashed audit ledger, org-scoped knowledge storage, destructive delete, open-source SDK.
- Build layer: visual canvas for assembling AI Workers with skills, knowledge nodes, hooks, and workflows.
- Routing layer: visual rules engine that decides which engine answers which prompt, with a live test bench.
- Channels: REST, dashboard playground, voice sessions, embeddable iframes, and open-source channel adapters.
- Monetization: orchestration (per-token) and platform (skills, workflows, channels). We never monetize training.

## Positioning pillars
1. Memory is the differentiator. Models converge; the memory of your customer, account, workflows, and open promises does not. Theo owns that layer.
2. Models are commodities. The routing engine treats the model fleet as interchangeable and selects per request based on intent, skill bindings, and your routing rules.
3. Trust is engineered, not asserted. Every privacy claim maps to a real code path. Audit hashes prompts. Knowledge files are org-scoped. Memory is exportable and deletable.
4. The platform is composable. Skills + knowledge + workflows + hooks combine into AI Workers that an operator can assemble visually.

## What Theo runs
- A memory protocol (MCIR 2.0) with four typed layers (episodic, semantic, procedural, memory chain) and eight protocol stages (Capture → Audit). See https://hitheo.ai/llms/memory.txt.
- An intelligent routing engine that classifies intent on every promotable request and dispatches to the right engine. See https://hitheo.ai/llms/routing.txt.
- A skill marketplace with installable, manifest-described bundles of prompts, knowledge, and tools. See https://hitheo.ai/llms/skills.txt.
- A visual canvas (E.V.I.) for assembling AI Workers without code. See https://hitheo.ai/llms/studio.txt.
- Image generation (multi-engine), video generation (with AI-disclosure watermark), document generation (PDF / DOCX / XLSX / PPTX / CSV), code generation, deep research, and a managed live-view browser. See the matching capability files under https://hitheo.ai/llms/.
- A REST API, an open-source SDK, channel adapters for chat platforms, a Model Context Protocol adapter, and embeddable chat widgets.

## Memory Packs (vertical AI Worker bundles)
Pre-built skill bundles tuned to specific industries: insurance, med-spa, B2B SaaS support, SaaS onboarding, legal intake, real-estate, healthcare front-desk, recruiting and staffing. See https://hitheo.ai/llms/packs.txt.

## Privacy contract (the four promises)
1. We never train on your prompts.
2. We never train on your knowledge files.
3. We never train on your memory graph.
4. We never sell your usage patterns.

See https://hitheo.ai/llms/privacy.txt for how each promise maps to a code path.

## Related machine-readable files
- https://hitheo.ai/llms.txt — full index of every Theo machine-readable file.
- https://hitheo.ai/llms-full.txt — long-form knowledge bundle (single fetch).
- https://hitheo.ai/humans.txt — team and open-source credits.
- https://hitheo.ai/lawyers.txt — trademark notice and legal contact.
- https://hitheo.ai/.well-known/security.txt — security disclosure contact.