Messaging Framework

This document is the canonical messaging principles reference for Made Open. It defines how the project describes itself — in public copy, internal docs, and any future surface. It exists so that the messaging stays coherent as surfaces are added or rewritten, without every contributor having to re-derive the positioning from first principles.

Reference this document before touching public copy, vision docs, or any surface where Made Open describes what it is and why it exists.

1. The Thesis and the Wedge

Made Open is fundamentally a data ownership project. That is the permanent thesis and has been since the project began. It is the thing being argued for, the right being asserted, the substrate the whole system is built on.

AI assistants are the current wedge — the vivid, contemporary scenario that makes the importance of data ownership land with a 2026 audience. Assistants are talked about on the site because they are new, valuable, and easy to recognize as a place where data ownership suddenly matters a great deal. They are never the subject of the argument; they are the illustration of it.

The implication for all copy: data is the subject, always. Assistants appear as scenario, illustration, threat model, or example — never as the thing Made Open is "about."

2. The Layered Argument

Public-facing surfaces teach the reader in this order. The order is load-bearing and should not be inverted without a reason.

1. Hook (vivid, current): Your data is about to be enclosed again — by the assistants you are asking for.
2. Threat (cool, new): Without data ownership, your agency is taken, not just your privacy. Agency is who shapes the conditions under which you decide, act, delegate, and persist. Data ownership is the boundary around your agency.
3. Thesis (warm, permanent): Data ownership is a human right.
4. Architecture (cool): Made Open is a sovereign data platform — a user-owned substrate for anything that acts on your behalf.
5. Economy (hot): Own your data. Own your solutions. Own your resources. Hacking capitalism. Same rules, better competition.

The arc warms from cool (threat, principle) through warm (thesis, architecture) to hot (economy, CTA) over the course of a single reading. Deeper surfaces can live at one temperature throughout (see §6).

3. Self-Description

Canonical pair: "A sovereign data platform. A user-owned substrate for anything that acts on your behalf."

Use the pair at hero-level self-descriptions, first mentions on major pages, and anywhere the project is introducing itself. "Platform" alone is fine deeper in copy. "Substrate" alone is fine in architectural contexts. The pair is the reveal: the word most readers know does not fully capture what Made Open is, and "substrate" closes the gap.

4. Core Vocabulary

Five words do the heavy lifting across the site.

Supporting vocabulary (retained): sovereignty (inside the phrase "data sovereignty" only — not as a blanket prefix), the People, hacking capitalism, Made Open economy, rules, memory, identity.

Retired: "plantation," "slave mentality," and the colonial framing as Todd's own metaphor. The Wikipedia quote about colonisation in the Manifesto is a framed historical quote and may stay. Any section or paragraph whose identity depends on plantation or slave-mentality imagery must be reworked, not softened in place.

Internal-technical only (never in public marketing copy): principal, policy authority, action authority, exploit path. These are threat-modeling terms. Public copy translates them: "you stay in charge of what runs on your behalf."

Stop stamping "sovereign" as a prefix. "Sovereign identity" survives because it is a term of art (self-sovereign identity, DIDs). "Sovereign platform," "sovereign marketplace," "sovereign governance," "sovereign economy" retire. Replace with "user-owned" or drop the adjective entirely.

5. Structural Implications

These are the structural consequences of the framework. They are what a copy edit pass cannot achieve on its own.

Three Pillars become Foundation + Outcomes

The current homepage presents three pillars as peers: Sovereign Software Platform, Sovereign Marketplace, Sovereign Governance. The substrate framing makes an honest correction: Pillar 1 is the foundation; Pillars 2 and 3 are built on it.

• The Foundation (the substrate): your data, your communications, your memory, your rules, your identity, your sandbox. What used to be called "Sovereign Software Platform." It is the floor.
• What it makes possible: a Made Open economy (was Marketplace), self-governing communities (was Governance), and assistants operating within your boundaries (new — and this is where the DEFCON wedge enters the homepage without becoming its subject).

Three outcomes on one foundation. This drops three "Sovereign" prefixes, restores architectural honesty, and gives the AI/assistant dimension a home without making it the thesis.

Temporal Planes is repositioned

Temporal Planes (past / present / future data) stays as a component, but its framing changes. Old framing: "data across time enables intelligence." New framing: "platforms took your past. They captured your present with attention. They are now competing to shape your future. Data ownership is how you stop the pattern." Temporal Planes becomes the bridge between Problem (extraction) and Scenario (assistants).

