AgentOS

The operating system for autonomous work.

Work orders in.
Completed work out.

The organization survives the model.

State survivesAuthority survivesEvidence survivesWork survives
The model is replaceable.
Most AI systems
Conversation = State
AgentOS
State Model
Claude dieswork survives
OpenAI dieswork survives
The session dieswork survives
The host dieswork survives
No model, agent, session, or host carries the state. The work does.
What comes out

Work orders in. Completed work out.

Most AI systems handle one request. AgentOS operates a governed work system: work orders enter the system, completed outcomes leave it, with authority, evidence, review, recovery, and cost built into every unit of work.

Inputs
Work Orders
AgentOS
a governed work system
Outputs
Completed Work
Not answers. Not conversations. Not tasks. Completed work.
Validated in production

Governed autonomous work, validated in production.

Validated today in software engineering. Designed for governed work everywhere. Multi-agent teams completing real work, attributed by phase, role, model, and token, down to the action.

Work-order governance Multi-agent execution Deterministic recovery Cost attribution QA & adversarial review Self-hosted Local + frontier models Inference Fabric
Work phasePrimary modelTokensCache reuseCost
QACodex GPT-5.5201M92%~$227
DevelopmentClaude Sonnet 4.6450M97%~$210
OrchestrationClaude Opus 4.8208M97%~$143
ReviewCodex GPT-5.538M89%~$55
ArchitectureClaude Opus 4.853M96%~$46
GatekeepingCodex GPT-5.522M91%~$36
PlanningClaude Opus 4.826M97%~$22
Every dollar traces to the phase, role, model, and action that spent it, where most platforms can only report a monthly total.
The problem

AI can answer questions. Organizations need work completed.

Answering a question is not the same as completing work. For any piece of completed work, a leader should be able to answer seven questions in seconds, the ones a chatbot can't:

01
Who did the work?
The work order names the worker, role, and model behind every action.
Hover
02
Why was it allowed?
An execution contract declares the allowed scope, tools, and authority before anything runs.
Hover
03
What grounding did the agent receive?
FAFO Memory supplies a grounding bundle: the code, decisions, and references the work was based on.
Hover
04
What changed?
Every state transition and artifact is recorded on the work graph.
Hover
05
What evidence exists?
An evidence bundle is attached to the work and must satisfy the acceptance contract.
Hover
06
What did it cost?
A cost record is attributed per action, rolled up by phase, role, model, and work order.
Hover
07
Can the operator trust it?
QA and an independent gatekeeper verify before close. The answer is a hard yes, not faith.
Hover
AgentOS answers all seven in seconds.
For any unit of work, anytime. If you can't, you're shipping on faith.
From request to outcome

AgentOS finishes the job.

A chatbot returns an answer and hands the work, the proof, and the accountability back to you. AgentOS carries a request all the way to a completed, evidence-backed deliverable.

Conversational AI

Question Answer Done

Produces answers. The work, the proof, and the accountability are left to you.

AgentOS · transactional

Work Order Execution Evidence Review Completion

Produces completed work, with the authority, evidence, and acceptance built in.

The combination

The power is in the combination.

Every other system answers
"How do I get an AI to do work?"
AgentOS answers
"How do I run AI workers like an auditable organization?"
01

The work order is the authority.

Not the conversation, not the agent, not a task board. Authority lives in a durable work order: scope, contracts, and acceptance criteria the work must satisfy to close.

scope → work order → contracts → acceptance → execution → QA → governance → close
02

Evidence-based completion.

Completion is derived from evidence and independent review, never from an agent's claim that it's done. Nothing closes without proof.

work → evidence → review → close
03

Governed state transitions.

Every change of state, scope, authority, or acceptance is an explicit, recorded transition. The work graph is always in a known, auditable state, never a guess about what happened.

04

Economic attribution.

Not "monthly spend." Planning, architecture, development, QA, review, and governance: each attributed, per work order and per deliverable. The cost of work, broken out.

05

Deterministic recovery.

For most systems, conversation lost means state lost. Here, state survives, the runtime is rebuilt, and work resumes from durable state. The hardest problem in autonomous work, solved.

06

Model independence.

Claude, Codex, OpenAI, local models, the Inference Fabric: interchangeable execution resources. AgentOS owns authority, state, governance, and cost. Providers are workers, not the system.

The system

A governed execution system for autonomous work.

Workers perform the work. AgentOS determines what work is allowed, how completion is proven, what it cost, and how it recovers.

Most AI systems
Conversation Answer
Most agent systems
Task Agent Result
AgentOS
Authority Execution Evidence Review Acceptance Completion
Autonomous workers · governance · evidence · recovery · economics · memory · inference routing  →  one operating system.
The shape of the work

How a work order becomes completed work.

Authority, grounding, execution, and proof in one flow. Each named system has one job; AgentOS holds them together.

