When a lighthouse is finished, a night is set aside for its first lighting. By then the tower has been standing for months, the lens is set and the keepers have moved in. What changes that night is not the building. It is the promise. From then on the light burns every night, at a published height, with a published character: a pattern of flashes a navigator can look up on the chart and match to the one on the horizon. Anyone at sea can take a bearing on it and know where they are.
This log is our first lighting. Pharos Fabric has been under construction, quietly, for a year. Starting today we are going to write about it in the open, on a schedule, in a way you can take a bearing on.
What Pharos is
Pharos Fabric is a semantic operating system for AI agents that have to be trusted. It takes the questions every agent should be able to answer and keeps the answers as facts in one graph, instead of scattering them across configuration files, logs and other people’s API keys:
- Who is acting? Every actor, whether a person, an agent, a service or the machine it runs on, is a principal with its own key. Nothing acts anonymously and nothing borrows someone else’s identity.
- What may it do? Authority is a capability: a verb on a scope, granted on the record, revocable on its own, and narrowed every time it is handed down.
- Where did this come from? Agents think in a fast working memory where doubt is free. What survives review is promoted into a slow, signed ledger that is never edited, only superseded, so every fact carries the story of how it became one.
- Who set the rules? Policy is data in the same graph, and so are the system’s own verbs. Teaching the fabric something new is a governed write, not a software release.
Sailing Directions walks through each of these with a working instrument you can push on. This post is about why we are writing at all.
Why now
Agents are being handed real work: code, money, other people’s data, decisions that used to need a signature. Most of them are doing it on infrastructure that was never meant to bear the weight. Identity is a shared token. Memory is whatever fits in the context window. Provenance is a log file someone might read later. Authority is whatever the token happens to allow.
A navigator would recognize the method. It is dead reckoning: each position is estimated from the one before, by speed and heading and hope, and the error compounds out of sight until the coast arrives early. Dead reckoning is not wrong. It is how every ship crossed an ocean before there was anything to take a fix on. But nobody serious navigates by it alone once a fixed light is in view.
The fabric is our attempt to put a fixed light in view. It does not make an agent’s decisions. It gives the agent, and the people responsible for it, something steady to take a fix on at every step: a signed position on a shared chart that anyone with the right to look can check.
Why the name
The Pharos stood on a small island at the mouth of Alexandria’s harbour from around 280 BC until earthquakes brought it down in the Middle Ages. Ancient writers ranked it among the wonders of the world. Its lasting achievement is quieter than that: the island’s name became the word for a lighthouse in half the languages of the Mediterranean. Phare, faro, far.
What I take from it is a division of labour. The Pharos never steered a ship. It gave every ship the same fixed point to steer by, so that captains who had never met could agree on where the rocks were. That is the job we want infrastructure for agents to do. Agents will be built by many hands, on many models, for many purposes, and none of that needs to be centralized. What needs to be shared is the chart.
What this log will hold
Three kinds of writing, in roughly equal measure.
- Essays on the architecture. Arguments, not announcements: why the fabric is shaped the way it is, what it gives up, and where the ideas came from.
- Field notes. What we built, what broke, and what we learned that we did not expect to. Some of the most useful things we know arrived as failures.
- Arguments with the field. Where we think the current generation of agent infrastructure goes wrong, and which older ideas deserve another look. A surprising amount of what agents need was worked out decades ago, in capability systems and knowledge representation, and then set aside.
To begin, we are reissuing six pieces written over the past months, each revised for this site:
- Capabilities All the Way Down: the sixty-year-old security idea the fabric is built on, and why agents finally need it.
- Why Reification Breaks the SQL Mind: the hardest problem in semantic computing is not technical.
- Fast Memory, Slow Memory: why the fabric keeps two memories with different physics, and how a thought becomes a fact.
- The Shell Is the Point: why serious agent work happens in a terminal, and what that says about interfaces.
- The Agent Memory Problem Nobody’s Solving: the case that agent infrastructure, not the models, is where things break.
- The Ground Truth Problem in Controllable Video: a field note from the generative side, on labels that are measured rather than estimated.
How we will write
A light is only useful if its character can be trusted, so here is ours.
We will not report a benchmark without its method, or describe something as running unless it is. When we are speculating, we will say so. When we change our minds, the post will say what changed and when, rather than quietly becoming something else. That last one is the fabric’s own rule applied to its writing: facts are superseded, never edited, and the earlier version stays on the record.
One detail you might enjoy. This site is itself a document in the fabric. Its pages were promoted into the ledger as one signed version, checked against the canon they cite, and held at review before anyone outside could read them. The log you are reading went through the gate it describes.
An invitation
Pharos Fabric is in private development. If you are building agents that have to be trusted, with real authority over real things, we would like to hear what you are running into. Write to hello@pharosfabric.ai. We read everything.
The light is lit. We will keep it burning.
— Erich Greenebaum