Your company already has a constitution. You just never wrote it down.

Every company runs on a handful of operating beliefs. What "done" means. Who gets to make a decision and who doesn't. Whether something is checked before it goes out, or whether "looks good" is enough. Whether data wins in the end, or the loudest opinion in the room.

These beliefs already exist in your company. You've just never written them down. They live in your head, in no document, and that is exactly what makes them the opposite of reliable.

An unwritten rule is still a rule

As long as a belief lives only in your head, it moves with you. "Done" means one thing on Monday morning and another on Friday night. Who's in the room shapes what passes as a good decision. A new hire can't read what you never wrote, so they guess, and they often guess wrong.

This isn't a discipline problem or a people problem. It's a structural one. A rule that's written nowhere can't be learned, can't be checked, and can't be enforced. It's there, but it's invisible, and invisible rules are a little different in every head.

A rule that lives only in your head isn't a rule. It's a mood.

What separates a constitution from a poster

Most companies have something like written values. They hang on a wall, sit in the onboarding deck, and sound good. And they change nothing, because nothing happens when someone breaks them. A value no system checks is decoration.

A constitution is the opposite of decoration. It's a few sentences the system actually enforces. Three examples of how Rocket Routine OS writes them:

1. Processes are the problem, not people. When quality is off, you don't go looking for the person, you fix the process. That's not a kindness, it's the rule that governs how failures get analyzed.
2. Data beats opinions. A decision without evidence doesn't move, no matter who it comes from. An opinion can start the conversation; it doesn't replace the evidence.
3. Verification first. Nothing ships without quality confirmation. "Done" isn't a feeling, it's a check that passed.

The difference isn't in the wording, it's in the enforcement. A poster describes who you want to be. A constitution defines what the system won't let through.

A few rules that actually hold

A constitution isn't a forty-page handbook nobody reads. It's short, on purpose. Rocket Routine OS starts with a Constitution Lite: the few rules that count, and a clear map of who decides what.

The reason for the brevity isn't convenience. A long list nobody enforces is weaker than three sentences that always hold. Every rule you write down is a promise to enforce it. So write down only what you actually mean, and mean every sentence enough that the system can act on it.

Better three rules that always hold than forty that hang on a wall.

Company 0

When I wrote the first constitution for Rocket Routine, it fit on one page, five sentences. The hardest part wasn't the wording. It was realizing that the first rule to genuinely constrain anyone was one that constrained me.

The sentence was "data beats opinions." Soon after, I wanted to cut a content topic I simply didn't like. The numbers said otherwise; it was one of the strongest themes. Before, my gut would have won, because it's my company. Now the sentence was written down, and it applied to me too. The topic stayed.

That's the point where CEO sovereignty gets concrete. Sovereign doesn't mean standing above the rules. It means writing the rules and then binding yourself to them. A constitution that doesn't apply to the founder is just a poster again.

What comes next

Your company already has a constitution: unwritten, in your head, a little different every day. Rocket Routine OS makes it visible, a few operating beliefs like "processes are the problem, not people," "data beats opinions," and "verification first," written down as rules the system enforces, not sentences on a wall. The task isn't to have more rules. It's to finally write down the few that count, and mean them.

If you're running a founder-led B2B company with 15 to 50 employees and you want measurable execution control without writing a handbook nobody reads: rocket-routine.com