Docs
Catalog data format
The fields used by component pages and the JSON catalog.
Schema
Core data schema
Each public core is represented by typed data and exported as JSON.
| Field | Purpose |
|---|---|
| slug, name, shortDescription | Stable identification and catalog copy. |
| category, tags, domain | Filtering, discovery and related-core logic. |
| status, verificationLevel | Compatibility summary; lifecycle and verification[] are authoritative. |
| license, commercialSupport | Component license terms and support availability. |
| repositoryUrl, docsUrl, packageUrl | Public evidence and package links where available. |
| supportedBoards, supportedToolchains | Target support without implying measured validation. |
| interfaces, clocks, resets, parameters, ports | Integration contract. |
| resourceUsage, benchmarks | Measured or explicitly pending evidence. |
| sourceAccess, distributionAccess | Independent access states; unknown is not private. |
| verification[] | kind, result, sourceState, evidenceRefs, scope and checkedAt or notCheckedReason. |
| lastContentReviewedAt | Fact review date, independent of release build time. |
| limitations, aiSummary | Do-not-overclaim guidance for humans and LLMs. |
type Lifecycle = 'unknown' | 'concept' | 'in_development' | 'prototype' | 'alpha' | 'beta' | 'released' | 'deprecated';