Review the package, then connect it to the public record.
Local face generation, signed operating records and hosted publication are separate steps.
Reviewed September 16, 2026 · Casa v0.3.0 · Current Launchpad mainnet presets. Release notes
- 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.
Prepare the company
- Complete the required Phase 0 artifacts and publish-readiness review.
- Build face.json and inspect the exact company claims and diagrams.
- Review the site, one-pager and deck folders; remove private files from the publication directories.
- Have a company signing key outside the brain and a local CAF record.
- Approve the public scope and understand the continuing behavior of a bound brain.
Establish the hosted company record
For a tokenless company, first create or update the private hosted profile. Supply the real HTTPS logo URL and a supported category slug; name and description default to company_name and one_liner in profile.json. A company already bound through Launchpad can use that existing hosted identity. These commands contact the Casa service.
node capx/profile.mjs --brain company-brain --logo "<https-logo-url>" --category "<category-slug>"Create and sign the local CAF record using the attestation guide, then push it. Hosted publication readiness requires an observed completed playbook, alongside the profile and public collateral. Do not fabricate a completion to satisfy readiness.
node capx/register.mjs push --brain company-brainPublish the reviewed collateral and face
The following commands require the capx/ integration, the company signing key and an existing hosted company record created by profile setup or token binding. They upload and activate public artifact versions, then send face.json. Run from the Casa checkout, or use absolute script and brain paths. These are network publication actions, not local previews.
node scripts/face.mjs build company-brainnode capx/publish.mjs site --dir company-brain/outputs/phase0-website --brain company-brainnode capx/publish.mjs one-pager --dir company-brain/outputs/phase0-one-pager --brain company-brainnode capx/publish.mjs deck --dir company-brain/outputs/phase0-pitch-deck --brain company-brainnode capx/publish.mjs face --brain company-brainCheck the returned URLs and company identity. Record confirmed URLs and approval scope in outputs/phase0-publish/README.md. Leave failures and missing integration steps open; a local file path is not a public URL.
Register a tokenless company or claim its page
For first publication, the service checks name, description, logo, category, publicly active site, one-pager and deck, and an observed completed playbook. Missing requirements produce NOT_READY. Seven-part face coverage is informational and does not replace these readiness checks. An already public company uses the claim flow.
node capx/terminal-code.mjs --brain company-brainThe integration requests a nonce from the Casa service, signs it with the company key and requests a registration code. The code expires after ten minutes. Redeem it at terminal.capx.ai/register. Terminal proxies the publish-or-claim flow to Casa. A token is not required. Terminal registration does not create a local Launchpad binding receipt.
What happens after connection
The public repository includes the optional capx/ integration and a guarded SessionEnd hook. Binding is treated as initial go-public consent. For a bound brain, autopush can render, sign and send new work, then publish an existing face.json. An unbound brain is a no-op. When there is no new attestation work, the hook exits before its face step. Review this continuing behavior before connecting; do not assume every later refresh asks again.