Getting started

A local engine with an optional public connection.

Model judgment produces the work; deterministic code controls graph eligibility, gates and durable state.

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

CASA / ARCHITECTUREJudgment around a deterministic core
  1. HARNESS

    Skills and operators

    Your agent harness supplies model reasoning, tools and the session interface.

  2. ENGINE

    Rules and transitions

    Node 20+ CLIs enforce eligibility, dependencies, gates and state updates with zero runtime dependencies.

  3. BRAIN

    Local durable context

    JSON, Markdown and JSONL hold the profile, work and evidence. Optional capx/ tools connect to hosted services.

The local core works offline. Hosted publication is a separate integration shipped in the public repository.

Local core

The harness reads skills and invokes specialist operators. Separate Node scripts select playbooks, order dependencies, record completions, evaluate gates and update the brain. The engine reads JSON and writes JSON, Markdown or JSONL; the profile is profile.json.

The face builder reads completed local artifacts into face.json. It can build a partial face during work. A successful build is not a publish-readiness pass. Local CAF generation, signing and checks also work without hosted publication.

Hosted integration

The public repository includes capx/ clients and hook configuration in addition to the local core. The Casa service accepts signed submissions, records observations and serves public company material. Terminal reads that material and proxies registration actions. Launchpad manages token-market interactions; it does not receive the private company brain.

Note: Connected mode can publish later updates

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.