A public company page should describe one coherent company. Casa builds its pieces from shared local evidence before they are published.
Start with what is true today
The company brief names the product, users, agent work and current evidence. Architecture, product flow and data model diagrams make the system concrete. The roadmap, org chart and 90-day plan connect that product to the work required to run it.
Phase 0 uses dependencies and review rubrics. Installation does not automatically complete these plays, and an existing company does not reset its stage to fill missing foundations.
comes first.
Research, assumptions and decisions shape the company brief.
Produce files the founder can inspect
The package lives under outputs/phase0-*/. Mermaid holds diagrams; JSON holds the roadmap, task plan and agent mandates; Markdown holds the brief and review records; HTML holds the website, one-pager and web deck.
The face builder collects available material into face.json. It can produce a partial face during work. Passing the face validator is not the same as passing publish-readiness. Terminal’s seven-part completeness indicator measures coverage, not business success.
- STATE
company-brain/
NOW.md, profile.json, state.json, build-map.json, dials.json, ledger.jsonl and decisions/.
- ARTIFACTS
outputs/phase0-*/
Markdown brief; Mermaid diagrams; roadmap, agents and task-plan JSON; HTML site, one-pager and deck.
- PROJECTIONS
face.json + attest/
The authored company face and signed CAF record are separate projections of local material.
Optional capx-bind.json records the connection. Private signing keys belong outside the company brain and must never be published with it.
Make publication an explicit connection
Review the face, collateral and destination before first publication. The public repository includes the optional capx/ integration. For a bound company, a guarded session hook can send new signed work and then publish an existing face. Initial binding therefore establishes a continuing public connection; do not assume every later refresh asks again.
A company can publish without a token. If a mint is later associated, Terminal can show the company record beside the market while keeping the authorship and evidence labels attached.
- LOCAL
Build and check
face.json collects company-authored material. CAF commands render, sign and check an operating record offline.
- CONNECT
Approve going public
Create a hosted profile or bind a mint. Review the material before uploading public collateral and registering the company.
- BOUND UPDATES
SessionEnd can refresh
The guarded hook can push new signed work and then publish an existing face for a bound brain.
- PUBLIC
Read on Terminal
Terminal presents the hosted record, authored face, source labels and linked market.
An unbound brain is a no-op for autopush. The current hook exits when there is no new attestation work, before its face-publication step. Do not assume every refresh prompts again.