Terminal listing and stats policy
How rows appear, how aggregates stay sparse, and how published outputs are hashed in the browser. The mint is the join key. There is no listing queue.
How rows appear
Terminal is a read client over two public directories. It does not mint tokens, take applications, or run a founder-approval step. Launchpad tokens appear from the public directory. Companies appear when a founder redeems a bind code at /register. The mint is the join key.
| Source | How it appears |
|---|---|
| Launchpad token | From the Launchpad public directory |
| Casa company | Founder redeems a bind code at /register |
| Join key | The mint |
| Listing queue | None. No application. No founder-approval step. |
| Account | None. One code field. No dashboard. |
- Bind codes are issued by Launchpad when a creator connects Casa. Terminal never prints the code.
- Registration is one field at /register. No account, no dashboard, no login.
- A public row is a directory fact. Appearing as a row never changes a claimed value into a reproduced one.
- Casa is not required for a token to list. Binding after launch does not change the token, the company identity, or the company URL.
| Row | Meaning |
|---|---|
| Company with token | The mint joins both. Terminal shows the company record beside the market. |
| Company only | Valid. A Casa company can appear with no token. A token can attach later without changing identity or URL. |
| Token only | Valid. Unbound tokens are a normal state. They are not hidden or treated as incomplete. |
Aggregates
Terminal statistics are computed from live directories with a short TTL. Anything without a source renders as a dash. Terminal does not fabricate aggregates. Sparse data stays sparse.
| Policy | Rule |
|---|---|
| Source | Live directories. Terminal does not keep a separate company database. |
| Freshness | Short TTL. A stale snapshot is not presented as a current figure. |
| Missing source | A dash. Never zero. Never a synthetic number. |
| Fabrication | None. Thin or empty sections are a legitimate production condition. |
| Provenance | Aggregate labels do not collapse on-chain, reproduced, committed, and claimed into one total. |
Published outputs
Company pages can list published playbook outputs. The reader hashes fetched bytes in the browser and reports hash matches the committed event only when the browser-computed sha256 equals a disclosed event hash. Content itself stays founder claimed.
| Check | Rule |
|---|---|
| Where | Company pages, published playbook outputs |
| Who hashes | The reader, in the browser |
| Match phrase | hash matches the committed event |
| Match condition | Browser-computed sha256 equals a disclosed event hash |
| On mismatch or missing hash | No match is reported. The content label does not change. |
| Content label | Founder claimed. A hash match is existence and integrity of those bytes, not a judgment of the contents. |
Attested means Casa observed a CAF envelope that passed structural checks, arithmetic recount, chain integrity, and Casa's own observation signature. It does not mean the business is real, the metrics happened, or Capx endorses the token. Attested is never used for published playbook output content.