maios.dev
Contact

Three systems · One founder

Systems that show their work.

Three systems, built one way: evidence outranks opinion, models are replaceable workers, and the human steps in only by exception.

The mark is the method: a short line for people, a long one for the system that keeps the evidence, a broken one for workers that keep being replaced. The dot is the one question that reaches a person.

The common thread

One way of building.

Three systems for three different worlds, on the same three convictions. Each puts a layer of judgment between people and the machinery that does the work.

People

The human steps in only by exception.

Routine work runs itself. People are called for direction, taste, money and risk, and the question arrives already prepared.

The system

Evidence outranks opinion.

A result counts when evidence says so. Not when its author, a confident model or a majority vote says so.

Workers

Models are replaceable workers.

Models, tools and machines keep changing. The system around them is what lasts: its state, its rules, its memory.

Chapter I · Flagship

MAIOS

State the job. MAIOS owns it.

Private preview
take own understand think design develop discuss execute check fix deliver one mission accepted
Plate I · The harnessRead the chapter

MAIOS

Multi-AI Operating System Private preview
Chapter I · The operating system for AI work

MAIOS isn’t another AI agent. It’s the operating system that runs them.

Give it one plain-language mission. It writes the contract, assembles the right AI workers, has their work checked independently and recovers on its own when something breaks.

Stage
Private preview. Its first end-to-end mission was recorded in October 2026.
People
You, the Operator. Direction, taste, money and risk.
System
MAIOS. Contracts, independent verification, recovery.
Workers
AI workers. Qualified before they’re trusted, replaceable after.
Concept interface · Operator Console
Mission M-0147 RunningVerifyingAccepted

Mission, as stated

“Reconcile our Q3 supplier invoices against the agreed price list and send me every mismatch above 2%, with the evidence.”

Started
09:12 · reversible
Workers
3, chosen for this mission

Acceptance · C-0147

  • Every invoice line parsed or flagged2,318 lines
  • Each mismatch cites invoice, line and price-list row57 mismatches
  • Totals recomputed independentlymatch
  • Held-out sample re-verified0 / 4031 / 4040 / 40
ACCEPTEDDelivered to you · 2 files · evidence 4/4

Run

MAIOS
Builder
Writer
Verifierindependent
Operator
  1. Contract written · 4 acceptance checks fixed before work
  2. Team chosen · builder, writer, independent verifier · one decision brought to you, prepared
  3. Builder delivered reconciliation.csv
  4. Writer interrupted · resumed the same attempt · 0 duplicates
  5. Writer delivered mismatch_report.pdf
  6. Verifier checking · independent of both authors

Acceptance is decided by evidence, not by the workers.

The Operator Console is a design concept, not a shipped interface. The mission and its data are illustrative.
A strong model is a talented employee. MAIOS is the company around it.

MAIOS is model-agnostic. Every AI worker has to prove it can act, not just answer, before it gets real work. Any of them can be replaced without changing how MAIOS thinks.

ROLE≠TOOL≠MODEL

Independent acceptance

Nothing is done until the evidence says so.

Delivering a file isn’t finishing a job. MAIOS accepts work only when a verifier that didn’t build it confirms the exact result meets a bar that was set from your intent before work began. A model saying “done” counts for nothing.

  • Written before the work

    Acceptance comes from your intent and is fixed before anything is built. The builder can’t move the bar.

  • Checked by someone else

    A separate verifier judges the result. The author never approves its own work.

  • Bound to the exact result

    Evidence names precisely what was checked. Missing or contradictory evidence never counts as a pass.

  • DELIVERY≠ACCEPTANCE
  • AUTHOR≠APPROVER
  • EVIDENCE>OPINION

Recovery

Resume. Never rerun.

Processes crash and machines sleep. MAIOS continues an interrupted mission from where it stopped: the same attempt, not a fresh start. Nothing that already took effect happens twice.

Recorded drill · October 2026
  1. Mission under way worker acting
  2. Controller killed mid-turn
  3. Resumed same thread, same attempt
  4. Delivered once
  5. Independently verified
Intent
1
Dispatch
1
Duplicates
0
Recorded drill, October 2026: the controller was killed mid-turn. MAIOS recovered into the same thread and attempt with exactly one resume: one intent, one dispatch, no duplicates.
  • RESUME≠RERUNInterrupted work continues. It doesn’t start over.
  • UNKNOWN≠ABSENTNot seeing an effect doesn’t mean it didn’t happen.

Operator by exception

You’re the CEO. Not the courier.

MAIOS keeps you where your judgment matters and handles the rest. When it needs you, it doesn’t ask what to do. It brings a decision, prepared.

You decide direction, taste, budget, irreversible steps and the risk you’ll accept. MAIOS handles choosing workers, retries and repairs, handoffs, testing and recovery.

The measure that matters: human dependency per verified outcome.

Decision needed · M-0147Prepared by MAIOS

Two suppliers switched invoice currency mid-quarter. Which exchange rate defines a “mismatch”?

Why now
9 invoice lines change status depending on the answer.
Reversible
Fully. The report can be regenerated.
Cost of delay
The report waits. All other work continues.
If no answer
At 15:00 MAIOS proceeds with A and flags it in the report.

