Our AI operating system
In daily useThe system our company runs on every day. Anything we install for a client runs here first.
12 agents
each with least-privilege permissions, plus 47 skills
What I built
The Bridge
One dashboard over the whole company: a 3D map of every note, both calendars, both inboxes, messages and meetings, and a chat over the knowledge base that can read but never send.
Specialist agents
Agents on least-privilege tool lists: reviewers that read like a dentist or an optometrist, research, meeting notes. Reusable skills cover proposals, QA, deploys and reporting.
Jobs that run themselves
A daily meeting sweep writes the notes, updates the week's priorities, logs decisions and texts the action items. A weekly health check keeps the knowledge base clean, and every run leaves a log.
Engineering
Files over a database: every agent and person can read them, all in git.
- How it fits together
- A markdown vault as the database; agents and skills as files with allow-lists.
- Tested
- Tested guard scripts and a weekly vault lint.
- Claude Code
- Claude Code headless
- MCP
- Python
- Three.js
My role. I built all of it.