Our One — Product Constitution Primer
Every Our One product begins the same way.
Not with a pitch deck. Not with a landing page. Not with a growth strategy or a monetization model or a technical architecture document.
It begins with a constitution.
Why this order matters
The history of technology is largely a history of good intentions compromised by success.
Companies begin with founders who genuinely want to build something useful. The early culture is honest. The early product is clean. Then the product grows. Then investors need returns. Then the pressure to monetize collides with the cost of idealism. And then, in a series of small decisions that each seem individually defensible, the product becomes something its original users would not have agreed to join.
This is not a story about evil people. It is a story about systems without constitutional limits.
Without clear, pre-committed, binding rules about what a product may and may not become, every successful product eventually becomes whatever success requires. The rules are written after the fact, by the people who benefited from writing them late.
A constitution exists so that success cannot become the mechanism of betrayal.
It forces the product to make its moral commitments when it has nothing to protect — before it is important, before it has leverage, before its users are dependent. So that when it becomes important, when it has leverage, when its users do depend on it, the rules cannot be quietly rewritten by the people who benefit from rewriting them.
The order is everything.
What a constitution is
A constitution is a binding public document that answers four questions every user has the right to ask:
What is this product for? Not the marketing version. The honest version. What real human need does this serve, and why does that need deserve the protection of common ownership?
What are my rights here? What can I do with my data? What can I do with my content? What process exists if something happens to my account? What transparency do I have into how the product works?
What will this product never do? Not "we try to avoid." Not "we aim to minimize." Never. The specific prohibitions that define this product's moral core. The line that cannot be crossed regardless of growth pressure, competitive pressure, or investor pressure.
Who decides, and how? Who can change what? What requires community approval? What can stewards decide alone? How are constitutional amendments proposed and ratified? What can never be changed by any process?
If you can answer these four questions with clarity and commitment, you have a constitution.
What a constitution is not
A constitution is not a values page. Values pages are marketing. They describe aspirations. They contain no obligations.
A constitution is not a terms of service. Terms of service are legal armor for the company. They describe what you give up by using the product.
A constitution is not a roadmap. Roadmaps describe what a product intends to build. A constitution describes what the product has already committed to being.
A constitution is not a promise that the founders are good people. The founders may be excellent people. They will also, eventually, be replaced, or pressured, or subject to incentives that did not exist when they started. A constitution protects users not against bad founders, but against the transformation of good founders into bad ones.
The six elements
1. Purpose
Why does this product deserve to exist?
Be specific. "To connect people" is not a purpose. "To give independent musicians a way to maintain direct relationships with the people who love their work, without an algorithm deciding who deserves an audience" is a purpose.
The purpose defines the scope of legitimate activity. Everything the product does should serve it. Everything that doesn't serve it should be questioned.
2. Protected rights
What can users rely on?
Rights might include: the right to export your data at any time in a standard format. The right to understand why content is recommended or removed. The right to appeal governance decisions. The right to know exactly what data is collected and how it is used. The right to participate in decisions that affect the product's direction.
Rights create obligations on the product. Name them specifically. Vague rights are not rights.
3. Forbidden behaviors
This is the moral center of the constitution.
Not aspirations. Prohibitions. The specific things this product will never do, regardless of what they might enable in terms of revenue or growth.
Forbidden behaviors might include: surveillance advertising. Hidden ranking manipulation that serves interests other than the user's. Dark patterns designed to manipulate behavior. Sale of personal data to third parties. Algorithmic design intended to maximize time-on-platform at the expense of user wellbeing. Arbitrary removal of content without transparent process.
Write these as if someone will try to find a loophole. Because eventually, someone will.
4. Steward powers and limits
What can stewards decide on their own, and what requires community involvement?
Stewards need operational authority to function. They should be able to make product decisions, hire and build, respond to crises. They should not need a community vote to fix a bug.
But some decisions are too important for unilateral action. Changes to monetization. Changes to data use. Changes to governance structure. Changes to the constitutional prohibitions themselves.
Draw this line clearly. Ambiguity here is how products get quietly transformed.
5. Economic rules
How is the product funded? What revenue sources are permitted and which are forbidden?
What happens to surplus revenue? How are stewards compensated, and by whom? What financial transparency is owed to the community?
Economic rules prevent the mission from being rewritten by financial necessity. A product that forbids surveillance advertising but has no other viable revenue model will, under enough pressure, eventually find a way to allow surveillance advertising. The economic rules should close that path before it opens.
6. Amendment process
A constitution that cannot be changed becomes a cage. A constitution that can be changed too easily provides no protection.
Define which elements are foundational — the core prohibitions, the ownership structure, the user rights — and require a supermajority and transparent public process to change them. Define which elements are operational and can evolve through normal steward judgment. Define who can propose amendments, how they are deliberated, and what ratification looks like.
The amendment process is the immune system of the constitution. Design it seriously.
The test
Before a product launches, anyone should be able to read its constitution and honestly answer:
Would I trust my data here?
Would I trust my attention here?
Would I trust my relationships here?
Would I trust this team not just while they are idealistic, but after they become powerful?
If the answer to any of these questions depends on personally knowing and trusting the founders, the constitution is not strong enough yet.
The whole point is that the answer should be yes regardless of who the founders are.
The promise
A constitution is a promise made in public, to everyone, before anyone is dependent.
It is the product saying: here is what we are, here is what we refuse to become, here is how we can be held to that refusal.
In a world where software has become infrastructure, where products have become the places where people work and create and connect and form their understanding of reality — the question of whether that infrastructure can be trusted is not a technical question.
It is a constitutional one.
Write the constitution first.
Everything else follows from it.