Pharos Fabric
Architecture

How the fabric
holds its course.

Six passages through Pharos Fabric: the loop that keeps state true, the two memories, the citizens who act, the authority they carry, the verbs they use, and a record that never blinks.

Each star is a passage. Choose one to sail there.

I — The loop

A declaration is a standing truth.

Nothing in the fabric is done by command. A fact declares what should be true, and a reconciler keeps it true. It watches the declared state, compares it with what it observes, takes the smallest step that closes the gap, and records what is now so.

It compares states, not messages, so it heals damage it never saw happen. Reconcilers are stateless. Everything they know lives in the graph, so one that restarts resumes exactly where the truth says it should.

Set the vessel adrift. Then stop the reconciler and watch what dead reckoning does.

The declared course, held
3127445248 DECLARED · 090° WATCH DIFF CONVERGE OBSERVE
Off the declared course: 0.0 cables
II — Two memories

Doubt is free at sea. Truth is earned on the chart.

Fast memory is where thinking lives. Agents and people build constructs there, speculative working graphs reshaped freely with no ceremony at all. Slow memory is canonical, immutable and audited. Neither is a cache of the other: one holds what is being considered, the other what is believed.

A construct crosses by ceremony, never by copy. It passes three gates or it is bounced whole, with the reason, and canon is untouched.

Nominate a construct and walk it through the gates.

Further in the logFast Memory, Slow Memory · The Agent Memory Problem Nobody’s Solving · The Ground Truth Problem in Controllable Video

The promotion ceremony

Working graph · fast

  1. Nothing bounced yet.

Canon · slow

  1. Nothing promoted yet.
III — Citizens, not clients

Every actor is a principal. Agents included.

Humans, agents, services and the compute nodes themselves share one anatomy: a key, a set of capabilities, and a history in the graph. There is no trusted interior for a login screen to guard. Every actor carries its identity into every act, and every act lands attributed.

Agents don't call the system. They inhabit it.

HUMAN

An operator

KEY
Bound to a person, never shared
MAY
What has been granted, and no more
RECORD
Every act attributed
AGENT

An agent

KEY
Its own, not a borrowed token
MAY
Exactly its task, for as long as it lives
RECORD
Winds down on the record
SERVICE

A service

KEY
Its own identity, scoped to its work
MAY
Narrow, delegated, revocable
RECORD
Every write traceable
NODE

A machine

KEY
The compute itself is a citizen
MAY
Run what it is assigned
RECORD
Reports its own state as fact
IV — Capability, not role

Authority narrows as it is handed down.

A capability is a verb and a scope: read canon in this domain, promote constructs for this project. Each one is granted deliberately, revoked on its own, and recorded as a fact. A principal can delegate a subset of what it holds and never more, so every chain of authority narrows and every link is on the record.

Capabilities govern reads as well as writes, so the graph looks different to each citizen. There is no wall around the sensitive parts. Each principal reads its own chart.

Choose a principal and see the chart as it does.

Further in the logCapabilities All the Way Down

A chain of delegation
V — Commands are data

The verbs live in the graph with everything else.

A command is a fact. It records a name, what it means, the capability its invoker must hold, and the machinery that fulfils it. Most useful commands are flows, pipelines declared as data and walked at run time under the invoker's own authority.

The shell knows no commands of its own. It asks the graph what exists, filtered by who is asking. Teaching the fabric a new verb is a governed write, not a release.

The list follows the principal you chose above. Change it and watch the verbs change.

Further in the logThe Shell Is the Point

List of lights
Verbs on this citizen's chart
No.CommandMeaningRequires
VI — Canon never blinks

Facts are superseded, never edited.

There is no operation that changes a canonical fact. When the world changes, a new fact supersedes the old one through the same ceremony, and both remain. The ledger remembers what it held and when, and who changed its mind.

Charts have always worked this way. A correction is issued as a notice and entered in the margin, and the earlier edition stays on file.

Issue a correction, then ask what canon held on any day.

Further in the logWhy Reification Breaks the SQL Mind

Corrections to Chart No. 1
Least depth over the bar
4.2 m

Small corrections

    Canon as of
    Earlier entries are never deleted.
    Private development

    The chart is open. The water is ours.

    Pharos Fabric is in private development. If you are building agents that have to be trusted, we would like to hear from you.

    Request early access → Back to the light