The ownership rule
An authored artifact is the designated source of truth for a fact. A generated artifact is a deterministic projection, index, interface, fixture, package input, or evidence record derived from authored authority.
Change the authored owner, run the canonical generator, and review the resulting projection. A manual edit to generated output either disappears on regeneration or creates drift that validation must reject.
Sources for block 1: projection-norms, catalog-cli
Authority matrix
| Fact | Authored authority | Generated or transported evidence |
|---|---|---|
| Brand intent and semantic roles | Brand and token source artifacts | W3C token files, target token APIs, and documentation data |
| Reusable Component public surface | Component contract YAML | TypeScript and Dart interfaces, normalized contracts, reference pages, and package exports |
| Composition-backed Component implementation | Composition body embedded in the Component contract | Strict Composition JSON and provenance sidecar |
| Screen or Shell assembly | Authored Composition document | Editor projections, target implementations, and execution digests |
| Reusable state semantics | Behavior contract | Target machines, runtime blueprints, and trace evidence |
| Catalog membership and ownership | Catalog manifest and manifest-owned artifact tree | Discovery indexes, generated examples, packages, and documentation facts |
Sources for block 1: product-brand-term, product-semantic-token-term, product-component-contract-term, product-behavior-term, product-screen-term, product-shell-term, product-composition-term, product-catalog-term
Implementation status
| Statement type | What it answers | Evidence |
|---|---|---|
| Normative | What an artifact means and which invariants valid implementations satisfy. | Contract, schema, term, or specification. |
| Implemented | Which projection or validator exists at a particular revision. | Generated producer facts and tests. |
| Released | Which consumer channel and version can be acquired. | Registry, Git tag, native digest, and release readback. |
| Planned | Which normative capability has no supported procedure yet. | Explicit availability state; no procedural steps. |
Sources for block 1: catalog-bundle, studio-composition
Drift is evidence
wyrd-catalog check --catalog wyrd.catalog.jsonExpected: Authored Catalog inputs and committed projections agree.
Verified by catalog-cli.
Sources for block 1: catalog-cli
Sources for block 2: projection-norms