How it fits together
You talk to the system through a few doors. Behind the doors is one small server. Behind the server are two stores: plain files for what is true, and a database for what is happening now.
You, the owneron a phone or a laptop
The box one small server
The outside worldemail, websites, the people you work with
InQuarantinemail_quarantine.pyOutside email reaches agents as a checked summary.OutSend guardsend-guard.pyMessages agents send are checked, or held for your yes.The vaultPlain text files in gitWhat is true and how things are done: agent contracts, skills, memory, the routines list, the box code.The logbookOne database on the boxWhat is happening right now: questions, inboxes, plans, settings, spending, history.
Read the map top to bottom
- You open the Office on your phone, or answer a question from a link.
- The doors are the ways in: the Office, chat, tap-to-approve links, and messages by email, Discord, or WhatsApp. They all reach the same brain.
- The box is the server. Its web server draws every screen. Its alarm clock wakes agents. Its timers run routines. A checker watches that routines ran and flags any whose result it cannot verify.
- Two gates stand between the box and the outside world. Email comes in through the quarantine. Messages an agent sends go through the send guard. The known limits page says where these gates stop.
- The two stores hold everything. The vault holds what is true and how things are done. The logbook holds what is happening right now.
What powers what
| When you see... | It comes from... | Read |
|---|---|---|
| An agent's row on the Office | Rows in the logbook, and files the agent wrote | The Office |
| A question card from an agent | An ask row in the logbook | How an agent asks you |
| A red or amber health card | A check that wrote its own card | The Health tab |
| "Held" on a message | The send guard | The send guard |
| A job on the Every job tab | The routines list, routines.json | Routines and the registry |
| An agent's goal and limits | Its contract file, agent.md, in the vault | An agent's files |
An example day, through the map
This is a made-up morning, but every step is how the real parts work.
- At 9:00 the alarm clock sees that Ada's wake time has come. It starts her.
- Ada reads her contract, her plan, her memory, and her inbox. A wall blocks every other action until she has read them all.
- A business owner replied to her invite overnight. She never sees the email itself. She sees a checked summary from the quarantine.
- She drafts an answer. She is not allowed to write to this person alone yet, so the send guard holds it.
- She asks the owner: "Send this answer to the business owner who replied?" with her reasons. The question shows up on the Office and as a link on the owner's phone.
- She writes what she learned, picks her next wake time, and stops.
- The owner taps Yes. The exact recorded send runs. The Office shows it as done.
Connected to
- What is Company OS: the whole idea on one page.
- How an agent wakes: the full wake loop.
- Prompt injection and the email quarantine: the "In" gate.
- The vault and The logbook database: the two stores.