AI dashboard/public/operator-data-architecture.html · grounded in the running silo implementationEvery customer gets one isolated directory on the operator host. Claude runs with its working directory locked to that folder (claude -p, cwd-pinned) — it physically starts inside your space and reads nothing outside it. No shared database, no commingled tables.
Everything the operator remembers is written as human-readable markdown files — todos, notes, decisions, people. No vector store, no opaque blob. The customer can open, edit, or delete any memory with a text editor.
no black boxA per-customer CLAUDE.md holds the operator's persona, standing instructions, language, boundaries, and shortcuts ("add todo" → edit todos.md). It is loaded automatically at the start of every single conversation — this is why the operator never forgets who it works for.
context/about-me.md — filled by the guided onboarding interview (/onboard): who you are, family, goals, preferences. Read on demand when a task needs personal context.
| Ability | Data it creates | Where it lives |
|---|---|---|
| 💬 Chat & memory (base) | Conversation audit, chat mirror, remembered facts | logs/*.jsonl, telegram-mirror.md, markdown memory files |
| ✅ Todos & notes (base) | Todo checkboxes, freeform notes | inbox/todos.md, inbox/*.md |
| 🤝 Contact memory | People, context, follow-up threads | contacts.md in the space (+ customer's own Google Contacts if connected) |
| 🌅 Morning brief / 📬 Mail digest | Nothing new — reads calendar/mail, writes only the message to you | transient; source data stays in the customer's Google account |
| 📅 Calendar concierge / ✉️ Email | Events and mail live in the customer's own Google account | customer's Google — reached via their own isolated credentials, never copied wholesale |
| 📡 Market scanner | Watchlist + seen-items list (dedupe) | inbox/watchlists.md + seen-log in the space |
| 🌙 Content factory | Drafts produced overnight | drafts/ in the space |
| 🎨 Visuals / 📎 files in chat | Generated images, received photos and documents | files/ in the space |
| 🏡 Family & household | Shared lists, home baseline values | markdown in the space (family members' locations are read live, never logged) |
claude -p launches with cwd locked to your folder. Handbook (CLAUDE.md) loads automatically. Tools are gated to your tier.Bot tokens and API keys live in .env.local.enc — encrypted with SOPS + age. Decrypted into process memory only for the seconds a task runs. Never plaintext on disk, never in git, never in logs (provisioning scrubs tokens from output by design).
Calendar/mail abilities use a per-customer credential directory (.config/gws/) — the customer signs into their own Google account. No shared service account, no operator-wide Google access. Revoke in your Google settings and the ability dies instantly.
Any token can be rotated at runtime without touching history. An emergency stop disables the listener, logs the bot out, and renames the secrets file so nothing can auto-restart until a human turns it back on.
rotate / killBecause everything is files, "export my data" is literally an archive of your space — readable the moment it lands. No proprietary format to escape from.
portabilityCancellation keeps your export link alive 30 days, then the space is destroyed. One folder to delete means deletion is verifiable, not a promise scattered across databases.
right to be forgottenData is processed under commercial API terms — not used to train models. There is also no cross-customer anything: no shared index, no "insights from users like you".
no trainingThe append-only JSONL audit plus the readable chat mirror mean a customer (or their admin) can always answer "what did my operator do, and when" — line by line.
accountabilitySpaces live on the operator-managed host in Sweden (EU rules), one directory per customer, chat/creds/logs excluded from any code repository by ignore rules. Tailscale-style private networking for any admin surfaces — nothing customer-facing is publicly exposed.
current implementationPer-customer encrypted volumes on EU cloud, so a host failure or move never touches plaintext. Same folder model, same export/delete story — just replicated and rebootable.
plannedFor customers who want physical custody: the space syncs to their Drive/NAS as the canonical copy. Pairs with "Bring your own AI" (sign in with your own model provider) for a fully customer-owned stack.
planned · pairs with BYO-AI