Schemas¶
JSON Schema (draft 2020-12) definitions for the machine-readable metadata layer of this repository: venture records, product records, component records, repository registry entries, ADR front matter, and general document front matter.
Markdown remains the primary human-readable, authoritative format for this
repository. These schemas validate the structured metadata that sits
alongside Markdown content (front matter, venture.json, product.json,
component.json, and the portfolio/*.json registries) — they do not
attempt to encode narrative content.
| Schema | Validates |
|---|---|
document-metadata.schema.json |
YAML front matter on authoritative Markdown documents. |
venture.schema.json |
venture.json files and entries in portfolio/venture-registry.json. |
product.schema.json |
product.json files and entries in portfolio/product-registry.json. |
component.schema.json |
component.json files under venture component catalogs. |
repository.schema.json |
Entries in portfolio/repository-registry.json. |
adr.schema.json |
Front matter on ADR documents in docs/decisions/. |
scripts/validate_registries.py currently performs focused
standard-library validation against a subset of these fields rather than a
full JSON Schema validation pass, to avoid adding a third-party dependency
for the initial repository foundation. See
../docs/standards/dependency-and-tooling-standard.md
for the reasoning. Adopting a JSON Schema validator library remains an open
option for a future revision if the registries grow more complex.