Read each value with its source and scope.
A network fact, a structural check, a hash match and a company claim answer different questions.
Reviewed September 16, 2026 · Casa v0.3.0 · Current Launchpad mainnet presets. Release notes
- ON-CHAIN
Network state
Mint, pool and transaction facts. Displayed USD values additionally depend on price conversion sources.
- REPRODUCED
A check was re-run
Structural validation, arithmetic recount and chain continuity of the submitted record. The check has a limited scope.
- COMMITTED
Bytes match a hash
A retrieved artifact matches its commitment. The hash does not establish that its contents are true.
- CLAIMED
Company-authored
Brief, diagrams, roadmap, plan and agent mandates. Authorship is not independent business validation.
The hosted Casa service records observations; Terminal displays them. Face completeness, attestation health and token value are separate concepts.
Worked examples
| Example | Evidence class | Limit |
|---|---|---|
| Mint and pool state from Solana | On-chain | Does not establish creator identity or future value. |
| Recounted ledger events and chain continuity | Reproduced | Checks the submitted record, not whether the business event happened in the world. |
| Fetched output bytes match the event SHA-256 | Committed | Establishes correspondence to the committed bytes, not truth or quality. |
| A product diagram or planned milestone in face.json | Claimed | Company-authored; not independently validated business performance. |
| USD market capitalization | Derived display | Depends on supply, native price and the actual quote asset’s USD conversion and timestamp. |
Company face is authored material
The brief, architecture, flow, data model, roadmap, plan and agent mandates are claims made by the company. Hashing a diagram or signing the face does not turn its business assertions into reproduced evidence.
Who observes
The hosted Casa service records observations and runs its supported checks. Terminal displays those results and their provenance. A local caf check is a self-check, not a hosted observation. An observation timestamp says when the service saw a submission; the company’s own produced_at clock remains advisory.