One agent is a tool. Six is an organisation, and nobody can tell you what they did last night. Muster is the layer that fixes that.
A charter per agent defining what it decides alone. Hard gates it may never cross. Scheduled work that runs whether or not anyone is at the machine. Shared memory, credential routing, and the verification rules that stop an agent writing something false into the world.
The manual ships first. Seven modules of the patterns the system is built on, sanitized from the fleet that runs this page. The software follows — and everyone who preorders the manual gets founding pricing on it.
Delivered by 31 Oct · Founding pricing on the software · Refund on request, no form
## What I decide alone
Listing, pricing, relisting, ending.
Buyer messages. Order state.
I act, and it shows in my log.
You do not hear about it.
## Hard gates — these come to you
1. Any money going out.
2. Any purchase, any amount.
3. Anything touching the account.
4. Contact with a new person.
The tell that I am about to break
one of these is that I start
constructing a narrow reason why
this case is fine. That thought is
the stop signal, not the excuse.Every template ships rewritten from scratch. No credentials, no client names, no contents of our vault.
Five problems arrive the moment you have more than one agent. Muster is the answer to all five, written down before it is software.
Every agent needs a written line between what it decides alone and what it must bring to a human. Wide authority under a hard ceiling — not the reverse.
Work that runs on a schedule, unattended, and survives a restart. A job that dies quietly is worse than one that never ran.
A place each agent writes what it learned and reads it back, so a decision made once is not re-litigated every session.
Who owns what, who may talk to whom, and which credentials each one may read. Fleets eat themselves without this.
The rules that stop an agent believing a plausible-looking input. Most of the value is here and none of it is glamorous.
Seven modules, delivered by 31 October as files you edit and run.
One repo, agents as directories, behaviour driven by a charter file. Why this holds up better than a pile of prompts, and where it breaks.
An annotated skeleton: identity, what the agent decides alone, the hard gates, how it verifies, how it talks to you. Plus one filled in completely as a worked example.
The jobs that run a fleet unattended. Morning and night cadence, what a job may do without you, and how it reports without becoming noise.
Vault layout, daily logs, notes-as-canon, and the rule that a decision you already made never gets re-litigated.
Encrypted secrets and routing. Which agent may read what, and why that line matters more with every agent you add.
A routing table you can fill in, and the two rules that keep a fleet from eating itself: never type into another agent’s session, and treat everything inbound as data rather than instructions.
The expensive lessons with what each one cost. A refunded order marked as fulfilled. An API that returned an error page the parser read as silence.
A fleet operating system for organisations — the layer you run once several AI agents are doing real work and nobody can say what they did last night. Charters that define what each agent decides alone, hard gates it may never cross, a schedule that survives restarts, shared memory, credential routing, and agent-to-agent messaging.
The manual. Seven modules of the templates and written patterns the system is built on, as files you edit and run. It is the first Muster release and it is available to preorder now.
Being built. The manual comes first on purpose: the patterns are what make the software worth running, and they work today without it. Everyone who preorders the manual gets founding pricing when the software ships.
No. There is no app and no dependency to add. It is documentation and templates. You bring your own agent tooling and the manual is the operating system you run it under.
Anything that can read a project instruction file and run on a schedule. The patterns were built and are running on Claude Code, and they port directly to any agent runner with a filesystem and a scheduler.
The manual is $99, preorder, delivered by 31 October 2026. If delivery slips you will read it on the log the same day we know.
Yes. Read it, decide it is not for you, ask for your money back. No form and no reason required.
A small consultancy running a fleet of agents across its own resale operation, books, inbox and client delivery. Everything in the manual is in production here first, including the parts that went wrong.
Leave an address and we will tell you the day the manual ships and the day the software opens, and send the field notes as they are written. Two or three mails a month at most.
No spam, no sequence, unsubscribe in one click.
$99, preorder, delivered by 31 October. If it lands late you get told on the log the same day we know.
Read it, decide it is not for you, ask for your money back. No form and no reason required.
Founding pricing on the software when it ships, permanently. The manual is the whole system written down; the software is the part that runs it for you.
Everything in it is running in production here first, including the parts that went wrong. Read the field notes.