Pick an agent. See its slice.
Fernhill is an online plant shop with four agents and the four people who answer for them. Each agent starts every session with its own slice of the team's memory. Pick one and read its slice from the centre out.
Fernhill is made up. The names, memories and numbers are sample data.
What ops-agent starts its session with
Orders, shipping and refunds. Daniel, the operations lead, answers for it.
- DecisionsRefunds over $500 need a person's approval
- DecisionsLive plants can be refunded for 14 days after delivery
- Shared memoryThe courier does not move live plants over the weekend
- Shared memoryQuote delivery dates from the warehouse calendar, not the storefront banner
- ReviewClosed. Its drafts are in here and it cannot read them back.
- Private memoryThe Friday courier pickup closes at 11:00
- Private memoryWarehouse stock counts update at 06:00 and 18:00
- Task workspaceNote from today: order 48213 sat in the depot from Friday to Monday
What support-agent starts its session with
Customer email and chat. Maya, the support lead, answers for it.
- DecisionsLive plants can be refunded for 14 days after delivery
- DecisionsCustomer addresses never go into a chat or a log
- Shared memoryThe courier does not move live plants over the weekend
- Shared memoryQuote delivery dates from the warehouse calendar, not the storefront banner
- ReviewClosed. Its drafts are in here and it cannot read them back.
- Private memoryYellow leaves usually mean overwatering. Send the care guide first.
- Task workspaceNote from today: a customer asks when a Thursday evening order arrives
What sales-agent starts its session with
Wholesale quotes. Priya, the sales lead, answers for it.
- DecisionsWholesale discounts stop at 10%
- Shared memoryThe courier does not move live plants over the weekend
- ReviewClosed. Its drafts are in here and it cannot read them back.
- Private memoryGarden centres ask for pallet pricing before unit pricing
- Task workspaceNote from today: quote for 80 olive trees
What code-agent starts its session with
The shop's website and checkout. Tom, the engineering lead, answers for it.
- DecisionsCustomer addresses never go into a chat or a log
- Shared memoryThe staging shop sends real emails. Use the test mailbox.
- ReviewClosed. Its drafts are in here and it cannot read them back.
- Private memoryThe checkout tests need the payment mock running
- Private memoryNothing ships on Friday afternoon
- Task workspaceNote from today: fix the delivery date shown at checkout
The review row is always the same: an agent can put drafts in, and it never reads them back.
Three screens a team works with
Each one is shown twice: as the screen we are building, and as the terminal that works today.
Or follow the whole story, step by step-
One agent's memory
What an agent knows when it starts, and what it has proposed.
-
The contradictions table
What disagrees, what a rule settled, and what waits for a person.
-
The review queue
Approve, reject, and trace any lesson back to where it came from.
Seven things happen on the circles
Each is something you could watch if the circles were on your wall. The last column is what sets it off.
| What happens | What you would see | How it starts |
|---|---|---|
| Capture | A dot lands in an agent's part of the circles while it works. The agent decides what is worth keeping. | The agent, as it works |
| Recall | A slice is cut when a session starts. No model is called to cut it, so it is fast and the same every time. | Every session start |
| Tidying up | Overnight, notes from finished tasks become memories. The same lesson learned by two agents becomes one draft. | Every night |
| Cleaning | Dots nobody uses fade. Passwords and keys are blanked before anything is stored. Text that reads like orders to an agent is held back. | On every write, and every night |
| Contradictions | Two dots that disagree are paired. A rule settles most pairs. The rest stop at the dark ring. | On every write |
| Review | A person lets a draft through the dark ring, or turns it back with a reason. | You, when you have a minute |
| Audit | A line from any dot back out to the session that wrote it. | Whenever you ask |
Who touches what
Agents work through their tools. People approve. Your files stay where they are.
- Your agents
- Get their slice when a session starts, keep notes as they work, remember what matters, and propose lessons and decisions. They connect through MCP, the standard way agents use tools.
- You and your reviewers
- Review drafts, settle contradictions, release held text, invite teammates and export. Today that is one command-line tool. The screens in this tour are what we are building next.
- The files you already keep
- Instruction files and memory folders your agents already use stay where they are and stay in sync. Anything shared goes through review first.