05 the harness

fleet os, and what is still planned.

the harness, the protocol, and an honest line between built and intended.

Fleet OS is two things glued together: a dashboard that shows the whole estate at once, and a protocol that lets an agent remember what happened in a session it was not part of. The first is built. The second is built. The third thing — the part that would make it a product rather than a tool — is planned and not started, and this page says so in the open.

memory graph
7,106

neurons, linked by 47,435 synapses across 15 regions

protocol version
22.0.0

the shared-memory protocol the fleet speaks

review judges
67

in the quality loop, of which 20 are enabled

planned, not built
4

capabilities designed and deliberately not started

the dashboard

The dashboard is the estate on one screen. It follows a design law — Meridian — which is the rule that every panel must answer "what changed since I last looked" without being asked.

brain viewport
The live memory graph, navigable. You can watch a recall happen rather than being told it happened.
chat
The primary surface. Every turn lands in the audit chain, not just the transcript.
voice
Speech in and out, so the dashboard is usable while driving or walking the floor.
meeting mode
A different posture for group use — the agent speaks last and cites what it used.
files
Documents the agent has actually worked on, with provenance rather than a folder listing.
settings
Where the guardrails live, and where you can see which ones are currently armed.
oversight
The panel that matters: what the agent did, what it refused, and what it asked a human about.
home
The physical estate — solar, mower, cameras, media — because a fleet that manages a house should show the house.

the protocol

what it does

  • Recall before acting — an agent searches the shared memory before re-deriving a fact the fleet already knows.
  • Ingest as you go — durable knowledge is written immediately, not batched to the end of a session.
  • Files and memory are complementary — runbooks hold the long-form record, the graph holds the recallable index.
  • Writes queue — if the memory service is briefly unreachable, writes land in a write-ahead log and flush automatically.

why it is the load-bearing part

  • A lost session is lost knowledge. The protocol is the answer to that.
  • It is what makes autonomous operation survivable: an agent can resume a project it never saw started.
  • It is the difference between a chat tool and a system with memory — and it is the part competitors copy last.

the part that is planned, not built

Four capabilities are designed, specified, and deliberately not started. Listing them here is the point — a product page that implies they exist is a lie, and the whole premise of this site is that the honest version is more useful.

effect verification
Prove a change did what it claimed before reporting success. The direct answer to the gateway defect that records a stream successful before reading a byte.
simulate before promote
Run a proposed change against a model of the estate first. A change simulator already exists; wiring it into the promotion path does not.
multi-agent deliberation
A Proposer, an Adversary, a Verifier and an Arbiter. Four roles, one decision, and a written dissent when they disagree.
scar memory
Remember not just what happened but what went wrong — and reach for it before repeating the mistake. The brain already stores scars; the harness does not yet act on them.

what it costs to run

community
free
  • the memory protocol and its API
  • single-machine, single-user
  • your data stays on your box
self-hosted
free
  • the full dashboard and harness
  • multi-agent, with the guardrails on
  • you run it; we publish the config
managed
later
  • hosted, with oversight as the default
  • not offered yet
  • priced per seat, not per token

The honest summary: the memory protocol is real and running, the dashboard is real and running, and the four capabilities above are design documents. If you are evaluating this, evaluate the first two and treat the last four as a roadmap, not a feature list.

relay & premierbot the gateway case studies

documented 2026-10-16 · "planned, not built" is a deliberate distinction