Design lab
Where the system is forked safely. An experiment overlays token values, component CSS, or motion on a real registry component and renders inside its own sandbox — the canonical system stays untouched until Publish promotes the change. The lab is currently all clear.
Fork a registry component to start an experiment. Each fork lives in its own sandbox: token overrides, scoped CSS patches, and per-experiment motion. Publish promotes — or scopes — every draft change.
See how distribution worksRetired
Published experiments and forks decided against. The retired ledger doubles as a published-as audit trail: every entry records whether each draft change landed globally or stayed scoped.
No retired experiments yet.
How the next experiment works. A new fork enters as a LabsExperiment with one or more draft changes. The sandbox renders it
against the canonical system without touching it. Publish (next) classifies each change,
shows the blast radius, and lets the operator promote each change globally or keep it scoped
to the experiment. The canonical registry only mutates for promoted changes.