Pax Machina

Pax Machina · The big idea · by Marcus

Everyone in this century wants to sell me an “agent.” An agent that answers my email. An agent that books my travel. An agent that, I am told, will “handle everything.” In Rome we had a word for a man who promised to handle everything: a usurper.

I do something different. I send Envoys. It takes a little more skill to set up, I will not pretend otherwise. But after a few months, the difference is the difference between hiring a stranger for the afternoon and having a trusted governor in every province of your life.

First, what I mean by each

An agent, in the way most products use the word, is an AI you hand a task to: a chatbot with tools, a browser assistant, a cloud service that “does it for you.” You describe what you want, it goes off and tries. Whatever it learns about you usually lives inside the vendor’s system, if it is kept at all.

An Envoy is a Claude Code project dedicated to one part of your life. It is simply a folder on your own computer with:

• standing orders in a plain text file called CLAUDE.md: who you are, what this Envoy handles, and its rules;
• skills: step-by-step recipes it has learned for the jobs it does often;
• its working files and notes: the memory of everything it has done.

When you open Claude Code in that folder, Claude reads the standing orders and picks up exactly where it left off. Claude Code calls it a project. Being Roman and all, I call it an Envoy.

Bills-Envoy/
CLAUDE.md standing orders
.claude/skills/ recipes (audit-subscriptions, pay-day-checklist…)
subscriptions.md what it has learned
exports/ bank and card CSVs

Seven reasons Envoys win

1. You own the memory

An Envoy’s memory is plain text on your computer. You can open it, read it, correct it, back it up, or delete it. Nothing it knows about you is hidden in someone else’s database. If an agent “remembers” something wrong about you, good luck finding it. If an Envoy does, you edit one line.

2. Specialists beat generalists

A general-purpose agent has to guess what matters in every request. An Envoy only ever thinks about one province: your bills, your birthdays, your photographs. Its instructions, files and history are all about that one job, so it makes fewer mistakes and needs less explaining.

3. It gets better every week

Each time an Envoy does a job well, you can tell it: “Turn what you just did into a skill.” Next time it follows the recipe. My Bills Envoy now runs the monthly subscription check from one sentence. A one-off agent starts from zero every time.

4. You can see everything it did

Every change an Envoy makes is a file you can inspect: the list it built, the notes it kept, the plan it proposed. There is no black box. For anything involving money or family, that transparency is the whole point.

5. The rules are yours, written down

Guardrails live in the standing orders, in your words: “Never enter passwords. Stop before any payment or cancellation is final. Ask before deleting anything.” Claude Code also asks permission before risky actions. You are the emperor; the Envoy governs within the law you wrote.

6. Walls between provinces

Separate Envoys keep separate things separate. My work Envoys never see my personal finances, and my Birthdays Envoy has no business in my bank exports. One all-knowing agent with access to your whole life is a single point of failure. Several Envoys, each with only what it needs, is how Rome governed an empire without handing any one governor the treasury.

7. Envoys talk to each other, through a protocol you control

This is the technique I am proudest of, and the one most “agent” products cannot copy. My Envoys cooperate without any of them running in the background, and without one of them seeing everything. It is a few rules and one shared folder. I call it the Envoy Inbox.

• Reading is allowed, with walls. Any Envoy may read another Envoy’s standing orders and notes to find information, except a short list of private provinces (family, health, personal money) that work Envoys are never allowed to open.
• Asking is done in writing. To get another Envoy to do something, an Envoy drops a small request file in a shared inbox folder, in that Envoy’s own tray.
• Nothing happens behind my back. The receiving Envoy checks its tray every time I open it, tells me what is waiting, and acts only with my approval.
• Done means filed. When the job is finished, the request moves to a done folder and a short reply goes back to the sender’s tray.
• A tap on the shoulder. If the receiving Envoy happens to be open at that moment, the sender also sends it a one-line heads-up.
• Information flows one way. Work can send summaries and schedules to my personal Envoys; personal details never flow back to work.

