Vision
Cloud holds truth. Disk is a mirror.
Traditional version control optimizes for async work: branches, commits, pull requests. That model fights realtime work, and it treats the filesystem as truth until you push.
What if your codebase lived in a cloud Sync Store and mirrored to your machine the way Drive mirrors documents?
Not another IDE. Not another git host. Storage, sync, work, and collaboration — one model. Files feel local and stay globally live.
Four layers
Storage
Files are rows. Versions are append-only history — not server paths or git objects.
Sync
Live WebSocket push — not commit / push / pull.
Work
Mirror at $HOME/Projects. Personal project at the top level; org project under the org folder. Any editor, any terminal.
Collaboration
Solo sync, async fork + Pierre merge, live pair later via Collab agent.
Success looks like
Storage and sync
- Open $HOME/Projects/my-app/src/index.ts, save, and every other logged-in machine sees it in seconds.
- Binaries sit in the same file/version model. No separate blob service.
- A new teammate logs in, gets a role, and projects appear on disk — no clone, no fetch, no checkout.
Work
- Zed on the laptop, VS Code on the desktop — same project, same mirror, zero git in the loop.
- Org owner creates roles, assigns members, and keeps ownership when someone is fired.
Collaboration
- Two people edit without pairing. Both versions exist. Pierre Merge is a line-pick, not a guess.
- Live pair (later): Neovim and VS Code, no browser, no Kitchen plugins. Voice stays on Discord. Checkpoint inserts one version.
The model in practice
Mission is how we know someone actually understands it.