Phase 1 — Foundation
Product Constitution
The rules that override everything else — including the AI
3 min read · Document 2 of 30
What is this document?
The Product Constitution is a numbered set of invariants: statements that are always true about your product, no matter what a later prompt, ticket or feature request says. Ownership of data, what the customer always controls, what the product never does.
Lower-level documents may refine the constitution but can never contradict it. That makes it the single place to look when two requirements appear to conflict.
Why does it matter?
- Without invariants, AI tools optimise locally and break globally.
- A constitution gives the AI a set of rules it cannot violate, no matter what an individual prompt says.
- Conflicts between documents resolve the same way every time.
What's inside?
- Articles — Numbered, testable rules — quality, ownership, privacy, fairness.
- Precedence — How the constitution ranks against requirements and implementation.
- Amendment process — Who may change an article and what must be updated with it.
ConstitutionRequirementsImplementation
How CREAH generates it
CREAH builds this document from your Stage 0 answers and interview. Questions that shape it include:
- What must always be true about customer data?
- Is there anything the product must never do, even if a paying customer asks?
- Who owns what the product produces?
Example excerpt
## Article 1 — Quality Over Speed
No document ships until its mandatory prerequisites are satisfied.
Generation speed is never a reason to produce an incomplete document.
## Article 3 — Customer Owns Everything
The customer holds full intellectual property rights to all
generated documents from the moment of download.