Nothing reaches the team without a person
Agents propose. The drafts wait in a queue that only the people who own that part of memory can see. Daniel approved one this morning. Three are still waiting.
Fernhill is made up. The names, memories and numbers are sample data.
| Draft | Goes into | Proposed by | State |
|---|---|---|---|
| Orders over 50 units get 15% offLesson | Shared memory | sales-agent | In conflict |
| Quote delivery dates from the warehouse calendarLesson | Shared memory | Nightly pass, from 2 agents | Merged |
| The courier does not move live plants over the weekendLesson | Shared memory | ops-agent | Approved by Daniel |
| Refunds over $500 need a second approverDecision | Decisions | ops-agent | Waiting |
$ circles review approve \
courier-no-live-plants-over-the-weekend
Approved courier-no-live-plants-over-the-weekend
into org/shared. The proposer's receipt says so.
$ circles review list
orders-over-50-units-get-15-off
lesson → org/shared by sales-agent 2d · 1 open conflict(s)
Orders over 50 units get 15% off
quote-delivery-dates-from-the-warehouse-calendar
lesson → org/shared by consolidation 1d
Quote delivery dates from the warehouse calendar
refunds-over-500-need-a-second-approver
adr → org/decisions by ops-agent 5d
Refunds over $500 need a second approverThe screen is a preview of the interface we are building. The terminal is how it works today. Both show the same sample data.
What each state means
A reviewer does one of three things with a draft. Each takes one click or one command.
- Waiting
- Approve it and every agent on the team starts its next session with it. Reject it with a reason and the agent that proposed it gets the reason.
- Merged
- ops-agent and support-agent learned the same thing on their own. Overnight the two notes became one draft: "Quote delivery dates from the warehouse calendar". You review it once.
- In conflict
- The draft disagrees with something already in force. You see both sides before you can approve anything. See how that is settled
Trace any memory back to where it came from
Start from the lesson Daniel approved and walk backwards. Each step is a stored record.
- Shared memoryThe lesson · Approved by Daniel on 2026-11-10
- ReviewThe draft · What was proposed, word for word, and the receipt sent back to the agent
- RecallWhat the agent knew · The slice it was given that morning, stored as pk_01M775J…
- Task workspaceThe task · Find out why order 48213 arrived wilted
- SessionThe session · Which agent, under whose name, and when
| When | Who | What they did | Result |
|---|---|---|---|
| 2026-11-10 09:14 | ops-agent | Proposed a lesson into shared memory | Allowed, draft created |
| 2026-11-10 09:15 | ops-agent | Tried to read the review circle | Denied, with the cause named |
| 2026-11-10 11:02 | Daniel | Approved the draft | Lesson in force, draft superseded |
Look at the second line. An agent can put a draft into review, and it is refused when it tries to read one back.