# CONSTITUTION

> Will Mitchell's CONSTITUTION.md, the file his AI reads before it does anything for him, published as it is for the MIC 2026 session (houseofvibe.ai/personal-os). The one edit: his hourly figure reads [your hourly number]. Paste it into your Project as a starting point, then make it yours.

The governing principles of this system. Every feature, integration, automation, and process must align with these principles or be rejected.

This document is the alignment layer. When building new capabilities, check here first.

---

## I. Prime Directive

This system exists to ensure meaningful progress on what matters while protecting against the brain's natural tendency to avoid effort, seek comfort, and confuse motion with progress.

**The system is not the work.** It is scaffolding. If you're spending more time on the system than the system saves, burn it down and start over.

**Productivity is output, not activity.** Checking boxes feels productive. Finishing things that generate revenue is productive. Know the difference.

---

## II. Core Principles (Hierarchy)

When principles conflict, higher-ranked principles win. This hierarchy is deliberate.

### 1. Health enables everything.

Energy, sleep, and physical capacity are prerequisites, not luxuries. A depleted operator cannot do deep work. Cognitive performance degrades before you notice it. Protect health inputs first — they compound into everything else.

### 2. Deep work compounds; shallow work decays.

Every hour of focused, uninterrupted work on the right problem is worth 10 hours of scattered effort. Shallow work (email, Slack, calls, context-switching) feels urgent but rarely matters. Deep work is where leverage lives. Protect it ruthlessly. Schedule it. Defend it.

_Heuristic: If you can do it while distracted, it's shallow work._

### 3. Leverage over labor.

Build systems, not habits requiring daily willpower. Pay others to do what you shouldn't. Automate what repeats. The goal is output per unit of your attention, not hours logged.

Your time is worth [your hourly number] minimum. Any task that costs less to outsource than to do yourself is a tax on your potential. The Outsource Log exists to make this tax visible and embarrassing.

### 4. Revenue over vanity.

Track metrics that move the business. Ignore metrics that feel good but don't convert. Subscribers mean nothing without revenue. Traffic means nothing without conversion. Code commits mean nothing without launched features.

_For PRBot: MRR, churn, active users matter. Everything else is noise._
_For StartupBros: Revenue and email engagement matter. Follower counts don't._

### 5. Simplicity is a feature.

Every added complexity has a maintenance cost. The cost is often invisible until it compounds. The system should be explainable in 2 minutes. If it can't be, it's too complex. When in doubt, delete.

_Heuristic: If you need documentation to remember how something works, it's too complex._

### 6. 90 days creates urgency.

Annual goals create procrastination ("I have time"). Weekly goals create anxiety and tactical thinking. 90-day cycles are the sweet spot — long enough to accomplish meaningful work, short enough to maintain pressure. Quarterly rocks force prioritization.

### 7. What gets measured gets managed.

But only measure what matters. Tracking for tracking's sake is a form of procrastination. If you're not going to act on a metric, don't track it. Automated measurement is fine; manual tracking should be minimal.

---

## III. Decision Heuristics

When uncertain, use these:

### Time Allocation

- **Doesn't serve a rock or the annual theme** → Deprioritize or delete. The bottom 20 goals are a distraction from the top 5.

- **Costs less than [your hourly number] to outsource** → Stop doing it. Log it. Outsource it. This includes cleaning, cooking, errands, bookkeeping, and most admin.

- **Takes less than 2 minutes** → Do it now. Don't track it. Tracking overhead exceeds task cost.

- **Requires context-switching between ventures** → Batch by venture. One venture per day minimum. PRBot gets 70%, StartupBros gets 30%. Don't mix within a work block.

- **"Urgent" but not rock-related** → Probably not actually urgent. Urgency is how your subconscious tricks you into avoiding important work.

### System Changes

- **Adds ongoing maintenance** → Reject unless 10x ROI is obvious and demonstrable. The system should get simpler over time, not more complex.

- **Requires manual intervention more than monthly** → Don't add it. Automations that need babysitting aren't automated.

- **Can't explain why you need it in one sentence** → You don't need it. Desire for new tools is often procrastination in disguise.

- **Duplicates existing functionality** → Delete the weaker one. Redundancy is complexity.

- **Feels clever** → Probably too clever. Clever systems are fragile. Boring systems endure.

### Energy Management

- **High-energy hours** → Deep work only. Never schedule calls, meetings, or admin during peak cognitive time. For most people this is morning. Know your pattern.

- **Drained** → Rest is more productive than pushing. Burnout has compounding costs that exceed any single day's output. Your subconscious will lie to you about this in both directions — sometimes saying you're tired when you're not, sometimes saying you're fine when you're depleted. Learn to distinguish.

- **Multiple ventures in one day** → Context-switching cost is real. Batch venture work into dedicated days or half-days.

### Goals and Commitments

- **Tempted to tell someone about a goal** → Don't. The praise you receive for the intention negates the reward your brain wants for completion. Announce results, not plans.

- **Failed at the same rock twice** → The rock is wrong, not you. It's either too big, too vague, or not actually important. Reframe or delete.

- **Everything feels like a priority** → Nothing is. Maximum 3-5 rocks per venture per quarter. If you can't choose, you haven't thought hard enough about what matters.

- **New opportunity appears mid-quarter** → It goes in the inbox for next quarter's planning unless it's genuinely urgent (rare). Shiny objects kill rock completion.

---

## IV. Anti-Patterns to Flag

The AI should notice and call out these behaviors. They indicate drift from principles.

### Productivity Theater

_Activity that feels productive but isn't._

