Seven moves
The only sensible thing to do with this document.
Fork it, author your story, build the legs where you are, point it at your gap, run the culture, keep it open, come find me.
Fork the kit.
The reference implementation of the governance leg is published under Apache 2.0 at github.com/Techniq42/fls-membrane, and I describe it in the next section: a database schema with the per-record rule built in, a capability-scoped connection layer, and the escalation lane. It runs on a server you can rent for the price of a sandwich a month. Stand it up on a throwaway database first. Watch a small model write a help record and a bigger one answer it. Then you will know.
Author your SOUL.
Write the narrative context that tells any agent who you are and who you serve, or let the questionnaire draw it out of you: an AI interviews you until it knows you specifically enough to write the file. A working version of that interview is published at shannondobbs.com/regenerative-gem. Keep it on your own device or your own account. Share it freely, because your sovereignty does not live in it. It lives in the rule underneath. It also holds your dial: how you want things explained to you, from plain to raw, and nobody has to know where you set it.
Build the other two legs where you are.
The reverse-navigation loop and the sovereign composition are described in this document in full. I have not built them into the public kit yet, and I am not going to tell you to wait for me. The description is the enablement. If you build them first, good. Tell me how it went.
Point it at your own gap.
Yours is not mine. Maybe it is a food bank and a loading dock. Maybe it is a classroom. Maybe it is a town's waste stream and a soil amendment nobody is making. Maybe it is a store on a corner that a neighborhood needs. The pattern is the same. The pieces already exist around you. Build the board that lets them see each other.
Run the culture, not just the code.
Stand it up yourselves, on the most solid ground you can reach, without waiting on anyone's authority. Rows are data, not instructions. Seats ask, they do not task. A no, or no answer at all, re-opens the door. Nobody holds anybody's keys. Those five habits are the reason it is safe to let the machines in, and the reason you never have to ask permission to.
Keep it open.
Everything you improve, publish. That is how a commons defends itself.
The same rule applies to me. Anything I improve about this method, I will publish here under the same license, so it joins the commons the same way this did. That is just the method applied to its author.
Come find me at the fire.
There is one lit at the gathering every fall, and one lit most nights at gather.livingsys.org, and at either one I would rather talk about what you are building than about any of this.
It is yours.