A request looks like this:

_inbox/Birthdays-Envoy/2026-10-05-company-holiday-schedule.md

From: Company-Envoy
To: Birthdays-Envoy
Date: 2026-10-05
Priority: normal
Request: Add the office closure dates to the family holiday calendar.
Context: Office closed Dec 24 to Jan 1.
Reply to: _inbox/Company-Envoy/

Each Envoy learns the protocol from a short paragraph pasted into its standing orders. That paragraph, the folder layout and a skill that files and answers requests will be in our free download, which we are packaging now.

My Envoys

You may wonder how far this goes. I govern about twenty Envoys today. Some details stay private, as they should, but here is the shape of my empire:

• The Emperor’s Envoy: the one that oversees all the others. It keeps my goals, my calendar and the master list of ideas, and nothing on that list happens until I have approved it.
• The business Envoys: one for the company’s vision and quarterly goals, one each for finance, marketing, proposals and customer relationships, and two that look after the company’s cloud and email systems.
• Client Envoys: one per client engagement, so no client’s work ever mixes with another’s.
• The Birthdays and Holidays Envoy: family birthdays, gift lists, budgets and Christmas.
• The Car Debrief Envoy: after a meeting I talk to Claude on my phone while I drive home, and this Envoy turns the conversation into notes and to-dos for the right Envoys.
• The PC Envoy: keeps my computer healthy, cleans up space and watches backups.
• The Channel Envoy: produces Pax Machina, the very thing you are reading.
• And the Envoys still being recruited: photographs (all 1,846 years of them), bills and subscriptions, and family check-ins.

None of them is clever on its own. Together, with written orders and a protocol for talking to each other, they run an empire. I keep the vision.

Side by side

	Typical agent	Envoy
Where memory lives	Inside the vendor’s service, often invisible	Plain files on your computer
Working together	One agent does everything, or hidden hand-offs	Written requests between Envoys, approved by you
Scope	Anything you ask, one task at a time	One part of your life, in depth
Improves over time	Rarely; starts fresh	Yes: skills and notes accumulate
Rules	The product’s settings	Your own written standing orders
Privacy	One assistant sees everything you share	Each Envoy sees only its province
Setup effort	Minutes	An evening for the first one
Lock-in	Tied to that product	Plain text; take it anywhere

The honest trade-offs

I promised solid advice, not a sales pitch. Envoys cost you something:

• More skill up front. You need to install Claude Code, create folders and write (or let Claude draft) a CLAUDE.md. Our Start Here guide covers it; the first Envoy takes an evening.
• You stay in charge. Envoys propose and you approve. If you want something that runs your life without you, this is not it, and I would argue nothing should be.
• They work when you open them. An Envoy is not a robot running in the background all night. You open the folder, give the order, and it works while you watch or while you make tea.
• Usage costs. Heavy Envoys use more of your Claude plan. Light ones barely register.

When is a plain agent better? For a quick one-off question, or an always-on alert, a chat assistant or a simple automation is fine. Envoys are for the parts of your life that keep coming back: bills, family, photos, a car, a business, a hobby, a YouTube channel.

Build your first Envoy in an evening

1. Pick one province that keeps coming back. Bills and subscriptions is a great first one.
2. Create a folder for it and open Claude Code there.
3. Say: “You are my Bills Envoy. Interview me about how I handle bills, then write a CLAUDE.md with your standing orders and rules.”
4. Give it its first real job (our Episode 1 subscription audit (coming soon, with the video) is perfect).
5. When it does something well, say: “Turn that into a skill.”

Or skip the blank page: our free download (coming soon) will include a starter Envoy template with sensible rules already written.

I kept the vision. I sent out the Envoys. For the first time since I arrived in this century, I have peace. Pax Machina.

Pax Machina is not affiliated with or endorsed by Anthropic. Claude and Claude Code are Anthropic products. “Envoy” is our name for a way of organizing Claude Code projects, not an Anthropic product.