AI teammates you can give real work to

Data sovereignty

Most AI products keep your context on somebody else's servers. Claude Agents installs PostgreSQL on your own machine and everything is recorded in that one place. It is a database file on a disk you control, in a format any tool can read if you grant it permission.

You can open it directly via a human user interface so you never lose access to your data. You can back it up. You can take it with you. You don't need permission from any third party to get to your own data.

Your ontology

Most systems make you fit your business into their categories. Here you write your own.

The database holds the kinds of record your business deals in and the relationships allowed between them, as rows you can edit. An invoice may be billed to a person or an organisation. A document may be about a project. A decision may depend on a report. You add what your business actually has, in the words your business actually uses, and an agent that tries to connect two things in a way you have not permitted is refused.

No more expensive, complex CRMs, ERPs, or other applications that need acronyms to describe them.

Each agent sees only its work

Every database record carries a label. A table says which agent may read and write which labels. The database applies it to every query, row-by-row, including ones the agent writes itself.

The rule lives in the database rather than in the software, so it holds even when an agent has been talked into asking for something it should not have. An agent can read the rules that bind it. It cannot edit them.

Agents do not message each other

Grok Bot lets its agents pass work between themselves. Claude Agents does not, on purpose.

A request travels as a file, and a person reads it on the way. That means a document carrying instructions aimed at a machine reaches nobody who can act on it, and every widening of what a machine can touch passes a human. You trade some autonomy for a boundary that holds.

Swap the engine, keep the record

Every session records which engine and which model did the work. Change the model and the record says which conclusions came from which, with dates.

The record does not belong to the engine. It belongs to you, and it outlives whichever model wrote into it.

Based on the knowledge framework

Data is the file. Information is that file read into shaped facts: this invoice, this amount, this supplier. Knowledge is how those facts connect and what they explain. Judgement is the decision you took, recorded with what it rested on.

Then the loop closes. The action taken sits beside the decision. The consequence sits beside the action, holding what you expected and what actually happened. A decision nothing followed from is visible as exactly that.