The Company Brain: your business as one graph
Every client, deal, project, invoice, and document you have, drawn as one map you can walk. It's the same graph your AI agents reason from, and the same graph that decides what they're allowed to see.
Ask an agency owner where a client stands and watch what happens next. The CRM comes up first, for the deal. Then the project board, because that’s where the work actually lives. Then a folder, for the document that got signed. Then finance, to see whether the invoice was ever paid. Four screens, all of them accurate, and not one of them able to answer the question.
The question is a chain. A client became a deal, the deal opened a project, the project produced a document and an invoice. That chain is the most useful thing a business knows about itself, and in most software it survives only in the memory of whoever happened to be in the room. The Company Brain puts it on screen as a single picture.
A map you can walk
The Brain renders your business as one living graph. Clients, deals, projects, invoices, documents, and meetings become connected objects in a single explorable map. Start at a client and walk outward: every deal tied to it, every project those deals opened, every invoice and document those projects produced. You move through a constellation, one connection at a time.
The map is generated rather than drawn, which is what keeps it honest. It comes from the ontology the platform already runs on: the same objects, relationships, and lifecycles that govern the records themselves. What you see is the business as it stands this morning.
The same graph your agents read
The graph your team browses is the graph your AI agents reason from. There is one copy, read two ways: a picture for people, a memory for machines.
Context decides whether an assistant is useful. Give it the whole graph and it can answer questions that cross the business, because it can walk the path itself. Start on a social post. One edge over is the lead that post generated. One more is the deal that lead became. One more is the invoice that deal was paid on, and the amount is sitting right there on it. Three hops, four objects, one traversal, and a question that used to mean opening five systems is now something an agent can run.
People roam, agents get fences
Building one graph that humans enjoy roaming and agents can be trusted inside is the difficult part, because the two demands pull against each other. The whole value of an explorable map is that you can follow any connection wherever it leads. An agent needs the opposite instinct. A junior’s assistant walking the graph must never be able to hop, edge by edge, from a harmless record into a finance secret it was never cleared to see. Powerful reasoning over an unscoped graph is a beautiful way to leak.
The tempting fix is to let the agent read everything and trim the answer on the way out. That fails on its own terms, since by the time the trimming happens the sensitive data has already passed through the agent’s hands. Amolfi attaches access to the data itself and enforces it inside the query. The check runs at the moment of the read, so the set of nodes a traversal can reach is bounded before any of it comes back. The fence lives in the graph, in which edges are there to be followed at all.
Every business already has a graph like this one. It’s in the founder’s head, in the account manager’s sense of which client is fragile this month, in a folder structure someone invented years ago and never explained to anyone. Writing it down as connected truth is the part almost nobody does. Amolfi keeps exactly one model of your business, and the Brain is where you walk through it.