AgentOS architecture flow A work order enters AgentOS, which coordinates FAFO Memory (grounds the work), Agent Swarm (performs the work), and Inference Fabric (executes the work) to produce evidence. Evidence is reviewed, and completed work leaves the system. INPUT Work Order GOVERNS THE WORK AgentOS GROUNDS FAFO Memory PERFORMS Agent Swarm EXECUTES Inference Fabric DERIVED Evidence VERIFIED Review OUTPUT Completed Work
Claude Code · OpenAI Agents · CrewAI · LangGraph

Those systems execute work.
AgentOS governs it.

The execution model

A governed state machine.

Most agent systems run a loop and hope it converges. AgentOS advances a governed state machine, which is what makes governance, economics, recovery, and completion possible in the first place.

Most agent systems
Observe Think Act Repeat
AgentOS
State Transition Evidence Verification Next State
Every transition is recorded, evidenced, and verified.  →  Cost, recovery, and completion fall out of the model.
Deterministic recovery

The work survives the worker.

No model, no agent, no session ever holds the state. Authority, progress, evidence, and routing live in a durable work graph outside the model, so when a worker dies, and workers always die, the work doesn't even pause.

01

Resume from durable state

Authority and progress live in a durable work graph, not a chat window. Execution picks up exactly where it left off.

02

Rebuild the team

A dead Claude, Codex, or session is replaced. Workers are temporary; the work system is permanent.

03

Continue execution

Crash, kill, or restart, with no operator intervention. Work is recovered, never lost and never duplicated.

The estate

One platform. Four systems. One job each.

Each system has one clear job and one clear boundary. That separation is what keeps it replaceable: swap the memory layer, or run the fabric in front of another swarm, without touching governance. Open any one to dig in.

Beyond software

One governance model. Any kind of work.

Software engineering is where we prove it. But the model, work order, roles, contracts, evidence, review, completion, cost, is about work, not code. The work changes from domain to domain; the governance stays the same, and that is where the market is.

Engineering
build → ship → review → close
Marketing
campaign → content → review → publish
Legal
contract → review → amendment → approval
Operations
investigate → remediate → verify
Accounting
close → audit → correction
Compliance
assess → review → attest
The work changes. The governance model stays the same.  →  Governed autonomous work is the category.
Not one product

Six systems in one.

Most platforms provide one of these. AgentOS combines all of them into a single operating system for autonomous work.

Autonomous WorkforceSpecialized AI workers take the job and run it to completion.
Governance EngineAuthority, evidence, review, and acceptance. Safe to put in charge of real work.
Economic Control PlaneCost attributed per action, models routed by class, spend kept under budget.
Recovery SystemState survives any worker. Work resumes from durable state, never lost.
Memory SystemCode, decisions, and cross-agent learning, so nothing is rediscovered twice.
Inference LayerLocal and frontier models on your own GPUs, powered by the Inference Fabric.
Most platforms provide one of these.  →  AgentOS runs all six as one governed work system.
Where it fits

One stack. One cost ledger. One security review.

Adjacent to all. Replaces none. Composes with all.

AgentOS sits underneath the tools you already run, not against them. Keep Claude Code and Cursor in the editor. Call a frontier agent from inside it. A LangGraph or CrewAI workflow becomes a governed execution contract; a framework persona becomes a governed worker with a scoped tool policy. It adds authority, evidence, and cost, and asks you to rip out nothing.

Claude CodeCursorDevinLangGraphCrewAI
5 products → 1

Governance, a memory layer, fleet-scale inference, GPU vector search, and budget-bounded provisioning each are someone else's whole product elsewhere. Here they arrive as one self-hosted stack, with one cost ledger, one security review, and one runbook. Local and frontier spend land in the same ledger, attributed per task.

Sovereign by default

You decide what leaves your perimeter.

The platform, your code, your weights, and the local model tier run inside your perimeter, from a single workstation to a multi-host GPU fleet. Frontier models are optional and governed: AgentOS controls what work is allowed to reach an external model, and attributes every token either way. No hosted source-code custody at any tier.

TIER 01

Developer

A single developer on a single machine. Local database, local Git, a small local model, an optional frontier key on the side. Zero cloud dependency by default, ideal for pilots and regulated solo work.

TIER 02

Team

A shared internal runtime for a team or product unit: shared database, shared inference, shared memory, one persona and tool catalog. Where most organizations land for their first production deployment.

TIER 03

Fleet

A full self-hosted swarm across a multi-host GPU pool, with cross-team dashboards and budget-bounded provisioning across any cloud, your LAN, or your own data center, with zero inbound ports.

Engineering evidence

We don't just make claims.

Every capability on this site is backed by an artifact. Not benchmarks. Not marketing. Real numbers from real work orders, with reproducible commands.

  • Fleet Retrieval
  • GPU Saturation
  • Recovery
  • Evidence Packets
  • Blast Radius
  • Memory Grounding
  • Deterministic Resume
  • Cost Attribution
  • Model Routing
See all evidence →
Governs the work Remembers the work Executes the work

AI workers,
under governance.

We're selecting a small group of design partners to put governed autonomous work into production. If you're putting AI in charge of real work, let's build it together.

We'll only use this to talk about design partnership. · FAFO · letsfafo.com