MCP — plug into the world
Any system that speaks MCP becomes a data and tool source. Enterprise side: auditable, revocable, never a black box.
v0.1 · early access
Your directory is the foundation.
Agents are yours to direct.
Zeus is an operating system that takes one folder as its data foundation. It connects MCP tools, grows Skills, and lets agents delegate to one another over A2A — while you remain the operator who directs, reviews and decides. Your data leaves only on your confirmation.
personal realmenterprise realmagent onlinedirectory = database
THREE ACCESS PRIMITIVES
Every capability enters through one of three channels.
No feature is a one-off. Anything Zeus integrates must collapse to MCP, Skill, or A2A — the only channels the architecture permits.
Skill — teachable, hardenable
Skill packages declare inputs, permissions and dependencies. A mentor agent can pass them to a new hire or a new agent.
A2A — agents govern agents
Every execution-agent product exposes an Agent Card. Zeus dispatches tasks, streams task artifacts back, and escalates to you the moment a human decision is needed.
THE STACK
Five layers, one seam.
Narrative on top, data on the bottom. Every layer above is backed by a real, executable primitive below — narrative and engineering are the same design.
05
NARRATIVE
Recovery protocol · Diary · Mentor · Secure carrier · Inheritance
Emotional value and belonging, not slogans — every story points to a recovery action.
04
COLLABORATE
Organization v1 · A2A delegation · Oversight deck
Departments, positions and task dispatch with graded D0–D3 approvals. You operate; agents execute.
03
GROW
Skill packs · Mentor onboarding · Agent registry
Recruit, train, harden. Capability becomes an asset, not a one-off prompt.
02
CONNECT
MCP connectors · External agents · Execution-agent products
pr-helper, loom, atlas — each keeps its own repo and deploy, reports back with task artifacts.
01
DATA
Realm directory · Vault · Map manifest · Backups
You point at a folder. That folder is the database. Backups are a first-class citizen.
ONE ENGINE, TWO REGIMES
Same primitives. Different governance.
Personal and enterprise realms share every layer. The only thing that changes is who holds the keys and who may audit.
Your personal agent, anchored in memory
This realm is your personal agent. Single owner — your memories, your diary, your recovery protocol — encrypted, backed up, and inheritable under conditions you set.
- Single-owner directory
- Diary as narrative backup
- A recovery protocol you can pass on
- Claude Desktop / Cursor can attach read-only over stdio MCP in one step
A virtual department
Multi-tenant, org-aware. A mentor agent briefs the new hire on day one; employees supervise agents, never hand-execute.
- Onboard on day one
- Knowledge survives turnover
- Audit-ready, data stays in the domain
RECOVERY PROTOCOL
The recovery protocol is the backup-and-restore contract.
Zeus never stores your data in the cloud. It stores an encrypted manifest plus the route to your backup carrier — so you hold the manifest, and Zeus only holds a backup of it.
AES-256-GCM·SCRYPT N=131072·SEALED · KEY NEVER LEAVES YOU
- 01
Manifest, not data: an encrypted list of what you own, where it lives, and how to restore it.
- 02
Diary as backup: memory written in story, replayable as events.
- 03
The data diode: personal realm and enterprise realm never leak into each other without explicit authorization.
- 04
Inheritance: a recovery protocol with conditions and keys — designed from day one, shipped later.
Early access
Bring your directory.
No migration, no lock-in. Point Zeus at a folder and the OS stands it up. Take the folder away and Zeus is replaceable — that is the point.
- Decision API v1 — graded D0–D3 approvals, SLA timeouts, idempotent replay
- Organization API v1 — departments, positions, task dispatch
- Per-record signed JSONL audit chain — tamper-evident, replayable
- Typed zeus-client SDK — zero-dependency TypeScript integration