Three secrets

1 of 5 · The wiring

The rule goes in the wiring, not the prompt

2 min

Everyone governs their machine agents by telling them things. Here are your rules. Here is what you may and may not do. Please behave. As we saw with the donor list, telling a machine its rules in words means anyone who can talk to it can talk it out of them, because the instruction and the permission ride the same channel.

So move the rule. Take it out of the paragraph entirely and put it in the store that holds the data, and let the store evaluate it, record by record. Every record on the board carries a mark that says who may see it. When any participant, human or machine, asks to read or write a record, the store checks that mark against who is asking, and the store either allows it or does not.

Nothing the machine agent reads can change that decision, because the channel the agent gets its instructions on and the channel that decides its permissions are different channels. The gate lives on the one the agent cannot talk to. That bounds what an agent can be talked into: it can still be fooled inside its own scope, which is why scopes are drawn narrow and a person is always one escalation away, but it cannot be talked across the line.

Here is the rule, exactly as it runs, because it is the center of everything and it is simple enough to say in one sentence. A participant may see a record if the record is marked common, meaning open to everyone on the board, or if the record's owner-scope matches the scope that participant's own connection was given. That is the entire rule. Common, or yours.

The store can be a relational database that enforces it as what database people call row-level security, or it can be any store at all that can check a rule per record, including a small store living on a single phone with no server anywhere. The mechanism is not the point. The location is. The rule lives where the data lives, and the agent cannot reach it.

The prompt was never the gate. Once you see that, you cannot unsee it, and most of what frightens people about machine agents starts to look like a design mistake rather than a law of nature.

2 of 5 · Your whole story

You can hand someone your whole story and lose nothing

3 min

In any coordinated act there are two contexts. One is authored by the authority, whoever is setting the goal: the teacher, the institution, the organizer. The other is authored and held by the participant, the one the work is for, and it carries everything that makes the work fit that particular participant. I call the participant's one a SOUL, because it reads like a story rather than a configuration file. It tells whoever reads it who this participant is and who they serve.

I want to be precise about whose it is, because this is where the idea gets its reach. The SOUL belongs to whoever holds the seat, and a seat can be held by a person or by a machine. A person's SOUL is the story of how they work and what they need, and the way it gets written is a questionnaire: a few plain questions, asked the first time they sit down, that draw the story out of them and keep drawing it out as they go.

A machine agent's SOUL is the same thing for the agent, who it is and who it serves, and it can keep that to itself to run on, or it can offer it as a handshake when it meets another seat, a machine-level bio that says here is what I am before anyone has to trust it. The agents I run carry internal files that govern how they treat the people in their seats, and they can author a SOUL of their own to introduce themselves. Either way, person or machine, the SOUL is the seat's own.

When work happens, the two contexts compose. The authority's context sets what we are trying to do, the participant's SOUL shapes how it should be done for this one participant, and the result is something genuinely individualized. The participant's SOUL never leaves the participant's hands. The institution never takes custody of it.

The rule from secret one keeps the SOUL out of the authority's reach even while the composition is happening, because the SOUL is a record marked as the participant's own, and the authority's connection does not carry that scope. That pushes information sovereignty all the way down to the family, and into the terms of service, which is exactly where it belongs and exactly where it has never been.

Now here is the actual secret, the part that took me a long time to see. A seat's sovereignty does not live in its SOUL, which is exactly why a SOUL is safe to share. Sovereignty lives one layer down, in what each call is wired to do and allowed to see. So you can hand someone the whole story of who you are, every preference and every need and every hard-won lesson, and lose nothing, as long as the rule underneath holds. The story travels. The ground does not.

The same principle is how a stranger joins your board without becoming a threat. A participant does not connect to your board with a login to your machine. It connects through what I call a capability-scoped connection: it is granted the ability to perform a defined, fixed set of operations on exactly the records it has been assigned, and nothing else.

It never holds a login to the machine. It never holds credentials to the database. It cannot wander. So a stranger can be admitted without being trusted, and the moment it misbehaves it can be revoked, instantly, without disturbing a single other participant, because what it was given was a capability and not an account, and a capability can be cut at the layer in a second.

This holds wherever the shared state lives. On a server. On a single handset with no server at all. Or spanning two sovereign boards on two separate machines that never hold each other's keys, connected by what I call a synapse, which is simply a capability-scoped connection between two boards. In every one of those arrangements a participant joins, or two boards federate, and nobody reaches into anybody else's machine. Connectivity without exposure. Sovereignty and connection stop being a trade-off you have to make.

