START HERE — the whole platform in one page.
Tu Empresa Digital OS
Tu Empresa Digital OS (TED OS) is a per-client operations brain: collect each client's data, accrete their memory from day one, and run AI tasks over it — then reuse the same core for the next client so each delivery is cheaper than the last. "Service outside, product inside."
This site documents the whole platform — its apps, its packages, its data architecture, and
the workflow (claude-kit) that builds it. Everything here describes what the system IS today,
derived from the canonical reference docs in the repo's knowledge/ directory.
This site is access-gated (Clerk). It documents internal architecture in full — including decisions, auth, and deploy topology. No page ever contains real secrets, tokens, keys, or env values — environment variables are referenced by name only.
The shape of the system
| Layer | What it is | Read |
|---|---|---|
| Platform apps | The operator admin, the superadmin console, white-label client instances, and the API behind them | Platform apps |
| Architecture | The Plan Engine graph (dev-workflow SoT), the product System of Record, per-client data & memory, and the last-mile engine | Architecture |
| Auth & deploy | Clerk authentication across subdomains, and the Vercel + Fly deploy topology | Auth & deploy |
| Design system | The neutral foundation, per-surface skins, and the Grid System v2 | Design system |
| Build & workflow | The effort model and the kit ↔ engine boundary | Build & workflow |
| claude-kit | The AI dev team — agents, skills, rules, and a workflow inside Claude Code — that builds TED OS | claude-kit |
Two databases that never mix
A foundational rule runs through the whole platform: the dev-workflow data and the client/product data live in separate databases and never share tables.
- The Plan Engine graph (
planschema) is the source of truth for our plans and tasks. It doubles as a training-trace corpus for a future builder model. - The product System of Record (
productschema) holds clients' data, isolated per client.
Tenant data never enters the dev-workflow corpus. See Plan Engine and Product System of Record.
The first client
Comprender (an education provider) is tenant #1 — the case study that drove the product System of Record, per-client isolation, and the white-label client app pattern. See Comprender.
How to read these docs
- This Overview for the shape of the system.
- Architecture for how it is built.
- Platform apps for what each surface does.
- Decisions (ADRs) when you need why a thing is the way it is.
The repo's knowledge/ directory is the upstream source of truth; these pages link and derive
from it rather than duplicating it.