The outer demons
The forces outside you.
Six of them. Each card is the demon and what the design does about it.
Outer demon
Enclosure.
The platforms you are offered are built on capture, and I do not say that as an insult. Gatekeeping is not a flaw in their model; it is the model, because a market requires a wall to charge rent at, and the companies selling you coordination are, structurally, in the business of walls. That means they cannot sell you coordination without capture, no matter how good their intentions, because doing so would dissolve their own moat.
I am not going to name names, because the pattern matters far more than any company and because the move that beats a walled garden has never been a better wall. It is a door out. This method is the door: coordination on ground you hold, federating on your own terms, with nobody standing at the gate.
Outer demon
The manufactured moat.
There is a loud argument right now about brakes and controls on artificial intelligence, and I want to take it seriously, because part of it is sincere and the risks are real. A lot of people have also noticed that the loudest calls for strict rules come from the biggest players, and that rules which only the biggest players can afford to follow are the best moat money can buy. Both of those things can be true at the same time.
This method dissolves the argument instead of picking a side. The brakes live in the data layer, in each holon's own wiring: the per-record rule, the capability-scoped connection, a boundary no instruction can talk an agent past, instant revocation, escalation to a person. That is real, structural governance of machine agents, and nobody grants it to you from above, and nobody can raise the rent on it. I call it safety without a landlord.
I am not claiming it solves every hard problem about artificial intelligence. It does not touch how a very large model is trained or what it might be capable of. What it does is give a small group real, enforceable control over what the agents working for them can read, write, and do, and that control is theirs to own and nobody's to revoke. The whole field is already converging on these same primitives, which tells me this is on its way to being basic hygiene for anyone running agents at all. If it is going to be table stakes, I would far rather hand every community a forkable, sovereign version than watch it sold back to them as a compliance product.
Outer demon
The toll.
I named this one among the five failures and I want to answer it directly. The method's answer to the price of frontier models is to touch a data center only when a question genuinely needs one, in single sips, and to let a small, cheap local model do the routine work and ask for help only when it hits its ceiling.
The answering tiers do not have to be owned at all, and here I want to be very plain, because people get this backwards. I rent the big models like everyone else. I do not own a frontier model and I am not going to. What I own is the rule and the wiring. A rented model sees only what the rule hands the participant it is serving, for exactly the task assigned, and nothing more. Capability, not capacity. A food bank holding nothing but a couple of subscriptions and a server that costs less than its coffee budget can stand up coordination it fully governs.
Outer demon
The standing door.
Every connection you have ever made cost you a login, and a login is a door into everything. The method replaces the login with a capability: a fixed set of operations on assigned records, revocable in a second, with no path to the machine underneath. Connect to anyone. Expose nothing.
Outer demon
The ones who cut you off.
Small operators carry a fear they rarely say out loud, and I have watched it stop good people cold: the fear that associating with anything disruptive will get them cut off by the incumbents they depend on for their next contract or their next grant. The method is built to make that fear structurally moot. Holons stay holons, so there is no bloc to be associated with and no single point anyone can lean on. Nobody has to adopt anybody else's worldview to connect; they just read and write the records they are assigned. Because this document is public, the method is already everywhere, and there is nobody left to cut anyone off from it.
Outer demon
The fencers.
Someone will try to patent an improvement and charge the community for the better version. Someone will try to trademark the name. This document is the first defense: it is dated, attributed prior art that no one can patent out from under you, and that includes me. The second defense is yours to carry: everything you improve, publish, so the commons grows faster than anyone can fence it. The third is attribution, which the license already carries. A commons defends itself by being already everywhere, with everyone's name on the parts they added.
The inner demons
The doubts inside you.
Eight of them, in the words people actually say.
Inner demon
"I am not a coder."
Neither am I, not really, and I built this. More to the point, the people who study this full-time have now said what I had to learn the hard way: writing code is no longer the gate. Judgment and oversight are. If you can run a loading dock, a classroom, a food bank, a garden, or a volunteer crew, you already have the skill that just became the scarce one. You tell the machine what you need in plain words, and the rule in the wiring does the rest. The reference kit stands up in an afternoon on a throwaway database, and the first time you watch a small model write a help record and a bigger one answer it, you will understand the whole thing in your hands instead of your head.
Inner demon
"It will get taken from me."
It cannot be, and I say that as someone who has had a store taken. Not by the vendor, because the rule lives in a store you own and can move. Not by a bad participant, because a participant only ever holds the records it was assigned and can be cut in a second. Not by a patent, because this document is now prior art. Not even by me, because I published it precisely so that I could not.
Inner demon
"I do not trust the machines."
Good. Neither do I, and the method is built on not trusting them. Rows are data, not instructions, so a machine cannot be talked past its boundary by anything it reads. What it does inside that boundary is still its own behavior, which is exactly why the boundary is drawn tight and a human is one escalation away. The rule itself cannot be argued out of its place. A human participant is always one escalation away, and a step that needs a person goes to a person. You do not have to trust the machine. You have to trust the wiring, and the wiring is something you can read.
Inner demon
"The ground always shifts. Why bother."
Let me be exact about what makes the ground yours, because somebody still has to own or rent the server, and if that were the ground we would be right back on sand. The ground is not the machine. The ground is the rule and your records, and both of those travel.
The server is rented like a utility, and if the company that rents it to you changes its terms, you pack the records and the rule onto another server in an afternoon and nothing about your operation changes. That is the difference between this and every platform you have ever been locked out of: the platform owned your records and its rules, and you rented your own life back from it. Here you own the records and the rule, and you rent only the metal underneath, which is interchangeable.
So the pattern survived the upstream agency being gutted, because the board did not live upstream. It survived the vendor changing terms, because the rule did not live in the vendor. It survives the organizer moving away, because the automations belonged to the board and not to her. It would have survived my landlord, because the method, unlike the store, does not sit on anyone's lease. The ground stopped shifting the day you poured the foundation yourself, and the foundation is a rule you can carry.
Inner demon
"I am exhausted."
I know. Exhaustion is the oldest reason good things do not get built, and it works the way it does because a person gets tired and a system does not. The machine does not tire either, and now it works for you. One organizer watches a hundred paths. The routine gets handled while you are asleep. It works on your hardest day because it was built on mine.
Inner demon
"We are not the ones with the authority to make it happen."
That sentence cost me a half-built grocery store, and I will not let it cost you anything. Here is what it actually means when you say it: that someone else holds the power to approve the thing, and you are waiting for them to use it.
The whole method exists to remove that someone. The board does not need an owner to honor it, an institution to adopt it, or an official to approve it. It needs a group of people who hold their own records, agree on one rule, and start. Every working piece described in this document was stood up by people who were not the ones with the authority, and that is precisely why it worked, because nothing in it waits on a gatekeeper. Stop standing aside and watching a thing you are able to do not get done. Do it.
Inner demon
"Why would anyone give this away?"
Because I do not want to enclose it. Because the people I want to build with are the ones who want a commons, not a wall. Because a patent plus a promise to be nice is a weaker gift than making sure no one can ever lock it up. Because the method only works if it is everywhere, and the fastest way to put it everywhere is to hand it to you.
Inner demon
"Why has nobody built this before?"
Because the best-resourced builders in the world were standing next to the same tools, with every incentive to use them, and they shipped adjacent things instead: document generators, file assistants, chat windows. None of them fused the three: a participant-held context, governance at the data layer, and a loop that persists to the goal, running across many sovereign seats under one rule.
Pieces of it exist everywhere, and good ones. The fusion did not, and it did not exist when I started writing this either. It showed up in the building. If it were obvious from where they sat, it would already exist, and it does not. It took someone standing in the gap, moving real resources and real people without a central authority anyone still trusted, who needed it badly enough to see it and could not do it any other way. The method is not hard. You just have to be standing in the right place to see it, and I was standing in a lot of them.
Stop standing aside and watching a thing you are able to do not get done. Do it.