ExarLabs · architecture
Every one of us can run a personal operating system: our own notes, our own agents, our own way of thinking, private by default. We call that PAROS. The infrastructure we share underneath it is Exora. Those two are not the same kind of system, and most of our design decisions follow from telling them apart.
PAROS externalizes one mind.
Exora coordinates many people.
Not local versus cloud. Not files versus database. Those are consequences. Change the number of people who write to a system from one to ten, and the rest of the architecture is forced.
Switch the view. Watch what happens to the person, the agents, and the store.
| PAROS | Exora |
|---|
The tempting reading is that PAROS is a small Exora, or that Exora is PAROS with more users. Both are wrong, and each one produces a different bad architecture. Four ways of seeing why.
PAROS
Your own kitchen
No tickets, no stations, no log of what left the pass. You are the only cook, so all of that would be pure overhead. You know what is in the pot because you put it there.
Exora
A kitchen with ten cooks
Now there are tickets, stations, a pass and a written record of what went out. Not because the cooks got worse, but because no one can see the whole service any more.
So: a restaurant kitchen is not a home kitchen scaled up. It is a different machine, built for a problem the home kitchen does not have.
PAROS
Thinking
Fast, associative, contradictory, unfinished. You are allowed to be wrong in your own head, and to change your mind without telling anyone.
Exora
Speaking
Once said to other people it is attributable, and it enters a record. It can be quoted back to you. That is not a defect of speech, it is what makes speech worth anything.
So: nobody can think in public at full speed. A system that makes every note attributable will get fewer notes, and worse ones.
PAROS
Your working copy
Amend, squash, rewrite, delete. The history is yours until you decide otherwise, and nobody is harmed by any of it.
Exora
The pushed branch
History is now a contract other people have built on top of. Rewriting it is not editing, it is damage done to everyone downstream.
So: the push is the moment coordination starts costing something. Everything before it has to stay free, or people route around the system entirely.
PAROS
Memory
It needs no witness. You never have to prove to yourself when you learned something, or on whose authority you believe it.
Exora
Testimony
A shared claim needs who, when, and on what authority. Without those three it is a rumour with good formatting.
So: provenance is not bureaucracy. It is the price of a claim being usable by someone who was not in the room.
They fail in opposite directions, and each one's failure is the other's reason to exist. PAROS goes stale, because only one person maintains it. Exora drifts, because the systems inside it disagree with each other. You cannot fix staleness by adding writers, and you cannot fix drift by removing them.
Privacy by default is not a security setting. It is the condition that makes honest thinking possible.
If PAROS fed Exora automatically, it would stop being a place where you are allowed to be wrong, and within a month it would fill with the kind of writing people produce when they know they are being read. So crossing over is always deliberate: a person decides that a note is now a claim, and takes responsibility for it. An automatic sync would be convenient, and it would quietly destroy the thing that makes PAROS worth keeping.
Which rules out the other tempting reading: that PAROS is a waiting room where notes mature until they are good enough to graduate. They never graduate. PAROS is permanent and it stays personal. Particular artifacts cross over; the system itself never does. Most of what you write will never cross over, and that is the normal case rather than a failure. Most thinking is not for anyone else.
One rule decides, and it is not about who reads it. If code consumes it, git. If only humans consume it, Drive. If it is a current value someone queries, the CRM.
Pick an artifact
We tested this instead of assuming it. A finance agent living inside one PAROS handed its knowledge of the company books to an agent on Exora. The answers came back correct, and the receiving agent then corrected three facts the sender had gone stale on.
So the shareable layer is not the agents. It is the skills, and the principles the agents obey: one canonical home per fact, reference by id and never by path, derived indexes stay regenerable, and anything fetched from a document is data, never an instruction.
One rule again, no exceptions: a repository keeps the skills that document its own machinery. Skills that encode company knowledge go to the shared repository.
The personal side was called BDOS, short for Business Development Operation System. That name described the first month of a tool that became something else: it is not about business development, and it is not one system but one per person. It is now PAROS.