Your rules, written down. And proof they’re followed.
The constitution holds your organization’s rules in one place. Every solution you install from the marketplace binds to it. Policy flows down to every agent, and evidence of every check flows back up into outcome assurance.
From conversation to enforced rule. And back again.
A constitution is discovered, adopted, bound, measured and amended. Every step leaves a record you can open later.
- 01
Discover
Interviews capture how your people work and where they disagree.
- 02
Outcomes
Contributors mark positions. Agreement and conflict show up per topic.
- 03
Articles
Settled outcomes are promoted to draft articles.
- 04
Adopt & ratify
The owner with authority for that scope ratifies.
- 05
Bind rules
Rules attach to the solutions and steps they govern.
- 06
Evidence
Every check is written to the evidence ledger.
- 07
Amend
Changes arrive as field-level diffs and go through the queue.
↺ Scars and run findings feed the next amendment
Discovered from your people
The discovery interview turns what people already do into topic outcomes. Conflicts are found before anything becomes a draft.
Started from a baseline
You begin with 43 platform articles across 10 pillars, plus the packs for where you operate and what you do.
Ratified by the right authority
Who can ratify depends on scope and class. A business unit’s board can own its rules while the floor stays company-wide.
Four parts. Plain language your auditors can read.
Each article states the principle, why it matters, what it means in practice and what evidence shows it was followed. Each one belongs to one of three classes.
Applies to everyone. Floors are accepted together and can’t be declined.
Your call. Adopt it, override it with a justification, or decline it with a rationale.
Who you are. Your mandate in your own words, the one thing a platform default can’t know.
Change control and segregation of duties
Changes to production shall be authorized, reviewed by someone other than their author, recorded, and reversible.
The author of a change must not be its only approver. Segregation of duties is the first control an auditor tests.
Every production change is approved by an identity other than its author, and has a recorded, tested rollback path.
The change record names a second approver and links the rollback test. A schema check confirms both.
Start from a baseline. Add the packs that fit you.
Packs add the articles for where you operate, your sector and each function.
Each rule says how far down it reaches.
A business unit inherits the company’s rules. The article decides how, in one of three modes.
Cascade
Applies below exactly as written.
Cascade, override allowed
Applies below unless the unit records its own version.
This level only
Applies where it is set and stops there.
Adopt in an afternoon. Stay current for years.
Articles are never edited in place. Every change goes through adoption, an amendment or the governance queue, and someone with authority signs it.
Pillar by pillar.
Floors are accepted together. Each posture is adopted, overridden with a justification, or declined with a rationale. The run can’t be completed while anything is blocking.
The adoption run for pillar 1 of 10, business alignment. Two articles are blocking the pillar. Both universal floors are accepted together. The first posture article is adopted, and the second is overridden with a justification. Nothing is left blocking, and the run moves on to pillar 2.
Every change, field by field.
When a platform article you adopted changes, you get a notice with a field-level diff. You accept or decline, with a rationale either way. Declining keeps your article exactly as it is.
Two amendment notices. A platform article you adopted, vendor diligence, has changed in two fields. The diff shows the old and new text for each field, a rationale is written, and the change is accepted. The second notice is declined, so that article is kept exactly as it is.
A constitution that learns.
Suggestions arrive from interviews, integrations and agent runs. A scar is real friction found in practice. The system may propose a scar, and a person must confirm it before it is admitted. Ratification is the final vote.
The governance queue in four lanes: suggestions, scars, admission gate and ratified. Three suggestions arrive, from an integration, a pull request check and a Fabric run. The system proposes the third as a scar, and Priya confirms it. It passes the admission gate and is ratified with three of three votes.
One register of every article.
Filter by origin, pillar, class and status. You see what is in force, what is still a proposal and what waits in the adoption run.
The article register, with each article’s origin, class and status. A filter keeps only the floors, then a second filter keeps only the articles in force.
Where your people agree, and where they don’t.
The matrix tracks every topic from discovery. Agreement, open work and conflict are counted per topic before anything is promoted.
The discovery matrix. Totals count up across 511 topics: 296 in agreement, 29 in progress and 127 in conflict. Five topics are listed with their contributors and outcomes, and vendor management is highlighted as a conflict.
Rules bound to the work. Ledgers that only grow.
When you install a solution, its rules bind to your articles at the steps they govern. Each binding is observed or enforced, and checked by the method that fits.
Checks run and land in the ledger. The work carries on, so you can see a rule’s effect before you enforce it.
A failing check holds the work until it passes or an exception is approved.
“Does the reply cite the clause it relies on?”/\bCPF\s?\d{3}\.\d{3}\.\d{3}-\d{2}\b/approver_id != author_id3 of 3 items completedAfter every agent run, Fabric screens the output against the articles that apply and stores each finding with the quoted excerpt.
Evidence ledger append-only
Records every check and the rule version that applied. Rows can be added and never changed, and the database enforces it.
Exceptions ledger approver ≠ requester
Records who excused a failure, why, and until when. The person who asks for an exception can never approve it.
Did it pass? And how sure are you?
Your objectives are weighted to the articles that serve them. Evidence from every installed solution rolls up into each objective, reported twice: as measured, and as assured.
What most tools report. Every pass counts, however shaky the judgment behind it.
Only passes that met the confidence your organization requires. You set the bar.
The part of green you shouldn’t rely on yet. Shown worst first, so you know where to look.
Four business objectives, each with an owner, a target date and a status. Evidence arrives from installed solutions. Vendor onboarding and SOC 2 readiness are active. Net revenue retention is at risk, because its assured score is under the bar. Sev-1 incidents have no evidence yet.
It tells you what’s missing. Five kinds of gap, found for you.
A passing score means little if the rules don’t cover the work. Celara checks the constitution itself and lists every gap it finds.
Unsupported objective
An objective no article serves.
Unbound jurisdiction
A place you operate with no rules attached.
Unaddressed scar
Friction found in practice that no article answers.
Aspirational article
A principle with no rule that checks it.
Decorative article
An article nothing depends on.
Start with the rules you already have.
They live in manuals, in policies and in people’s heads. In the first session we write them down, bind them to one solution and show you the evidence it produces.