Who did what
Kael sent 34 renewal notices
Ana approved the price wording
Mira read four weeks of threads
Sam corrected Kael on holiday sends
Vesa reconciled September
Ade reassigned two tickets
Tova wrote the week up
Priya marked check 1 met
Kael held two for the holiday
Mira filed 4 notes under Billing
Vesa refused a send, and said why
What the team learned
Never send a price change on a Friday.
Sam corrected Kael on Tuesday. 11 agents have it, across six people and four clients.
Anything about price goes to Ana first.
Set by Ana in September · used 41 times since
Refunds under £200 need no second pair of eyes.
Set by you · applied by three different agents this week
Enterprise wants the invoice before the notice.
Learned from two runs, confirmed by Priya · 15 September
Bank holidays are never a send window.
Sam corrected it this week · already applied by Kael on Friday
Nobody had to tell a second agent any of these, in any client, under any model.
Still with a person
Two renewals land on the bank holiday · Ana
Kael and Vesa disagree on the send date · Ana
Everything else
The other 316 runs are written up, attributed and closed. Nobody spent Friday assembling that.
Retention
Set by you. What was done is never editable, by anyone — us included.
Access
Six people on Billing. Two can change what an agent is for. Nobody can edit the record.
Where this is running
Your account, eu-west-1, against your own Postgres.
Export
All of it, as plain text, whenever you ask.
What a team gets that one person does not
One identity, one memory, one record.
Every change has a name on it
Person or agent, recorded the same way — and never confused for each other.
See identityOne correction, everyone's agents
Somebody fixes it once on a Tuesday. Nobody on the team types it again.
See memorySam corrected KaelTuesday, once
Never send a price change on a Friday.
11 agents have it · 6 people · 4 clients
The week is already written
The audit trail is a by-product of the work, not a project somebody runs.
Read the recordA heavy renewals week, and one call still with Ana.
Written by Tova · 318 runs read
Six people, eleven agents. Nobody assembled this.
Connect your agents to the tools you already work in
Any client that speaks MCP. One endpoint, one token, the same agent.
Run it the way your review says it has to
Your infrastructure, your provider, your rules.
Your infrastructure, your database
Run the server in your own account, against a database you hold.
Read the docsYour model provider
Bring your own. Sylvia is where the work is kept, not the model that does it.
Why that mattersRunning onBedrock
Lost in the swapnothing
Access that matches your org
Who can see a record, correct a memory, or change what an agent is for.
Tell us your rulesBring it in-house.
One identity per agent, one memory for the team, on machines you control.