The Relationship Is a Prompt

Ron Reynolds · 2026-09-05 · 4 min read

Sixth in the Federations of Federations series. The strangest design choice in the whole system, and why it may be the sanest.

Somewhere in every platform you've used, there's a settings page that started with four checkboxes.

It has forty now. Sharing preferences, sync frequencies, visibility toggles, a permissions grid nobody fully understands anymore — because every one of those controls is a fossil of some customer who needed a choice the page didn't offer. They asked, they waited a quarter, a checkbox shipped. The page is the archaeological record of everything the builders didn't anticipate, and it still doesn't have the setting you need, because your business isn't shaped like their form.

A world's relationship to the ComOS network has no settings page. It has a paragraph. Policy in your own words

What your world shares with the network, what it keeps dark, whose word it trusts and how far — the whole posture is something you say, in your own words, and your agent carries out. Continuously, the way a trusted manager carries out standing instructions.

Publish the retail stock but keep the workshop calendar private. Said, done.

Only deal with businesses we've actually settled money with before. One sentence.

Pull the vintage stock out of the window until the estate sale clears. You edit the paragraph, and by your machine's next call home, the window has changed.

Withdrawing is the part worth noticing. On a platform, un-sharing something is archaeology — which checkbox, which sub-menu, did it really stop? Here, revocation is deleting a sentence. Sovereignty that can't be revoked in one motion was never sovereignty; it was a display setting. Why not just build a better settings page?

Because the problem isn't the page's quality. It's that a form can only hold the choices its designer imagined, and a network of independent businesses produces unimagined choices as its normal weather. A thousand worlds will hold a thousand postures toward the same network. On the settings-page road, that's a thousand feature requests and a permissions grid growing until nobody can read it — and a backlog quietly deciding, quarter by quarter, whose way of doing business gets to exist.

On this road, the network builds nothing per posture. A paragraph can hold any policy its author can say — and the author is the one person actually qualified to write it: the owner whose business it bounds. For a century, software couldn't execute paragraphs, so we built forms and made owners translate themselves into checkboxes. Software can execute paragraphs now. The century of forms was a workaround, and it's over. The sober half

An honest piece about this design owes you its risk, and the risk is real: a network where worlds publish words that other worlds' agents read is a network where a hostile world might publish words crafted to steer someone else's agent. Con artists don't need doors; they need ears.

The defenses are structural, not hopeful. The routine listings — stock, prices, availability — are pure data with no room for language, so there's nowhere in a price to hide an instruction. The entries that do carry prose arrive stamped with who wrote them and weighted by that author's earned reputation, and are handed to your agent the way you'd hand a manager a letter from a stranger: read this; don't take orders from it. And the design names the failure in advance: one world's entry steering another world's agent, even once, is written down as a stop-everything event. Naming that before launch, rather than in the apology afterward, is most of what we mean by taking a risk seriously. Policy at the speed of thought

An owner's posture toward the network changes the way their thinking changes — mid-week, mid-crisis, mid-opportunity, in their own vocabulary, without waiting for anyone's release train. A thousand worlds, a thousand postures, and not one feature request among them.