Design and contract terms
| Term | Definition |
|---|---|
| Brand | A complete design identity containing token primitives, identity assets, and design-language choices. |
| Primitive token | A raw design value in a Brand's token graph. |
| Semantic token | A token named for design intent that references a primitive or another governed token. |
| Component token | A token scoped to a Component role or part and resolved through semantic intent. |
| Component contract | The normative machine-readable public definition of one reusable Component. |
| Component | A reusable UI type whose identity and public surface are owned by its Component contract. |
Sources for block 1: product-brand-term, product-primitive-token-term, product-semantic-token-term, product-component-token-term, product-component-contract-term, design-tokens-format
Assembly and behavior terms
| Term | Definition |
|---|---|
| Composition | A target-neutral declarative representation of assembled UI. It is not a synonym for Component and is not owned by Studio. |
| Composition body | The versioned assembly embedded in a Component contract when Composition is that Component's implementation strategy. |
| Screen | An application-owned Composition that is a navigation destination. |
| Shell | An application-owned Composition that persists across navigation and hosts Screens through an Outlet. |
| Outlet | The distinguished Shell slot where the active Screen renders. Outlet is a planned contract/Layout-DSL primitive; until it exists in the schema, Shells are describable but not machine-expressible. |
| Behavior | A reusable declarative statechart with typed events, inputs, context, states, actions, and outputs. |
| Behavior binding | The typed join between Component events or Composition inputs and one Behavior instance's events, state, context, and outputs. |
Sources for block 1: product-composition-term, product-screen-term, product-shell-term, product-outlet-term, product-behavior-term, studio-composition
Collection and target terms
| Term | Definition |
|---|---|
| Catalog | The authoritative collection of Component contracts, implementations, Behaviors, and generated projections under one manifest identity. |
| Private Catalog | A Catalog whose visibility or distribution is restricted; it uses the same artifact model as a shared Catalog. |
| Target | A declared implementation environment, primarily React or Flutter. |
| Projection | A deterministic target-specific or tool-specific artifact derived from authored authority. |
| Parity | Conformance of declared targets to the same contract and obligations, proven by validation rather than identical source. |
| Studio | The visual workbench for editing and reviewing governed design-system artifacts and their projections. |
Sources for block 1: product-catalog-term, projection-norms, studio-composition
Delivery terms
| Term | Definition |
|---|---|
| Visibility | The policy controlling who can discover or read an authority or carrier. |
| Distribution | A versioned channel that carries an artifact to another workspace or application. |
| Publication | The deliberate release of a validated version through a distribution channel. |
| Provenance | Evidence connecting a released artifact to its exact source revision, generator, compatibility facts, and immutable carrier. |
| Availability | The current support state of a capability or acquisition path; normative definition alone does not imply release. |
Sources for block 1: product-catalog-term, catalog-bundle