Open data · Schema docs
JSON Schema for every machine-readable format
Formal JSON Schema (draft 2020-12) for each structured file this desk publishes, so a builder's validator, type generator, or linter can check any of these files without guessing at the shape by hand.
| Schema | Validates |
|---|---|
| citation-artifact.schema.json | Per-article citation.json — short answer, claims (with provenance IDs, verification dates, source chains), sources, license, evidence tier. |
| corpus.schema.json | /corpus.json — every article and page, with evidence type, dates, provenance ID, canonical + citation URLs. |
| release-manifest.schema.json | Hash-chained release manifests at /data/releases/latest.json and each /data/releases/<version>/manifest.json. |
| licensing.schema.json | /licensing.json — the cite / remix / commercial reuse tiers. |
| contributor-badge.schema.json | /contributors.json — badge levels and the current contributor registry. |
| corrections-queue.schema.json | /corrections-queue.json — submission/review status taxonomy and open items. |
| web3-readiness.schema.json | /web3/readiness.json — per-feature and per-page web3 gating/loyalty/verification readiness states (scaffold, not live). See /web3/. |
| web3-policy.schema.json | wallet-privacy.json, data-use.json, attribution-boundaries.json, onchain-data-use.json — draft-scaffold policy for wallet-based features. |
Each schema file is plain, static JSON — fetch it directly (no auth, no rate limit) and point any standard JSON Schema validator at it. See /builders/ for working code against the files these schemas describe, and /provenance/ for how the release manifests are hash-chained.