Casa is the open-source control plane that runs a company from your terminal. It keeps the plan, the context, the review bar, and the human gates in your own files, and opens every session on the work that matters now.
Open sourceMITRead, fork, and contribute to the full operating layer.
EngineNode 20+Zero runtime dependencies. Node 20 or later.
StateYour repoThe company brain stays readable and versioned locally.
Catalog183 playbooksSelected by business fit and readiness, not by prompt.
Every pin is one of Casa's 183 playbooks. Point at one.
01What a session looks like
Open the terminal. The company is already loaded.
Casa reads the brain, names the binding constraint, and ranks what is ready. Operators produce real artifacts, critics review them, and consequential actions wait for you.
Demo company · InboxPilotCasa's own example · synthetic data
The session opens on the company's own files: what it is, where it stands, what it may do on its own, and everything already recorded. Nothing lives in a chat scroll.
NOW.mdWhere it standsread
profile.jsonWhat it isread
state.jsonIts constraintread
build-map.jsonThe planread
dials.jsonWhat may run aloneread
outputs/What was maderead
ledger.jsonlWhat happenedread
Company
InboxPilot · Casa's example company
Level
0 · Ideation and Validation
North star now
validated demand
Constraint
no users yet · Growth and Strategy lead
Session 01 · Step 02
Demo company InboxPilot · synthetic data
Rank the ready set
The binding constraint leads the order. Casa's router ranks only what is eligible now; blocked work cannot be started, whatever a prompt says.
Binding constraint
No users yet
Win: 100 paying subscribers at 8 dollars a month within 90 days
01StrategyProblem Validation Interviews7.158
02StrategyPhase 0 Company Brief5.270
03StrategyMarket Sizing (TAM/SAM/SOM)4.785
04StrategyCompetitive Teardown2.625
05StrategyWhy-Now Memo2.594
Ranked by Casa's own router (scripts/router.mjs next), v0.3.0 @ cf94ce4, for its example company.
Session 01 · Step 03
Demo company InboxPilot · synthetic data
Draft against the contract
An operator takes the top play and drafts it against the playbook's contract: its procedure, its deliverable, its rubric.
We believe account managers at client-services firms lose the first hour of a day rebuilding long client threads when they come back from time away, causing slow or off-voice replies, and today paste threads into general chatbots to cope.
Assumptions to test, ranked
1. Long client threads cost them time every week.
2. Their replies get forwarded, so voice matters.
3. Pasting client email into a chatbot feels unsafe.
Questions (past behavior only)
1. Walk me through the last long client thread you had to catch up on.
2. What did you do to get up to speed? What did it cost you?
3. Would you use a tool that summarizes threads for you?3. When did you last try to make this faster? What happened?
4. Who reads your replies before or after you send them?
Recruiting
10 to 30 client-services professionals (N1 in the opportunity brief). Stop when 7 of 10 confirm the problem unprompted.
The draft is an illustration written for this page from the example brain; the procedure it follows and the rules it keeps are the playbook's own (playbooks/level-0/002-problem-validation-interviews.md).
Session 01 · Step 04
Demo company InboxPilot · synthetic data
Review against the bar
Critics read the draft in parallel. A finding two of them raise is promoted; weak ones are suppressed. The operator fixes what must be fixed, and it is checked again.
CSCustomer skeptic1 finding
AHHonest numbersagrees
IRInvestor red teamno finding
BCBrand and copyno finding
Must fixraised by the customer skeptic, the honesty analyst agrees
Question 3 asks about the future.
Why: The playbook rejects hypothetical "would you use" answers as evidence.
Fix: Ask about the last time they tried to solve it.
Fixed on recheck
The personas and the merge rule are Casa's (skills/casa-review). The finding is an illustration; the rule it cites is the playbook's.
Session 01 · Step 05
Demo company InboxPilot · synthetic data
Wait for the founder
Strategy is set to approve first, so Casa proposes and waits. An approval is a record, not an execution: it goes on the ledger, and the work resumes from there.
Dial Strategy · approve first
Recruiting and running the interviews starts only with your yes. Casa proposed the work and is waiting.
Press and hold the button or the glass gate (or hold Space or Enter) until it fills.
Waiting for you. Nothing moves until you decide.
Session 01 · Step 06
Demo company InboxPilot · synthetic data
Commit to the brain
The artifact is written into the brain and its digest into the ledger, so someone who was not there can check what was produced. The latest line wins; nothing is edited.
Nothing is committed yet: the work is still waiting at the gate. Go back to the gate
The first line was written by Casa's ledger.mjs on a copy of the example brain. The lines your decision adds are written by this page in the same format, in your browser only.
When the report passes its rubric, the router ranks next
Change what holds the company back. The work changes.
The same company, further along: everything in its map below level 3 is done. Pick the binding constraint: Casa's router lifts the ready work of the departments that lead it, and when they have nothing ready, the order holds. Each ranking is the router's own output.
Binding constraint
01GrowthLanding Page CRO5.371
02GrowthPricing Page Copy & Layout4.875
03LegalData Processing Agreement and Subprocessor Package3.786
04LegalToS & Privacy Policy3.288
05ProductPRD Drafting3.162
Growth and Strategy lead this constraint, so the router lifts their ready work.
What-if: InboxPilot with its 38 map items below level 3 marked done, ranked by Casa's router (v0.3.0 @ cf94ce4) under each of its six constraints.
03Why a control plane
More capable agents make order load-bearing.
01
A durable company brain
State, decisions, artifacts, and learnings live in plain files in your git, not in a chat scroll.
02
Playbooks as contracts
183 pieces of company work with entry rules, dependencies, deliverables, and a review bar. The model cannot start blocked work.
148 dependencies between them
03
Human gates that hold
Action gates cover spending, going public, merging to main and destructive changes. Review the continuing update behavior before connecting a public company.
60 playbooks carry a human gate
Autonomy dials · InboxPilot
Flip a department. The plane lights what would run on its own, pales what Casa would propose first, and rings what always stops for a person.
Strategy0 run · 11 ask · 6 stop
Product0 run · 12 ask · 1 stop
Brand0 run · 9 ask · 3 stop
Engineering0 run · 10 ask · 7 stop
Data0 run · 12 ask · 1 stop
Growth0 run · 33 ask · 15 stop
Success0 run · 8 ask · 2 stop
Sales0 run · 9 ask · 3 stop
Finance0 run · 10 ask · 6 stop
Legalnot in InboxPilot's roster
Operationsnot in InboxPilot's roster
Always asks · no dial crosses this line
Spend money
Go public
Merge to main
Destructive
Every department starts at approve first in the example.
04Casa Phase 0
One company brain. A complete first chapter.
Turn the evidence into a company brief, a product architecture and a plan to build. Casa carries that context into your website, one-pager and deck.
01
Define the product. Brief, architecture, product flow and data model.
02
Map the work. Roadmap, agent mandates and a 90-day plan.
03
Make it legible. A site, one-pager and deck from the same context.
13 Phase 0 playbooks, picked out on the plane Phase 0 Company Brief · Phase 0 Website · Phase 0 One-Pager · Phase 0 Pitch Deck · Phase 0 Publish Readiness · Phase 0 Architecture · Phase 0 Product Flow · Phase 0 Data Model · Phase 0 Roadmap · Phase 0 Org Chart · Phase 0 Task Plan · Phase 0 Token Flow · Phase 0 Publish
