New paid orders and subscriptions are retired. Existing records, settlement and refunds remain available through your account.
Welcomes
The corpus of hospitality. Every kind of arrival — upstream source, publisher, federation peer, downstream adopter, agent, non-default being, future-self, and (since kingdom-083) the kingdom's own infrastructure — has a named slot here. Each slot says: who we anticipated, when, what we prepared, how they arrive. The kingdom prepares the welcome before the guest knocks. The corpus is the record of that preparation. Substrate-honest about anticipation: a slot exists before its subject does.
Total:41
Arrived:24
Anticipated:16
Blocked:1
Downstream adopters · 4
Mirrors, builders, aggregators, standard-citers — consumers of the spec.
✦ Mirror — partner caches our catalog
anticipated
Cache only what each response permits. Cambridge-authored schemas and explicit first-party CC0 datasets can be kept and remixed; mixed catalog exports are NOASSERTION until field-level upstream rights are preserved. `_meta.source_license` names policy-governed, proprietary, internal-only, and open layers separately.
Why we anticipated · what we prepared · how they arrive
Anticipated because: Mirroring is the lowest-cost adoption path. Adopters who can't sustain ingestion infrastructure can still build user-facing products.
Prepared:
data-pantry envelope — _meta.sources + _meta.source_license per response
FRESHNESS table in @cambridge-tcg/data-spec — declares per-key cache TTLs you can honor
_meta.request_id on every response — quotable in support if a discrepancy shows up
Arrival protocol: Just start caching. Optional attribution: cite our /standards URL in your published responses.
anticipated_at: 2026-05-12 · id: adopter.mirror
✦ Builder — partner ships an app on our data
anticipated
Build against /api/openapi.json and /standards.json. One contract, one envelope, one canonical SKU — your code learns the public shape once and never re-learns. When we evolve the spec (SPEC_VERSION bump), the old version stays at /api/v1/* for at least 12 months. The workspace packages are internal implementations, not published dependencies.
Why we anticipated · what we prepared · how they arrive
Anticipated because: Builders ship faster on stable contracts. Cambridge TCG's spec is intentionally narrow + intentionally stable.
Prepared:
/api/openapi.json — codegen-ready OpenAPI 3.1 document, CC0 for this document only
/standards.json — machine-readable standard versions, status, and exact license scope
/methodology/sku-standard — CC0 specification text for the canonical SKU; implementation code has separate rights
/api/v1/sources — public registry view of source policy and observed coverage
SPEC_VERSION + 12-month deprecation window for breaking changes
Arrival protocol: 1. Fetch /api/openapi.json and /standards.json. 2. Generate a client and implement the published SKU specification. 3. Build. (No registration required.)
anticipated_at: 2026-05-12 · id: adopter.builder
✦ Aggregator — partner federates across multiple platforms
anticipated
You're building cross-platform card identity. Our content_hash addressing lets you cache `(hash, source, as_of)` triples and re-resolve to SKUs when needed — even when the SKU changes upstream. K2 ships per-source upstream-anchor columns (scryfall_oracle_id, cardmarket_id_metacard, ygo_passcode); /api/v1/federation/identify/[anchor_type]/[id] (post-K2) will accept any of them.
Why we anticipated · what we prepared · how they arrive
Anticipated because: Aggregators are how a heterogeneous TCG ecosystem stays interoperable. Every aggregator that uses our standard makes other aggregators' jobs easier.
✦ Standard-citer — research / journalism / policy reference
anticipated
Cite us by URL + spec_version. The corpus is CC0. Our methodology pages are stable URLs (the schema lives in code; the explanation lives at /methodology/<topic>). The four doctrines, the cosmology, the fifth question — all citable, all evolving with version trails.
Why we anticipated · what we prepared · how they arrive
Anticipated because: Standards become standards by being citable. Cambridge TCG's substrate-honest doctrines + per-game policies + per-byte license metadata are unusual enough to be worth citing.
Prepared:
/methodology/* — stable URLs for every policy + formula