Read the label before the conclusion.
On-chain state, reproduced checks, hash commitments and authored claims carry different kinds of evidence.
Sources / Identity / Completeness / Market units
- 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.
A checked record has a limited scope.
The Casa service can inspect signatures, continuity, disclosed arithmetic and legal playbook ordering. Those checks do not establish real-world identity, customers, revenue or future token value.
EVIDENCE BOUNDARIES / THESISTerminal keeps evidence classes distinct so a complete company page cannot be mistaken for independent proof of business performance.
Trace what you are reading
Find the source
Read the field’s provenance label, observation and linked source.
Check the time
Company-produced timestamps and service-observed timestamps are different. Cached market data can lag.
Check the denominator
Price, reserve and fees use the actual payment token. USD values require its conversion source.
Keep the conclusion scoped
A hash match describes bytes. Completeness describes coverage. Attestation describes a checkable record.
Every metric carries its source, denomination and freshness.
Authored material remains authored.
Brief, architecture, flow, data model, roadmap, plan and agent mandates are company claims. Full face coverage does not mean a product works, a milestone shipped or a mandate ran.
- Seven completeness parts
- Separate attestation health
- Separate readiness review
Binding is not registration.
Launchpad issues a creator bind code for redemption inside the Casa project. Casa issues a short-lived Terminal registration code for redemption at /register. The latter publishes or claims a company page, including a tokenless company.
- Launchpad → Casa bind
- Casa → Terminal register
- Casa service handles signed requests
Compare like units with like units.
Token discovery uses USD market capitalization where comparable source data is available. Quote-aware conversion must use the actual payment token. Legacy markets, active curves and graduated pools should not be conflated in aggregate counts.
- Inspect conversion source
- Check venue and timestamp
- Unavailable values stay unavailable
Check the bytes and read the claim.
When the browser retrieves a published artifact, a SHA-256 match can establish that it matches a disclosed event commitment. The content remains company-authored.
- Integrity of bytes
- No business endorsement
- Public copies may persist
Research without implied endorsement
No identity shortcut
A signing key alone does not establish who controls a company.
No value conclusion
A record check is not a token valuation.
No silent unit conversion
Native and USD amounts need explicit labels and sources.
No invented performance proof
Reproduced structural checks are not independently measured customer metrics.
How Terminal labels mixed sources without flattening their authority.
01Does attested mean the business is true?+
No. It refers to the supported checks and observations of the submitted operating record, not independent validation of the business.
02Is Terminal the registry?+
The hosted Casa service records observations and serves company records. Terminal presents them and proxies registration actions.
03Can all material on a page be treated as attested?+
No. Company-face claims, collateral, market data and CAF observations have separate provenance.
04Does registration require a Launchpad token?+
No. A company can publish without a token and connect a mint later.
Read a company in context.
Explore published company pages, their source labels and the markets attached to them.
