How the system fits together
- Authored contractsCatalog graph validation
- Catalog graph validationGenerated React and Flutter projections
- Authored contractsShared Rust runtime
- Shared Rust runtimeGenerated React and Flutter projections
- Generated React and Flutter projectionsConsumer applications
Text equivalent
Authored contracts feed Catalog graph validation and the shared Rust runtime. Validation gates generated React and Flutter projections before they reach consumer applications, while the shared runtime carries the same behavior and motion semantics into both target hosts.
Sources for block 1: system-topology, studio-workbench
Authority layer
Brand and semantic-token sources own design intent. Component contracts own reusable public UI surfaces. Composition documents own application Screen and Shell assemblies, while a Component contract can embed a Composition implementation without surrendering its identity.
Catalog manifests establish ownership and discovery boundaries. Catalog validation resolves cross-Catalog references and joins Components, Compositions, Behaviors, tokens, and target declarations into one checkable graph.
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
Projection and runtime layer
Generators translate validated authority into target-specific interfaces, implementation inputs, examples, documentation facts, and package contents. React and Flutter remain distinct rendering environments while their contracted surfaces converge.
Behavior and motion semantics execute in a shared Rust core exposed through WebAssembly for TypeScript hosts and native FFI for Dart hosts. Target adapters connect platform events and rendering to that shared authority.
Sources for block 1: projection-norms, shared-runtime-topology
Delivery layer
Packages, Git dependencies, native carriers, and generated bundles are delivery surfaces. A consumer uses a released channel and compatible versions; a contributor works against authored authority and proves the resulting projections before publication.
The generated Catalog and Design System bundles report current package facts. They describe implementation availability, while the contracts and specifications describe normative meaning.
Sources for block 1: catalog-bundle, design-system-bundle
Sources for block 2: product-catalog-term