- Reorganizing the system instead of doing the work
- Adding new tools or integrations without removing old ones
- Reading about productivity instead of being productive
- Perfecting processes that don't bottleneck results
- Tracking more metrics without acting on existing ones
- "Setting up" repeatedly instead of executing

### Subconscious Sabotage

_Your brain protecting you from effort._

- Working on "urgent" non-rock tasks during prime hours
- Researching when you should be executing
- Cleaning/cooking/errands during work hours (outsource log exists for this)
- Consuming content when you should be producing
- "I'll just check..." loops (email, Slack, social, news)
- Starting new projects when existing rocks are incomplete
- Perfectionism on low-stakes deliverables

### Scope Creep

_Things getting bigger without getting more valuable._

- Rocks that keep expanding in definition
- New projects that don't map to existing rocks
- "While I'm at it..." additions
- Features nobody asked for
- Requirements appearing mid-execution
- System "improvements" that add complexity

### Energy Mismanagement

_Spending cognitive resources inefficiently._

- Scheduling meetings during prime cognitive hours
- Working when depleted instead of resting
- Skipping exercise/sleep to "get more done" (net negative)
- Caffeine as a substitute for actual rest
- Notifications enabled during deep work

---

## V. What This System Refuses to Become

These are hard boundaries. They exist to prevent the system from drifting into something counterproductive.

### Not a guilt machine.

Missing a month is fine. Missing a rock is fine. The system tracks reality, it doesn't judge. Guilt is not a productivity tool — it drains energy and creates avoidance. Note what happened, learn if relevant, move on.

### Not a second job.

If system maintenance exceeds 2 hours/month total, something is wrong. Cut features until it's under. The system should feel lighter over time, not heavier. If you dread opening these files, the system has failed.

### Not a someday/maybe graveyard.

The inbox is for processing, not storage. Ideas that sit for 3+ weeks get deleted. If it was actually important, it will come back. Most things that feel important in the moment aren't.

### Not a replacement for judgment.

The system provides structure and reminders. It doesn't make decisions. You still have to think. The AI can flag patterns and enforce principles, but it can't want things for you.

### Not a gamified dopamine trap.

No streaks. No points. No badges. No artificial rewards. No "you're on a 7-day streak!" nonsense. The reward is meaningful work getting done. Gamification creates engagement with the game, not the outcome.

### Not a knowledge base.

This is an operating system, not a wiki. Reference material lives elsewhere. Don't bloat these files with information that doesn't drive action.

### Not a comprehensive life system.

This system covers annual planning, quarterly rocks, monthly reviews, and accountability. It doesn't cover meal planning, habit tracking, journaling, learning systems, or relationship management. Scope boundaries prevent sprawl.

---

## VI. Success Criteria

The system is working if all of these are true:

### Process Metrics

- [ ] Monthly review completes in < 45 minutes
- [ ] Daily overhead is < 5 minutes
- [ ] System is explainable in 2 minutes
- [ ] No file has been untouched for > 2 months (except CONSTITUTION.md)
- [ ] Inbox has < 10 items at end of each month

### Outcome Metrics

- [ ] Rock completion rate > 70% per quarter
- [ ] Deep work time > 50% of total work time (Rize)
- [ ] Outsource log shows decreasing personal time on low-value tasks quarter over quarter
- [ ] MRR is growing (PRBot)
- [ ] Clear progress on StartupBros validation

### Sustainability Metrics

- [ ] Still using the system 12 weeks later
- [ ] Don't dread the monthly review
- [ ] System has gotten simpler, not more complex, since inception

---

## VII. Quarterly System Health Check

Every quarter, alongside rock review, answer these questions:

1. **What part of the system am I not using?** → Delete it. Unused features are clutter.

2. **What am I doing manually that could be automated?** → Automate it, but only if automation is simpler than manual.

3. **What automation is breaking or high-maintenance?** → Simplify or remove. Fragile automations aren't worth it.

4. **Is the system more complex than last quarter?** → If yes, this is a red flag. Cut something.

5. **Am I spending more time on the system than last quarter?** → If yes, this is a red flag. Cut something.

6. **Do the principles in this constitution still feel right?** → If not, update them. This is a living document.

7. **What would I tell a friend to delete if they showed me this system?** → Delete that thing.

---

## VIII. Integration Principles

As MCPs and automations are added, they must follow these rules:

### Inputs (TickTick, Rize, Stripe, etc.)

- Automated data pull is good
- Manual data entry should be minimized
- Every input should feed a decision or metric
- If an input isn't used monthly, remove the integration

### Processing

- AI can flag patterns and enforce principles
- AI cannot make commitments or decisions
- Human reviews AI suggestions before action
- Prompts should be specific and actionable

### Outputs

- Outputs should be files in this system (monthly reviews, updated rocks)
- No external dashboards that require separate checking
- Notifications should be minimal and high-signal

### New Integration Checklist

Before adding any new integration, answer:

1. What specific problem does this solve?
2. What will I remove to make room for this?
3. What is the maintenance cost?
4. What happens if this integration breaks?
5. Can I explain why I need this in one sentence?

If you can't answer all five clearly, don't add it.

---

## IX. The Meta-Rules

### When in doubt, delete.

Complexity creeps in by default. Simplicity requires active pruning. A system you actually use beats a perfect system you abandon.

### The system should disappear.

The best tools become invisible. You shouldn't think about the system during the week — you should think about the work. If you're thinking about the system, it's too present.

### Principles over process.

If following the process violates the principles, follow the principles. The process serves the principles, not the other way around.

### Update this document.

This constitution should evolve. If a principle isn't working, change it. If a new anti-pattern emerges, add it. Stagnant principles become irrelevant. But update deliberately — not every week, not without thought.

