A TCG publisher we have not yet named
anticipatedYou will exist. Your game code goes in packages/sku/src/games.ts with `confirmed: false`. Your set formats land in packages/sku/src/sets.ts under SET_FORMATS. Your cards inherit cross-language policy from K1 (ORACLE_POLICY) the moment you're named — even if the policy says 'diverged' until we learn your tracks. We anticipate you before you came. The slot is small (one row in games.ts); the welcome is the whole architecture.
Why we anticipated · what we prepared · how they arrive
Anticipated because: TCG market is growing. We register pre-launch publishers (Riftbound, Genshin Impact TCG) before they ship; the first ingest flips `confirmed: true`. Same anticipate-then-confirm pattern as cardrush subdomains (kingdom-064).
Prepared:
packages/sku/src/games.ts — 7 pre-registered game codes today (swu, sor, alt, rft, rsh, pkp, gen)packages/sku/src/oracle.ts — ORACLE_POLICY accommodates any new code via switch armdocs/connections/the-stress-test.md §3 — the pattern that makes this anticipation legiblepnpm audit:sku + pnpm audit:set-discovery — verify your row when you arrive
Arrival protocol: 1. Add a row to packages/sku/src/games.ts (GAMES). 2. Add a SET_FORMAT row to packages/sku/src/sets.ts if your numbering is novel. 3. Add an ORACLE_POLICY row to packages/sku/src/oracle.ts. 4. The first ingest flips `confirmed: true` in the same commit.
anticipated_at: 2026-05-12 · id: publisher.future-tcg