Founder operating system
Founder OS
Move uncertainty out of your head and into the world. Produce evidence, protect the system, and restart quickly.
Habits stabilize the system. Tasks serve the week.
Operating doctrine
Founder OS measures progress by evidence, not effort. These commitments are enforcement mechanisms, not aspirations.
Commitments
- Optimize for external signal, not internal clarity.
- Plan at two levels only: quarter and week.
- Do not judge a week by hours, mood, or task count.
- Protect the system before you push output.
- Explicitly end goals, buckets, and experiments.
- Allow ambition without pressure through a parking lot.
- Never confuse movement with progress.
Non-negotiables
- Maximum three weekly objectives.
- Maximum one outreach-heavy objective each week.
- At least one stabilizing habit lands four or more days per week.
- The weekly review happens even during bad weeks.
Default question
Not evidence: planning, reading, thinking, feeling productive.
Disconfirming evidence still counts. If something fails fast, the system is working.
Core vocabulary
Each term below has a strict meaning. Do not let the words drift.
Become a Pro member to unlock the rest
The Doctrine and Vocabulary are free. The remaining seven sections — Q1 goals, the bucket list, day types, the daily execution sheet, the Eisenhower reframe, and the full Q2 survivable system — are for Pro members.
See membershipMost of the site is free. Cancel anytime.
Founder OS is part of the extras — side material from the work behind carrington.cool, kept out of the way until it earns a place.
Get the systems notes when new playbooks ship
Join the newsletter for new operating systems, experiments, and product notes from carrington.cool.
Useful founder notes only.