Log in

Project management for agents

Exos

Everything your project receives, captured into one record agents can navigate, and turned into shipped, verified work with a person at every gate.

See how the Studio ships Talk to us

How it works

A record that fills itself, and a process with a person at every gate.

  1. 01 The capture

    Everything the project receives lands in one record.

    Mail threads with their attachments, meetings with their transcripts, chats with their voice notes transcribed: a worker matches what arrives to the project’s contacts and files it, deterministically, into the project’s own repository as typed documents. No model touches the capture, so nothing is invented on the way in.

  2. 02 The record

    Plain files, in a repository that is yours.

    The record is markdown in git: meetings, threads, contracts, decisions, specs, sessions, and a wiki distilled from them with every claim linked to its source. Agents navigate plain documents extraordinarily well, so the record needs no database around it, and any tool can read it. You can leave with all of it.

  3. 03 The gate

    Agents propose. A person decides.

    The knowledge loop runs in cycles: an agent reads everything a cycle brought, checks every ask against the code, and renders one page. Nothing becomes a task, and nothing ships, until a person says go. Tasks are only ever touched through the rail, and closing one requires the pointer to what was delivered.

  4. 04 The delivery

    One lane builds. An adversary verifies. You merge.

    A lane is one agent session on a few tasks, with an independent verifier whose only job is to break the work before a human’s merge gate. A wave runs several lanes in parallel under one coordinator. What the client receives is a page in their language: what you told us, what changed, what to test, played and screenshotted before it is sent.

The whole machine

Everything a project receives, on one side. Everything it ships, on the other.

Between the two sits the record, and one gate a person holds. Nothing crosses it without a name on the decision, and everything that happens after comes back into the record.

Arriving Mail Meetings Chats Documents The record The gate Delivered Lane Lane Lane Everything that happens comes back to the record

What it does

The machine, piece by piece.

  • What comes in

    The arriving half of a project, filed without a model in the way.

    • The capture Gmail, meeting notes and WhatsApp, matched on the project’s contacts, landed as typed files with attachments and transcripts, one pull request per sync.
    • The record Eighteen kinds of document in one repository per project, linted, with a schema-governed wiki maintained off-cycle.
    • The board A standing dashboard per project: the shaped plan, and the state derived from the record and the rail.

  • What a person decides

    Every gate has a name on it, and no state moves without one.

    • Cycles and the gate One page per cycle, every claim verified against the code, one human go that creates the tasks and merges the capture as one event.
    • The task rail Tasks live in Linear and are only touched through the CLI: the description is the brief, and Done demands a delivery pointer.
    • Accountability A named person behind every call, an audit trail, and the closer stamped on every task.

  • What goes out

    The work itself, and the page the client opens at the end of it.

    • Workstreams The unit of work across agent sessions: a brief, a narrative, demo data, an event stream, rendered as one page anyone can open.
    • Lanes and waves Solo or parallel delivery with an independent verifier and a human merge gate, each lane in its own worktree and port band.
    • Client demos A page in the client’s words with expiring links, played by a browser and screenshotted, published through Slideless, mailed as a draft a person sends.

Who it is for

Studio clients

Every engagement runs on it

From day one your project has a record, and every mail, meeting and decision is in it, current, with a person at every gate. When we hand over, you keep all of it.

The Studio itself

The same process on every project

An agent loads a full project picture in seconds; the rail, the workstreams and the lanes are the same everywhere. Exos records its own build in its own record.

Other studios

Not yet, and honestly so

Today Exos is run by us, for the projects we deliver. The design is fork-and-own, one installation per company, and we will say so here when it is ready for yours.

Where it came from

What Exos is, and who it is for.

Strip any project to its essentials and two things remain: information arriving, and people acting on it. Mails, calls, messages, meetings, documents passed from hand to hand. Software has always tracked the acting half; the arriving half still scatters across inboxes and memories.

Exos starts there. It captures what a project receives into a record agents can navigate, and turns what has to happen into tasks agents can actually take, with a person deciding at every gate.

We built it for ourselves. Our Studio delivers every client project on it, which means it is tested the only way we trust: by depending on it, daily. Today we point it at software delivery, but the machinery does not care what the project makes.

If running projects is your work, Exos was built for the version of you that works with agents.

A photogram of a bundle of letters, a folded map, punched tape and cards, toned plum-grey.
The photogram What a project receives, laid on the paper.

Where to go next

See it at work, on a project of yours.

Send a message

Your name, email address and message are stored so we can answer you, are used for nothing else, and are deleted automatically after 90 days. What happens to your message