COSMOS · THE TECHNOLOGY
Five systems, taken apart.
Not a feature list. Each of these is a load-bearing decision, and each one is here with the reasoning attached — including what it refuses to do. Everything on this page is interactive. Press things.
- 01Agent OSThe layer beneath the apps — one core, two shells, one place that decides
- 02BrainJournal, index, graph — and the rule that keeps them honest
- 03AdaptersSeven open contracts and an industry-standard protocol, both ways
- 04Vault & permissionsWhere it stops, what it never stores, and who decides
- 05ResemblanceRange of recognition — the one the other four are for
SYSTEM 01 · AGENT OS
One core. Two shells.
One place that decides.
Most assistants are an app with a model behind it. Cosmos is built the other way round: a core that owns configuration, discovery, permission and events, with the desktop and the web as two shells over it. Nothing is decided twice.
A real request crosses four layers and one policy check. The point of the architecture is that the third row is always the same row.
Why one core
Two products drift. The moment desktop has its own permission logic, a rule fixed in one place is still broken in the other.
Why contracts
If extension happens through a documented surface, the inside can be rewritten without breaking anyone. If it happens by reaching in, it cannot.
Why agents are processes
A feature waits to be called. A process observes and speaks first. That difference is what makes an assistant an operating system.
SYSTEM 02 · BRAIN
It keeps everything,
and it can still find it.
Keeping everything is easy. Finding it again is the product. Three layers do three different jobs, and a memory you cannot retrieve is treated as a memory you never kept.
Illustrative — sample memories, not a live account.
Channels
Conversation, agents, connected services. Anywhere it can observe is an entrance — and if the only entrance is a chat box, that is exactly how much it knows.
Quality
Only what will still be true later. Your CPU temperature is false thirty seconds from now; that is not memory, that is noise.
Repetition
Once is an event; twice is a disposition. A system that hears the same thing ten times as if for the first time is not learning you.
THE RULE THE CODE ENFORCES
Every feature must answer what it stores and what it reads back before it can exist. A feature that never touches memory is not part of this product — and storing without ever reading back is a feature built half-way.
SYSTEM 03 · ADAPTERS
A grammar,
not a list.
Every product that competes on integrations eventually loses, because no company can support every technology in the world. So Cosmos does not decide what it connects to. It publishes how connecting works, and lets the world arrive.
AND CONNECTING HAS TO BE ONE CLICK
Being connectable and being connected are different things. The moment a feature asks a non-developer for an API key, a client ID or a token, that feature does not exist — because they stop at that screen. Registration is something we do once, not something every user does.
SYSTEM 04 · VAULT & PERMISSIONS
Trust comes from
boundaries, not capability.
Working on your behalf does not mean acting as it pleases. Three things decide whether anything happens: what this persona is allowed, what the capability policy permits, and whether the action can be undone. Try to get something past them.
READY
Pick a request on the left and watch it hit the boundary.
Secrets are never remembered
The brain is searched and loaded into prompts. Anything that goes in can come back out somewhere you did not expect — so card numbers, tokens and passwords are kept out of it entirely and live in a separate vault the brain cannot read. Safety comes from absence, not from defence.
Your memory is a file you own
Local first: the original lives on your machine. You can read it, correct it, delete from it and carry it out whole — and every memory records where it came from and how confident it is, so a bad source can be rolled back in one move. Memory you can't take with you was never yours.
SYSTEM 05 · RESEMBLANCE
Not imitation.
Range of recognition.
This is the one the other four exist for, and it is the one most often misdescribed. Cosmos does not try to act like you. It widens how much of you it can recognise — and resemblance is what follows from that, not a thing aimed at directly.
IT WRITES
Generic. Correct sentences, nobody's voice.
IT JUDGES BY
Whatever the model weighs by default.
IT SURFACES
What you literally asked for, and nothing else.
EVERY NIGHT
Summarise the day, drop duplicates, connect the new people and events onto the map, recompute what mattered. In the morning it wakes up sorted — which is why the range widens even on days you barely use it.
AND THE LINE THAT DOES NOT MOVE
However wide the range gets, what you said yourself always wins. No amount of learned pattern overwrites a decision you made out loud. People above, automation below — and the key to this stage is not the technology. It is the trust built in the four before it.