Casa

Eleven functions, one ranking

Departments are useful lenses, but they do not get separate priority systems. Casa names the problem that can kill the company at its current stage and puts the functions that resolve it in the lead.

Reviewed September 16, 2026 · Casa v0.3.0 · Current Launchpad mainnet presets. Release notes

The eleven

DepartmentOwns
StrategyVenture viability, business-model selection, pricing, stage gates
BrandNaming, positioning, entity formation prep, brand system
ProductMVP scope, feature priority, roadmap, product and design specs
EngineeringStack, deployment, observability, security baseline, incident response
DataEvent taxonomy, dashboards, attribution, north-star measurement
GrowthExperiments, channels, funnel and CRO, traction loops, lifecycle
SalesProspecting, pitch, pricing positions, deal management
SuccessOnboarding, retention and winback, expansion, health scoring
FinanceUnit economics, runway, cap table, model, fundraising materials
OperationsHiring and org design, process, vendor strategy
LegalCompliance roadmap and the actions that must never run unattended

Lead, support, or wait

The binding constraint decides posture. If activation is the constraint, Product and Growth lead, Data supports with instrumentation, and Sales waits, no matter how full its backlog looks. Readiness gates prevent out-of-order work across functions.

CASA / ROLESSpecialists, company agents and critics
  1. LIBRARY

    14 specialist operators

    A reusable operator library spans the company's functions.

  2. COMPANY

    agents.json

    A company-specific roster records roles and mandates. It is not a claim that every operator is always running.

  3. REVIEW

    Critic panels

    Review personas check work against the rubric. /casa-cos is the Chief of Staff skill, not an extra operator.

The catalog has 183 playbooks across 11 departments and 26 skills in Casa v0.3.0, reviewed September 16, 2026.

The board view: one constraint at the top, eleven departments in lead, support, or idle posture.
Note: Approve-first by default

Every department starts at approve-first autonomy. You dial up automation per department as trust builds. See Governance and gates.

Next steps

Department autonomy

Each department uses auto or approve_first. Action-level hard gates still apply. The company org chart and agent mandates describe responsibility; they do not change the engine’s eleven departments.