Capability Registry
One structured documentation record of what a Primitive capability is, where it lives and how mature it is.
The Docs Capability Registry is the machine-readable read model used to generate the human feature catalogue. A capability carries identity, maturity, relationships, primitives, surfaces and evidence pointers while implementation and Control remain authoritative.
Instead of keeping one list of features for people and another list for software, Primitive keeps one labelled card for each capability and lets both people and machines read it.
The registry borrows the useful part of shadcn's distribution model: predictable structured records. Primitive extends the idea from UI components to system capabilities. In this repo it is deliberately a read model over implementation and Control truth; the same contract can later be generated from a Control-owned capability registry for search, agents, Create and dependency inspection.
Where this concept shows up
Record contract
A capability record requires a stable slug, title, category, status, plain-language comprehension layers, surfaces, primitives, relationships and source evidence.
Truth boundary
The registry describes and indexes capabilities; it does not overrule implementation repositories or Control authority. Its status must be reconciled against those sources.
Future direction
A broader registry could distribute or discover skills, agents, workflows, components, policies and templates using related schemas while preserving type-specific contracts.
Source lineage
Concept pages preserve whether an idea is canonical, proposed or working theory. That label is independent from whether a related product feature is implemented.