JSON Schema

Machine-readable JSON Schemas for validating BCP files. Served with Content-Type: application/schema+json to enable automated tooling.

BCP 2.0 schemas and validator

• 2.0 frontmatter — exact protocol version, source coverage and file metadata.
• 2.0 claims blocks — independent use, evidence and brand-approval statuses.
• 2.0 delivery — response scope, exact requested-file identity and integrity scope.
• Reference validator download — extract, run npm install --ignore-scripts, then npm test or npm run validate -- package files.json.
• 2.0 migration mapping — preserve ownership, editorial content, evidence dates and historical signatures.
• Independent example and conformance tests — no Encoded account or domain required.

The validator checks document structure and delivery consistency. It does not establish factual truth, legal approval, successful AI ingestion or independent signature verification.

Historical schemas (1.x and earlier)

• brand-context.schema.json — Validates BCP v1.1.0 root, pointer, and daughter frontmatter, including Registry-direct, self-hosted, and Registry-backed packages
• claims.schema.json — Validates the deterministic claims companion, including three-component BCP versions
• manifest.schema.json — Validates package file records, checksums, extension metadata, and three-component BCP versions

v0.2 daughter schemas

• voice.schema.json — Validates voice.md frontmatter and structured body blocks (traits, vocabulary, messaging tiers, anti-AI patterns)
• visual.json — Validates visual.md (logo variants, color tokens, typography, imagery)
• representation.json — Validates representation.md including never_compare_to and framing_traps

v0.1 Schemas

• brand.json — Root frontmatter schema

Schema source

All schemas are published in the canonical spec repository.