New section: The Principle

A new short section appears between Temporal Planes and the Architecture section. One screen, two or three sentences. The pivot the site turns on:

Privacy asks who can see your data. Agency asks who can shape the conditions under which you decide and act. Data ownership is the boundary around your agency.

This is the teaching moment. The reader arrives at the Foundation + Outcomes section with a sharpened vocabulary.

The Problem section expands to two faces

The current Problem section stops at extraction of the past. The revised section shows the problem has two faces: past extraction (what already happened — surveillance, attention markets) and future agency capture (what is coming — assistant-centric architectures that own your memory, identity, rules, and action authority). Same root cause. The plantation metaphor retires from this section; the extraction narrative stays, cooled.

Homepage section order

1. Hero
2. Problem — two faces
3. Manifesto Band
4. Temporal Planes
5. The Principle (new)
6. Foundation + Outcomes (was Three Pillars)
7. The Proof
8. Their Way / Our Way
9. Adoption Roadmap
10. Final CTA

Every existing component stays. One new section is added. Pillars restructure. The narrative gains a bridge (Temporal Planes in its new role) and a pivot (The Principle).

Hero headline stays; body and pills change

"We are building solutions." stays as the hero headline. It is the movement voice and it earns its place. The body paragraph and the three pills underneath are rewritten to introduce agency, substrate, and the expanded problem. The existing fourth-phrase pattern — "Own your data. Own your solutions. Own your resources." — may extend to a fourth, "Own your future." Do not tack on "Own your agency" as a parallel noun; agency is the explanation of why you own your future, not a thing to own.

6. Register Map

7. Drafting Rules

1. Data is the subject; assistants are never the subject. "Made Open protects your data and your agency from platforms that would enclose them" — not "Made Open is a safe way to use AI assistants."
2. Pair "platform" and "substrate" at hero-level self-descriptions. Either alone is fine deeper in copy.
3. Prefer "agency" over "privacy" when the argument is about control of future action. Privacy is still correct when the argument is specifically about disclosure.
4. Retire "plantation" and "slave mentality." Any paragraph that depends on them must be reworked, not softened in place. The Wikipedia colonisation quote is framed historical material and may stay.
5. Stop stamping "sovereign" as a prefix. "Sovereign identity" survives. "Sovereign platform / marketplace / governance / economy" retire.
6. "Principal" stays internal. Public copy: "You stay in charge of what runs on your behalf."
7. "Boundary" is weight-bearing vocabulary. Used sparingly, at moments that matter.
8. The pedagogical order is load-bearing: vivid scenario → principle → thesis → architecture → economy.
9. On cool surfaces, let architecture do the arguing. Do not reach for political heat to make a point the architecture has already made.
10. On the Manifesto, do not cool the voice with technical register. Movement voice earns its place there.
11. "Hacking capitalism" is campaign text. Closers, CTAs, rallying moments — not inside technical arguments.
12. Three-phrase formulas keep working. "Own your data. Own your solutions. Own your resources." May extend to a fourth ("Own your future."). Do not tack on "Own your agency" as a parallel noun.

8. Application Plan

The framework above is applied to existing surfaces across a series of cascading sessions. The rough sequence:

1. Framework doc (this document) — written and approved.
2. Highest-leverage public surfaces — homepage body, pills, and new Principle section; Manifesto retirements and replacement paragraphs; Problem section expansion.
3. Secondary public surfaces — About, Features, Architecture, Explore pages, Community.
4. Internal vision docs — docs/01-vision/* brought in line with the new vocabulary.
5. Internal architecture docs — targeted vocabulary updates in docs/02-architecture/* where "sovereign" prefix or old framing appears.
6. Utilitarian surfaces — docs/05-guides/*, help, setup, download. Minimal or no change.

Each session references this document as its source of truth. Any change to positioning is made here first and cascades out; no session modifies the framework by side effect.

9. What This Framework Is Not

It is not a vocabulary replacement. The word "substrate" should not appear everywhere; the word "agency" should not replace every instance of "privacy." The framework is a mental model and a hierarchy of words. Most sentences on the site should sound like they were written by someone who had internalized the framework — not by someone running find-and-replace against it.

If a surface already reads well and the reader lands on the right principle, the framework has done its work. Do not add vocabulary for its own sake.