ISSUE · BRANDS
A signature that says: this is ours.
Everything on this platform reduces to one mechanism: an organization signs a fact it is willing to stand behind, and anyone can check the signature without asking anyone's permission. For a brand, the fact is "this item is ours". That is not a special product. It is the same vouching rail every other page on this site describes, pointed at merchandise instead of people.
This page is shorter than its siblings, on purpose
The banking page can cite a liability model. The employment page can cite a regulation. This page can cite neither, because the written corpus behind this platform contains no authenticity-specific schema, no anti-counterfeiting design, and no brand customer — a brand appears in the founding brief exactly once, as an example of who might buy. A sector page that dressed that up as a product would be the swapped-stock-photo page our own build plan warns against. So this page states the mechanism, states the gap, and stops.
What a brand programme would be, when it is real work
Planned, in the plain sense of the word: a brand as a tenant, a claim type meaning "genuine article", issuance bound to a product or a batch, and revocation for recalls — each one an application of rails that already exist for organizational claims, none of it designed yet for this sector specifically. When that design work happens it will appear in the register below as rows with states, and this page will point at them instead of at this paragraph.
What is actually here today.
No brand issues on this platform today, no authenticity schema exists, and sector packs are planned work. This is the emptiest sector page on the site because its corpus is the emptiest — the honest gap is the content.
- PLANNED A wallet a person installs from an app store. wallet-native You cannot hold a credential on a phone you own. Everything a person would do with a proof waits behind this.
The register holds 17 live · 2 partial · 2 planned · 5 not yet.
4 of the 5 capabilities this page depends on have no row in the register yet, so this page will not print a state for them. They are named rather than dropped, because a slice that silently shortens itself is the same defect as a claim with no receipt.
- vc-issuance
- selective-disclosure
- partner-certification
- self-service-onboarding
The register route serves, but it carries no row for these yet. List what it does carry:
curl -s https://id.orbis.id/api/site/register | jq -r '.entries[].slug'