Product details reviewed and diagrams updated · 2026-09-16. Release notes

A complete page is useful context. It is not a substitute for knowing where each claim came from.

01

Read the public company package

Terminal company pages now extend beyond a row: brief, architecture, flow, data model, roadmap, task plan, agent mandates, activity, attestation and collateral. Mint and slug routes provide access to the same continuing company identity.

The face completeness indicator covers seven components. It measures whether the package is present, not whether the business is strong or the roadmap is already delivered.

Read the page in layers. Begin with the brief to understand the intended company, then use the diagrams and plans to make its claims concrete. After that, inspect the operating record and any associated market. This order helps avoid mistaking an active token for a complete company package, or a polished company face for evidence of delivered results.

Terminal / reading a companyStart with the company, then inspect its record.
The company package, operating record and optional market are read together while their sources and scope remain distinct.READING ORDER / FROM COMPANY INTENT TO SUPPORTING EVIDENCEPUBLIC COMPANY IDENTITYCompany page / slug route / optional mint route01 / UNDERSTANDThe companyBrief and product diagramsRoadmap and task planAgent mandates + collateral02 / INSPECTThe recordActivity and attestationThe scope of each checkSource and observation time03 / IF LINKEDThe marketPayment-token denominationCurve or pool venueConversion source + freshnessA seven-part coverage indicator tells you what is present, not whether the company will succeed.Company-only, token-only and bound records are different valid views; a token is optional.
Swipe to explore the full diagram
02

Keep provenance attached

On-chain data describes network state. Reproduced checks describe the supported structural or arithmetic checks re-run against a submitted record. Committed bytes can be compared with a disclosed hash. Claimed material is authored by the company.

The Casa service records observations; Terminal presents them. A local self-check is not an independent observation, and a hash match does not validate a diagram’s business claims.

A useful question is “What would this observation let me conclude?” A network read can support a statement about a mint or pool at a particular time. A reproduced check can support the calculation or structure it actually tested. A file commitment can identify bytes. None of these automatically establishes that a roadmap is achievable or a product has customers.

Keep the timestamp and scope close to the value being read. A fresh market observation and an older company-authored plan can both be useful, but they describe different things at different times. Presenting them together should make those differences easier to see.

Terminal / evidence classesFour labels. Four different kinds of support.
Network observations, reproduced checks, committed bytes and company-authored claims make different statements and must not be conflated.FOUR EVIDENCE CLASSES / KEEP THE CLAIM WITH ITS SOURCENETWORKRead from the chainMint, pool or network stateIdentify the network and observation time.REPRODUCEDA check run againSupported structural or arithmetic checksInspect what the check actually covers.COMMITTEDBytes match a commitmentA disclosed hash can bind a particular fileA hash match does not make the claim true.CLAIMEDAuthored by the companyBriefs, diagrams, plans and statementsRead the evidence behind the assertion.A local self-check is not an independent observation; a source label keeps the distinction visible.
Swipe to explore the full diagram
03

Connect identity and market carefully

Token binding and company registration use different codes and destinations. A Launchpad bind code belongs in the Casa project; a Terminal registration code comes from the Casa integration and is redeemed at /register. A company can publish without a token.

A linked market can use CAPX or another eligible payment token. Native amounts require that denomination, while USD comparisons require the actual quote asset’s conversion source and freshness.

Treat identity as a deliberate association. The company page can stand on its own before a token is linked, and the registration journey should not be confused with the token-binding journey. Once a market is associated, confirm the mint and payment asset before comparing prices or valuations with another company. Shared display conventions do not make different quote currencies interchangeable.

Capx / identity connectionsThe two codes travel in opposite directions.
A Launchpad token bind code enters Casa. A Casa Terminal registration code is redeemed at Terminal /register and expires after ten minutes.TWO CODES / DO NOT SWAP THEIR DESTINATIONSTOKEN BINDINGLaunchpad issues the bind code.Use it in the Casa project to associate a mint.capx/bind.mjsCode enters Casa.COMPANY REGISTRATIONCasa issues the registration code.Create a code with capx/terminal-code.mjs.Terminal /registerCode enters Terminal.Terminal registration codes expire after ten minutes. A company can register without a token.
Swipe to explore the full diagram
Terminal methodologyExplore the ZZZ reference company
END NOTE