Casa keeps the plan, state, review bar and approval boundaries in the project you own.
Your harness, your company context
Casa uses the agent harness and model access you already have. Its local Node 20+ core has zero runtime dependencies. In v0.3.0, the catalog has 183 playbooks across eleven departments, with fourteen specialist operators and twenty-six skills.
The harness supplies judgment and tools. Deterministic scripts select eligible work, enforce dependencies, evaluate action gates and update state. The company brain stays in readable files rather than relying on a conversation to remember the business.
The division of responsibility matters. The model can investigate a question, draft an artifact or propose a next step. The local core supplies repeatable rules about what is eligible and which actions require approval. The brain holds the company context those rules and judgments operate on. Moving between sessions should not mean rebuilding the business from a transcript.
Make a company package, then operate it
Phase 0 produces the brief, architecture, product flow, data model, roadmap, org chart, agent mandates, task plan and collateral. Reviews keep the package tied to real evidence and distinguish current capabilities from planned work.
Existing companies fill missing artifacts without resetting their stage. Each subsequent session reads the current brain and chooses eligible work against the company’s constraint.
Think of the company package as an operating reference that stays useful after the first public page is built. A product decision may change the architecture; a new constraint may change the roadmap; a revised mandate may change who owns the next deliverable. Recording those changes keeps the next session grounded in the company as it exists now.
A productive session therefore has an outcome smaller and more testable than “run the company.” It selects eligible work, creates the promised artifact and checks it against the playbook’s rubric. The resulting file, review and state change make the next session easier to start and the completed work easier to inspect.
The public layer is optional
A reviewed face and signed operating record can be published through the Casa integration. A token can be launched through the current curve mechanism and optionally bound to the company. Terminal presents the published package beside its market.
The local core remains useful without either step. Before connecting, review the bound update path: the guarded session hook can send new work and an existing face after initial binding.
These are separate choices: operating locally, making the company public and associating it with a market. Decide which connection is useful at the current stage. The value of the local system comes from accumulated context and reviewed work, so a founder can establish those foundations before choosing a public profile or token relationship.