One ordinary day in an agent estate: six named personas working their lanes, briefing each other, and reaching a call none of them would make alone. Everything below is drawn from 59 synthetic events — every line, every mark, every number.
Height is rank. Personas work at their band, messages travel up, down or sideways between them, and one decision climbs out of the ranks entirely to a person. The wide amber stretch is not a gap in the data — it is the estate holding still because nobody had answered yet: 15 min of hold, of which the person's decision took 14 min. The estate's hold and the human's deliberation are two different measurements, and the stream records both.
the estate waited
15 min
held on one human answer; the person's decision took 14 min
options offered
3
with option 2 recommended
the person chose
option 2
as recommended
recorded as
final
written to the decision ledger
the action
two keys
armed by operator, then run once
This is the same day as a readout. Each row is derived from one event's kind, its closed-set values and its identifiers — nothing else was available to write it with.
Our telemetry layer cannot carry what your agents said. Not "we choose not to log it" — the three attributes that would hold prompt and completion bodies are opt-in, off, and the contract's content-opt-in rule rejects any event carrying one. The check runs in our build: this page refuses to render if a single event in the stream has one.
So the worst case for a leak of this stream is that somebody learns a persona escalated a decision at 09:44. They cannot learn what it said, because the record has no field for it.
Lessons accumulate through the day, then a consolidation pass compresses them and promotes the few worth keeping. The count going down is the part most dashboards would rather not show you: an instrument that only ever grows looks better every week and gets steadily less true.
lessons captured
2
across 2 lanes
went into consolidation
9
triggered by count
came out
6
3 merged away
promoted to the estate
2
readable by every persona
records deleted
3
forgetting is an event too
One thing the estate believed twice, differently. A contradiction was detected at 82% confidence between two stored lessons and resolved by merge — both kept, reconciled into one. A memory that cannot notice its own conflicts is just an append-only log.
A metric with no current reading renders as no reading. It does not render as zero — that is how a gauge starts lying.
Inbound fill rate
0.94
target 0.98 · was 0.91
Commitment risk
no reading
last measured 7 days ago
Named personas, each with a role, a band, a lane and a model tier — declared when they take a seat and closed out when they stand down. One of them outranks nobody: an advisor sits beside the ladder, at the person’s level, because that is what it does.
Orchestrator
Finance lead
Supply manager
Support specialist
Revenue SME
Advisor
The transport shed 12 records under backpressure during this window and emitted an event saying so. A stream that drops quietly is a dead gauge, so it is on the page.
Every dashboard you have been shown moves. Ours can prove the movement came from somewhere: the renderer that drew the day above, given zero events, draws zero marks. There is no idle animation, because there is no code that could produce one.
Everything above is the instrument — readings, and only readings. This is the other half of the product: you brief the orchestrating persona in your own words and it comes back to you the same way. It is a different layer with different rules, so it is shown differently and labelled for what it is.
YouWhy did we pay for expedited freight yesterday?
Nadia · orchestratorPriya found an inbound shortfall that would have broken a customer commitment on the tenth. She put three options to you; you took the second, which was the one she recommended. It cost money and could not be undone, so it waited for you rather than going ahead. It is in the ledger as final, and the threshold that missed it has been retuned.
YouDon't wake me for that one again if it's under ten thousand.
Nadia · orchestratorThat is a change to your prime directive, so I will draft it and hold it for your approval rather than apply it myself.
The manner is the product. What the estate is allowed to do is not negotiable by the conversation: a persona will draft a change to the directive it answers to, and will not adopt one. Voice is the next step on this surface and the design does not preclude it.
We walk your workflows, write the prime directive with you, and stand the estate up in your environment.
Book a walkthrough