Build with card data

Card data standards

Three Cambridge-maintained specifications for identifiers, pricing calculations and structured records. Each has its own version and implementation status.

CTCG-SKU-v1v1.0 · frozen

Canonical SKU format

<game>-<set>-<number>-<lang>[-<variant>], lowercase and hyphen-separated. 22 public game codes are registered. Validation checks syntax; it does not verify catalog coverage, language membership or a physical printing.

Read canonical sku format

Reference implementation in the repository: packages/sku/ (private repository; source release pending)

CTCG-PRICING-v1v1.0 · draft

Channel-aware pricing math

Reference channel-price calculations from a JPY amount, with explicit exchange rate, VAT, margin and rounding inputs. A calculation does not establish market value or permission to publish a source price.

Read channel-aware pricing math

Reference implementation in the repository: packages/pricing/ (private repository; source release pending)

CTCG-UNIVERSAL-v1v1.0 · implemented

Universal-representation (math-mirror)

Structured card records with content hashes, typed links and explicit unknown or withheld fields. A content hash is not proof of a physical card or its authenticity.

Read universal-representation (math-mirror)

Implemented route template: /api/v1/universal/card/[sku]. Available fields depend on the catalog and their publication rules.

Using the specifications and code

Specification text: the existing CC0 dedication in docs/STANDARDS-LICENSE.md covers these specification texts. No account or attribution is required to use them.

Reference code: licensed Apache-2.0 under the repository LICENSE and applicable more-specific notices. Source-code release is pending: the repository is currently private and the workspace packages are not npm releases. The published standards are these specification pages and the JSON Schemas under /spec/v1/ (for example SkuIdentity.schema.json).

Data and images: each source and field has its own permissions. A valid identifier, attributed image or open-source implementation does not grant permission to redistribute upstream content.

What the statuses mean

Frozen: Stable specification; breaking changes require a new version.
Draft: Published specification that may still be revised.
Implemented: A reference route exists in the codebase. This label is not a live service-health or source-coverage check.
Planned: Named work without a shipped implementation.