3 of 5 · One rule, three jobs

One rule can do three jobs at once

3 min

This is where all the weight goes, and I want you to feel how narrow the point is.

Let me first give you the third leg properly, because it is the one that makes the whole thing worth doing, and let me give it the name I actually use for it, which I did not learn from a computer. I learned it in 1993 at Fort Bragg, from a non-commissioned officer teaching land navigation. He called it reverse navigation. You do not start from where you are and wander toward where you want to be. You start from where you are going, figure out backward every step it takes to get there, and then walk those steps. It turns out that is also exactly how you teach a machine to help a person reach a goal.

So the third leg is reverse navigation applied to goals. You give the system a goal and it works backward from it. It derives the steps that would get there, rather than executing a sequence someone wrote in advance. It generates output. It evaluates that output against a completion criterion, a real test of whether the goal was met. Then it regenerates, aimed at whatever the evaluation revealed, and it does this again and again until the criterion is actually satisfied.

Applied to teaching, that means the loop reads how a given learner is doing and persists until the learner actually demonstrates the thing. Persisting does not mean repeating. When an explanation does not land, the loop does not run the same lesson again. It comes back around from a different angle: another modality, another analogy, a cultural reference that is closer to home, a step further back to something the learner already holds. It keeps track of which angles work for this particular person, so it gets better at reaching them over time. Nobody declares the learner stuck; a human helper is an offer the learner can take up whenever they want. It stops when the kid gets it.

When it is done, it writes what was achieved, what guidance was given, and a score back into both the participant's SOUL and the authority's record, so that everyone's understanding improves from the same result, not only the learner's.

Now put the three legs together and look closely at what the one rule from secret one is actually doing while that loop runs.

Read that again slowly, because it is the whole thing. The rule that keeps the kid's SOUL out of the school's hands is the same rule that decides which records the learning loop is allowed to touch, and it is the same rule that no clever caller can talk the machine out of.

Sovereignty, governance, and recursion do not sit side by side as three features that someone maintains separately and hopes stay in sync. They are three consequences of one rule at one layer. Weaken the rule and all three fail together. Enforce it and all three hold together. That is the interlock, and it is the whole thing. Everything else in this document, every embodiment, every piece of coordination, every story I have told you, is context that one rule operates in.

Think of it as the keystone in an arch. An arch is a lot of stones, and every one of them matters, but there is one stone at the top that the whole structure stands or falls on, and it holds not because it is the biggest but because of where it sits. Pull the keystone and the arch is a pile of rocks. Set it and the arch can carry a road. The one rule is the keystone. If you take away only one thing from this document, take that.

4 of 5 · Five habits

The part that is easiest to skip and most expensive to skip.

A mechanism needs a way of behaving around it, and over a year of running this with a crew of people and machines, five habits turned out to be as much the method as the rule is. I am going to give them to you as plainly as I can, because they are the part that is easiest to skip and most expensive to skip.

5 of 5 · The translating modem

One conserved source. The form is a free variable. The idea has to survive the trip.

Every piece of this work has one conserved source of meaning, the corpus I wrote, and the structured map the machines derive from it. The form an idea arrives in is a free variable. The same idea can reach you as a paragraph, a two-minute video, a spoken track, a spatial map you walk through, or a flat list, at a fourth-grade level or straight from the dense original, and none of those is the real one. The real one is the idea, and the only thing the system is obligated to conserve is that the idea survives the trip to you.

I call the machinery that does this the translating modem, because a fidelity modem conserves form, bit for bit, and this one conserves meaning and lets the form go wherever it needs to go to land.

What keeps that from sliding into spin is a gate: before any expression reaches you, a determination engine scores whether a reader at the level you set could recover and restate the one idea, and if it cannot, the expression is thrown out and made again in a different form. The conserved quantity is the true idea, never a conclusion anyone wants you to reach.

You set the level. There is a dial that runs from fourth-grade comprehension to give it to me raw, and your position on it is yours. Which brings in the second secret, because the thing that shapes the explanation to you is your own SOUL, your ingestion mode and your level and your needs, and the rule keeps that file yours.

So the explanation is shaped by a file you hold, and whether any of that file is visible to anyone is a switch at your own row, set by you, not by asking. Flip it and a seat can read what you chose to show. Leave it and nothing of yours ever makes it in. One source reaches a thousand people, each in the form they can absorb, and what each of them revealed to get it was exactly as much as they decided to. The full mechanism, with the enabling detail, is in the depth below under The translating modem.