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 throne.
Agents are your vassals.
Zeus is an operating system that takes one folder as its data seat of power. It connects MCP tools, grows Skills, and lets agents delegate to one another over A2A — while you remain the driver who steers, reviews and decides. Your data leaves only on your order.
personal realmenterprise realmvassal onlinedirectory = database
THE THREE TENETS
Every capability enters through one of three doors.
No feature is a one-off. Anything Zeus integrates must collapse to MCP, Skill, or A2A — the only postures the constitution 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 vassal product exposes an Agent Card. Zeus dispatches tasks, streams reports back, and escalates to you the moment a human call 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 — poetry and engineering are the same map.
05
NARRATIVE
Chronicle · Mentor · Harbor · Inheritance
Emotional value and belonging, not slogans — every story points to a recovery action.
04
COLLABORATE
Team · A2A delegation · Oversight deck
A small society of agents, with you as the driver. Approve, reject, redirect.
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 · Vassal products
pr-helper, loom, atlas — each keeps its own repo and deploy, reports back as war dispatches.
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 sovereignty.
Personal and enterprise realms share every layer. The only thing that changes is who holds the keys and who may audit.
A harbor for memory
One sovereign. Your memories, your diary, your treasure map — encrypted, backed up, and inheritable under conditions you set.
- Single-owner directory
- Diary as narrative backup
- A map you can pass on
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
THE TREASURE MAP
The map is the recovery protocol.
Zeus never stores your treasure in the cloud. It stores an encrypted manifest plus the route to your vault — so you hold the map, and Zeus only holds a backup of the map.
142 OBJECTS·1204 EVENTS·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.
- First vassal: pr-helper, now in acceptance
- Realm read / write / retrieve interface spec
- A2A agent-card + task dispatch draft
- Bilingual (en / zh) on day one