One business question, fully prepared. Pick an option to see what happens next.

Concept An illustrative decision request.

Proof, not promises

MAIOS built, verified and used its own first tool.

Its first mission was to build an evidence-intake audit tool, have it verified independently, then use it on MAIOS’s own source archive. These numbers come from that recorded run, October 2026.

Recorded run · October 2026

  • 507/507required independent verifier checks passed
  • 1·1·0intent · dispatch · duplicates, through a real mid-turn controller kill
  • 6/6source documents confirmed unchanged in actual use
  • 5Operator touches: the only human involvement in the entire run

Failures are kept too. The first run failed, and a later worker binding was refused, fail-closed. Both causes were fixed and the records preserved. Evidence outranks opinion. Including ours.

Chapter II · Logistics

Control Tower

Silence the normal. Surface the exception.

Phase 1 · simulated data
Plate II · From the world to the mapRead the chapter

Control Tower

AI logistics control tower Phase 1 · simulated data
Chapter II · Exception-first operations for international road freight

Every shipment gets a digital twin. Only the exceptions reach a human.

An exception-first operations layer for international road freight. It sits above the telematics, planning and messaging systems a fleet already runs, keeps one record per trip with the source and confidence of every status, and brings people only what needs them.

Stage
Phase 1. The operator interface now runs on simulated data. Nothing is deployed and no live data provider is connected.
People
The operations team. Sees the exceptions, not every truck.
System
The tower. A digital twin of every trip, each status with its evidence.
Workers
Existing systems, and AI. AI reads only free text, voice and photos.
Concept · the idea
A concept of the idea, not the product’s interface.

The problem

A truck’s status lives in three places at once.

A telematics feed that is sometimes stale, a plan that was right this morning, and a dispatcher’s memory of a phone call. Attention goes to the trucks that are fine. The one that isn’t gets noticed after the delivery slot, the ferry booking or the demurrage window has closed.

Guiding principle

“The goal isn’t more messages. It’s the right information with the fewest human and driver touches, with its source and confidence visible.”

What it is

  • A decision layer above existing systems of record
  • A digital twin per trip, with source and confidence on every status
  • An exception desk, not a dashboard
  • Button-first driver check-ins, not a chatbot
  • Arrival times you can explain line by line

What it deliberately isn’t

  • A telematics provider, or a rewrite of the planning system
  • A black-box model guessing arrival times
  • A system that commits to customers or invoices without human approval
  • A driver scoring or ranking engine

Built backend-first

Proven before a single screen depended on it.

The foundation came first and the operator interface came last, on purpose. Every work package passed independent review before it was accepted. One took five rounds. A documentation check failed the build whenever a document claimed more than the code delivered, so the project couldn’t quietly claim progress it hadn’t made.

Measured 21 September 2026

  • 2,342unit tests
  • 585integration tests against real infrastructure
  • 75mutation probes, and the suite fails if a single one survives
  • 38architecture decisions on record

What isn’t claimed. Nothing is deployed to production, no live data provider is connected and no pilot has started, so there are no field results here yet.

Chapter III · Media

Content Factory

Run the factory, not the tools.

In development
research write voice visuals edit check publish outlets
Plate III · The factoryRead the chapter

Content Factory

Local-first AI media production In development
Chapter III · Local-first, model-agnostic AI media production

AI can generate content. It still can’t run the factory by itself.

Research, writing, images, video, voice, editing, quality control and publishing usually live in separate tools, with a person as the glue. Content Factory is designed to run them as one local-first, model-agnostic system that calls its owner only when human authority is required.

Stage
In active development. The architecture and principles are set; the capabilities are being built and qualified.
People
The owner. Strategy, taste, capital and true exceptions.
System
The factory. State, provenance, quality gates and recovery.
Workers
Models, machines, media tools. Routed by capability, not brand.
Concept · evidence model

One claim, followed through a storyEvidence travels with everything built on it.

  1. SourceInspection report, p. 14Revised report, p. 14CurrentCorrected
  2. Claim“Cracks grew 2 mm a year”“Cracks grew 3 mm a year”SupportedRe-checkingSupported again
  3. Script beatBeat 7: the slow failureCurrentStaleRebuilt
  4. SceneDiagram of crack growthCurrentStaleRebuilt
  5. ProductsVideo, article and shortVerifiedPublishing heldVerified again
Long-form video · 16 scenesAll current1 scene stale1 rebuilt · 15 untouched

A concept of the evidence model, with illustrative data. Change one fact and only what depends on it is rebuilt, then checked again before anything ships.

Evidence

Content that can show its work.

Every factual claim is designed to carry its source. A claim without support doesn’t ship unless it is deliberately marked as editorial. Correcting a fact rebuilds only what depends on it.

Restraint

Explanation over spectacle.

Not every scene needs generative video. Real evidence, maps and diagrams come before generated footage.

The editorial test

“If removing a scene doesn’t reduce understanding, the scene may only be producing motion.”

Autonomy

Autonomy is earned, not declared.

Each class of task earns its autonomy separately. Nothing is declared autonomous all at once.

  1. Commissioning
  2. Calibrated
  3. Auto with veto
  4. Autonomous
  5. Exception only

The models will change. Build the system that survives them.

Get in touch

One address for all three systems.