One vocabulary, and everything is one of its words.
The Brain gives what you already have a shape, so a question has somewhere to land and an answer has somewhere to come from.
This is the morning
The screen the night resolves into. Every row is one customer, from every system they arrived in, with what it means and what to do already written.
| Who | Evidence | What it means | What to do | Status |
|---|---|---|---|---|
Marcela Rivas WhatsApp · Gmail · HubSpot |
| first two never resolved | read the threads, then reply | Held for you |
Northbound Ltda HubSpot · Drive · Calendar |
| renewal in 30 days, unowned | assign an owner, send v3 | Held for you |
Tomás Aguirre WhatsApp · HubSpot · Calendar |
| quote going cold, nine days | one message before the demo | Done |
Support queue Webchat · Drive |
| same customer, two cases | merge, one reply | Done |
Eight nouns carry the whole product
Every screen shows one of them. That is what stops an intelligence layer from becoming a pile of widgets with a chat box on top.
- 01
Entities
the things
- 02
Memory
what it kept
- 03
Signals
something happened
- 04
Insights
a pattern, defended
- 05
Decisions
what should happen
- 06
Actions
what executes
A signal is what happened. An insight is what it means. A decision is what should be done. Keeping the three apart is the difference between a product that thinks and one that summarises.
| The distinction | One side | The other | Why it is kept |
|---|---|---|---|
| Observed against inferred | "They asked for delivery before Friday." | "They seem to care about speed." | Only one can be quoted back to a customer. Every memory says which it is. |
| Noticing against deciding | A signal: something happened. | A decision: what should happen next. | A system that only notices leaves the deciding to whoever reads the summary, which is most of the work. |
How is this different from what I have
The question every second conversation asks, answered one rung at a time.
01 · You say
“I can put a chatbot on WhatsApp.”
The answer
A chatbot answers the message in front of it and forgets. The Brain holds the customer, the order, the earlier thread and the open case as one record, and the reply is written from all of it.
02 · You say
“My CRM already has automations.”
The answer
A CRM automates the fields it holds. It does not know what was said on WhatsApp or promised in a document. The Brain reads the conversation, the document and the CRM as one thing and marks what was observed against what was inferred.
03 · You say
“I can connect a model to my data.”
The answer
A model does not keep identity straight across systems and does not refuse a conclusion it cannot back. The Brain resolves who is who with rules you can read, and an insight with no evidence is refused at the moment it is created.
04 · You say
“Agents can just act for me.”
The answer
Here an agent cannot act. It proposes. A separate engine decides against rules you wrote, and only a clean permit executes. Autonomy is earned per action, and the record of every verdict is kept.
A different kind of thing: the brain, with hands it cannot use without permission.
One model, seen through nine lenses
All of them cross-link. A card opens its entity, an entity its neighbourhood, an insight its evidence, a decision its policy check.
| View | What it is for | What it is not |
|---|---|---|
| Today | What deserves you first, this morning. | Not a feed. It ends, ordered by consequence. |
| Entity | Everything known about one customer, company, order or case. | Not a CRM record. It holds conversations, documents and cases too. |
| Graph | How things connect: who belongs to what. | Not a diagram to admire. It is how a name becomes everything touching it. |
| Memory | What the Brain retained, and where each piece came from. | Not an archive. Conclusions, marked observed or inferred. |
| Insights | Patterns with their evidence attached, so you can disagree. | Not a dashboard. Every entry is a claim, not a number. |
| Decisions | What the Brain proposes should happen, and your answer. | Not an approvals inbox for things already done. |
| Ask | A question in plain words, answered from the Brain's own records with the evidence listed. | Not a chat with a model. The counting happens in code; the model only phrases what the records say. |
| Agents | The workers, their versions, where each one runs. | Not the top of the product. Deliberately secondary. |
| Sources | The systems the Brain reads, and when it last did. | Not a settings page. Every conclusion traces back here. |
Grounded in what you already run
Sources are read-only, every record carries the source it came from, and the first time the Brain tells you something surprising you can ask where it came from and get an answer.
The model is easier to see than to read about.
Connect one system and look at a real Today view built from your own data.
On duty ·