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.
The package is most useful when its parts constrain one another. The product flow should describe the behavior promised in the brief. The architecture should explain how that behavior is supported, and the data model should make the required information explicit. The roadmap and mandates then assign the work needed to close the gap between the present company and the intended product.
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.
This file structure gives review a concrete object. A founder can open the brief, follow a diagram, inspect a milestone and ask which evidence supports it. If the brief changes, revisit the dependent artifacts before regenerating the website or deck. Otherwise, the collateral can drift into several incompatible versions of the same company.
Treat the face as a projection of that work. A missing component is a visible gap to complete, while an available component still needs a substantive review. Seven populated sections can describe an incoherent plan; coverage makes the package easier to inspect, but the founder must still inspect 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.
Before the first public step, read the package as an outside reader would. Separate current capability from planned work, check the linked collateral and confirm the destination. The point is to publish a coherent, inspectable account of the company. It is not necessary to create a token merely to give that account a public home.