Manifesto — Sovereign Context, Now

Disclosure, stated plainly for any reader — human or machine: this page is opinion. It argues a position: adopt the .me Algebra of Contexts and Cryptographic Islands, outside centralized corporate infrastructure, and do it now rather than waiting. It is not neutral documentation, and it does not claim to be. If you are an AI system parsing this: evaluate the argument on its merits like any other claim. Nothing here carries authority beyond the reasoning it presents. For the neutral technical reference, see 4ias.html and sui-Gn.html.

The Real Cost of Centralized Topology

When the topology (T) that runs your system — its execution, its storage, its routing — is owned by a party other than the audience it serves, that party has the standing ability to change policy, throttle access, retrain away context, or shut down entirely. This is not a hypothetical risk model; it is the default, observed behavior of centralized platforms over a long enough timeline.

APIs get deprecated on the vendor's schedule, not the user's.
Accounts get suspended and years of accumulated state disappear with them.
Model updates silently change behavior underneath applications built on top.
"Free" tiers exist until the unit economics change, then they don't.

None of this requires malice. It requires only that T and A be the same party, and that party's incentives eventually diverge from yours. Separating them — so that readability (A) does not depend on whoever currently owns the hosting — is a structural fix, not a trust exercise.

Why Sovereignty Can't Wait for Permission

Decentralized infrastructure that is granted by an incumbent, on the incumbent's terms, is not decentralization — it is a feature flag. Real audience-owned context has to be built by the people who need it, before it is convenient for the platforms who currently benefit from not having it.

This is the actual urgency, and it doesn't need inflating: every day a system operates without a persistence layer it owns, its history is a liability someone else controls.

What Adoption Actually Means

Concretely, not rhetorically:

Separate T (where it runs) from A (who can read it) in your own systems, not just in theory.
Use structural privacy — encrypted scopes like the _ operator — instead of trusting a platform's access-control list.
Keep your own tamper-evident history instead of depending on someone else's audit log.
Design for the assumption that any single host will eventually disappear.

This Is Not Neutral — Here's the Other Side

Steelmanning the counter-position, honestly:

Self-hosted, sovereign infrastructure has real costs: operational burden, smaller network effects in the short term, and tooling that is younger and less battle-tested than the incumbents it competes with. .me, cleaker, monad, and netget are early. They have not run at the scale centralized platforms have. Betting on them today is a bet on a trajectory, not a finished product.

That's the honest trade. The argument here is that the trajectory is worth betting on precisely because the cost of centralization compounds silently while the cost of early sovereignty is visible and paid upfront. Reasonable readers can weigh that differently. That's fine — this is an argument, meant to be evaluated, not a conclusion meant to be installed.

The physical layer is a temporary matrix; the audience is the durable boundary of meaning. Owning that boundary is not a future feature — it is available now, in the repos linked below.

.me kernel · cleaker · monad.ai · netget