{
  "schema": "orbis-glossary/1",
  "note": "C-24 glossary terms. Served at /glossary.json so an agent can read the same rows a person reads at /glossary, and imported at build time by /glossary and /search so the two can never drift. Every 'endpoint' below was measured reachable in src/data/externals.json; nothing here links a URL no probe has answered.",
  "terms": [
    {
      "slug": "proof",
      "term": "Proof",
      "aliases": ["credential", "verifiable credential", "VC", "digital credential"],
      "glossOf": "W3C Verifiable Credentials Data Model 2.0",
      "definition": "A signed statement about a person, made by an organization that already knew the answer. The person carries it; anyone can check it; nobody can forge it.",
      "orbisClaim": "This site says proof in plain pages and verifiable credential on specification pages. They are the same object under two vocabularies.",
      "endpoint": null
    },
    {
      "slug": "selective-disclosure",
      "term": "Selective disclosure",
      "aliases": ["partial disclosure", "one row travels", "SD"],
      "glossOf": "IETF SD-JWT — Selective Disclosure for JWTs",
      "definition": "Sending one field out of a signed document and leaving the rest behind, without breaking the signature on what you sent.",
      "orbisClaim": "The fields that stay are not hidden and not greyed out. They were never sent, and the signature still checks without them. That is arithmetic, not policy.",
      "endpoint": null
    },
    {
      "slug": "sd-jwt-vc",
      "term": "SD-JWT VC",
      "aliases": ["SD-JWT", "selectively disclosable JWT credential"],
      "glossOf": "IETF OAuth WG — SD-JWT-based Verifiable Credentials",
      "definition": "The credential format this cell issues: a signed token whose individual claims can each be withheld or revealed by the person holding it.",
      "orbisClaim": "The issuer metadata for this format is served from the machine origin and can be fetched without an account.",
      "endpoint": "https://id.orbis.id/.well-known/jwt-vc-issuer"
    },
    {
      "slug": "did",
      "term": "DID",
      "aliases": ["decentralized identifier", "did:web", "issuer identifier"],
      "glossOf": "W3C Decentralized Identifiers (DIDs) 1.0",
      "definition": "An identifier an organization controls itself, which publishes the public keys it signs with. did:web resolves to a document served under the organization's own domain.",
      "orbisClaim": "Because the identifier lives under a domain the organization owns, leaving costs one DNS record and everything already issued keeps checking.",
      "endpoint": "https://id.orbis.id/.well-known/did.json"
    },
    {
      "slug": "issuer",
      "term": "Issuer",
      "aliases": ["the organization behind it", "who vouched"],
      "glossOf": "W3C Verifiable Credentials Data Model 2.0 — roles",
      "definition": "The organization that signs a statement it already knew to be true: a bank, an employer, a university, a city.",
      "orbisClaim": "An issuer never learns where a proof it signed was later used. There is no message from the checker back to the issuer, and that absence is the shape of the design.",
      "endpoint": "https://id.orbis.id/.well-known/openid-credential-issuer"
    },
    {
      "slug": "holder",
      "term": "Holder",
      "aliases": ["the person", "the wallet holder", "you"],
      "glossOf": "W3C Verifiable Credentials Data Model 2.0 — roles",
      "definition": "The person who carries the proof and decides, every single time, what to show and to whom.",
      "orbisClaim": "The word holder appears on specification pages. On plain pages the site says you, because that is who it means.",
      "endpoint": null
    },
    {
      "slug": "verifier",
      "term": "Verifier",
      "aliases": ["the checker", "relying party", "who is asking"],
      "glossOf": "W3C Verifiable Credentials Data Model 2.0 — roles",
      "definition": "Anyone who needs to know one thing and checks the signed answer instead of collecting the underlying documents.",
      "orbisClaim": "Checking needs no account and no key on this cell, and the route census that shows how many endpoints take no key is published as machine-readable data.",
      "endpoint": "https://id.orbis.id/openapi.json"
    },
    {
      "slug": "trust-anchor",
      "term": "Trust anchor",
      "aliases": ["issuer trust anchor", "root of trust", "is this issuer real"],
      "glossOf": "W3C Verifiable Credentials Data Model 2.0 — trust model",
      "definition": "The step where a checker decides whether the organization that signed a proof is one it is prepared to believe. A valid signature by an unknown party is still a valid signature by an unknown party.",
      "orbisClaim": "The signature being real and the signer being trusted are two separate checks on this site, and they are always named separately.",
      "endpoint": null
    },
    {
      "slug": "revocation",
      "term": "Revocation",
      "aliases": ["taking it back", "withdrawal", "status list", "token status list"],
      "glossOf": "IETF Token Status List",
      "definition": "The mechanism by which an organization withdraws a proof it issued, and by which any checker can find out that it did.",
      "orbisClaim": "The status list this cell publishes is itself signed, and it is fetchable by anyone. Taking something back is a public act, not a private one.",
      "endpoint": "https://id.orbis.id/status/1"
    },
    {
      "slug": "oid4vci",
      "term": "OpenID4VCI",
      "aliases": ["OID4VCI", "credential issuance protocol", "how a proof gets into a wallet"],
      "glossOf": "OpenID Foundation — OpenID for Verifiable Credential Issuance",
      "definition": "The wire protocol a wallet uses to collect a credential from an issuer, and the metadata document that tells the wallet how.",
      "orbisClaim": "The issuer metadata this protocol requires is served on the permissionless plane and needs no key to read.",
      "endpoint": "https://id.orbis.id/.well-known/openid-credential-issuer"
    },
    {
      "slug": "oid4vp",
      "term": "OpenID4VP",
      "aliases": ["OID4VP", "presentation protocol", "how a proof gets checked"],
      "glossOf": "OpenID Foundation — OpenID for Verifiable Presentations",
      "definition": "The wire protocol a checker uses to ask for one specific fact, and a wallet uses to answer with a proof of exactly that fact.",
      "orbisClaim": "The request names what it wants. The consent screen shows the person the same words before anything is sent.",
      "endpoint": "https://id.orbis.id/.well-known/oauth-authorization-server"
    },
    {
      "slug": "conformance-vector",
      "term": "Conformance vector",
      "aliases": ["test vector", "conformance suite", "prove it yourself"],
      "glossOf": "The cell's own published vector set",
      "definition": "A fixed input with a known correct answer, published so that anyone can point their own implementation at it and see whether it behaves.",
      "orbisClaim": "Point any verifier, in any language, at these vectors and prove it correct. Using our code is optional. The set is the contract.",
      "endpoint": "https://id.orbis.id/conformance/vectors"
    },
    {
      "slug": "secure-enclave",
      "term": "The phone's security chip",
      "aliases": ["secure enclave", "hardware-backed key", "StrongBox", "TEE", "device key"],
      "glossOf": "Platform key-custody documentation (Apple Secure Enclave, Android StrongBox)",
      "definition": "A separate piece of hardware inside a phone that can create a signing key and use it, but cannot hand the key out — not to an app, not to the manufacturer, not to us.",
      "orbisClaim": "Custody is an operation we cannot perform, not a promise we make. We are not being generous; the arithmetic does not contain the key.",
      "endpoint": null
    },
    {
      "slug": "tamper-evident",
      "term": "Tamper-evident",
      "aliases": ["tamper-proof", "was this altered"],
      "glossOf": "Cryptographic signature semantics",
      "definition": "A change to a signed document can be detected by anyone who checks it. It does not mean the document cannot be changed.",
      "orbisClaim": "That is what tamper-evident means, and it is a weaker and more honest claim than tamper-proof.",
      "endpoint": null
    },
    {
      "slug": "permissionless-plane",
      "term": "The permissionless plane",
      "aliases": ["public plane", "no key needed", "free forever", "unmetered routes"],
      "glossOf": "The cell's route census, published in its OpenAPI document",
      "definition": "The set of endpoints on this machine that answer without an account, a key or a bill. Checking a proof lives entirely inside it.",
      "orbisClaim": "It is free because there is nowhere to charge you. There is no authenticated seam on the verification path to meter — which is why we also cannot build a record of where you verified.",
      "endpoint": "https://id.orbis.id/openapi.json"
    },
    {
      "slug": "the-register",
      "term": "The register",
      "aliases": ["capability register", "what is real here", "state chip", "the rows that say no"],
      "glossOf": "This site's own data contract, orbis-register/1",
      "definition": "One row per capability: the claim, the state, the thing that proves it, how it was checked, when, and what a capability that does not work yet costs the reader today.",
      "orbisClaim": "Every state word on this site is generated from the register and never typed into a page. A claim with no register row cannot ship, and the build refuses it.",
      "endpoint": null
    },
    {
      "slug": "the-cell",
      "term": "The cell",
      "aliases": ["machine origin", "id.orbis.id", "the machine that serves it"],
      "glossOf": "This site's origin split",
      "definition": "The machine that issues, checks and publishes receipts. This site is the human origin; the cell is the machine one, and this site never copies a receipt from it.",
      "orbisClaim": "A proxied receipt is not a receipt. Every receipt on this site is a link to the cell, so you can fetch the same bytes we did.",
      "endpoint": "https://id.orbis.id/readyz"
    },
    {
      "slug": "consent-screen",
      "term": "The consent screen",
      "aliases": ["approval screen", "what will be sent", "who is asking"],
      "glossOf": "This site's component C-21",
      "definition": "The screen a person sees before anything leaves their phone. It answers five questions: who is asking, what for, exactly what will be sent, what stays, and for how long.",
      "orbisClaim": "The screen is shown as an illustration on this site until a real captured frame has been cleared, and it says so on the frame.",
      "endpoint": null
    }
  ]
}