# SUDX Adoption Guide

## Prove

Start from a real workflow and verify the need in a product.

## Ratify

Extract only the reusable behavior, accessibility contract, and visual law.

## Publish

Add the rule to canonical SUDX sources and regenerate the published bundle.

## Adopt

Read `/design/assets/manifest.json` and the laws. Copy `sudx-tokens.css`,
`shadcn.json`, and `shadcn.css` locally as the required foundation, then copy
only the recipe files for adopted families. Never import SUDX assets at
runtime.

Create consumer-owned adoption and evidence records beside those local copies.
The adoption record names the required foundation, adopted recipe families,
product-local extensions, and accepted deviations. The evidence record pins the
manifest digests the consumer actually copied, then records the consumer
commit, configuration, lockfile-resolved environment, tests, and rendered QA.
The central `shadcn-evidence.json` is attestation, not a file for a consumer to
copy and edit.

## Verify

Run the consumer's own tests and rendered QA for every adopted family. Unused
families carry no compatibility claim. Record all local additions or
deviations and give every deviation a stated action, so an open record says
what closes it and a settled one says why it stands.