Skip to main content
SanchikaEvidence contracts
Primary navigation
Search Source

Adoption

Adopt one controlled surface, then prove the boundary.

Use the artifact path to take one narrow consumer surface live while retaining ownership of product copy, authorization, real evidence, and rollback.

Current stable v0.1.1 · No next package release is currently announced.
Rendered example
The consumer order and tarball route are rendered below.
Contract / API
v0.1.1 GitHub tarballs: @sanchika/tokens, @sanchika/primitives, @sanchika/patterns
Limit
A gallery example is not consumer adoption or production authorization.
Failure state
Without a recorded consumer verification and rollback result, adoption remains unproven.

Known consumer order

  1. 01ComplyEazeFirst controlled public/product surface
  2. 02AxalProtected workspace after public foundation proof
  3. 03PackLocal-first utility; no taxpayer upload assumption
  4. 04ToolsBrowser-local drafts after bounded tool specs

Package artifact method

@sanchika/tokens

@sanchika/tokens

Import only package entrypoints. CSS follows token → primitive → pattern order when needed.

Read package documentation
@sanchika/primitives

@sanchika/primitives

Import only package entrypoints. CSS follows token → primitive → pattern order when needed.

Read package documentation
@sanchika/patterns

@sanchika/patterns

Import only package entrypoints. CSS follows token → primitive → pattern order when needed.

Read package documentation

Current acquisition path

GitHub artifact release

Install the reviewed v0.1.1 tarballs.

The stable release provides tokens, primitives, and patterns as GitHub assets with checksums and file inventories. The packages are not published to npm.

Inspect v0.1.1 release evidence
Controlled evaluation

Prove a narrow consumer surface first.

Record the artifact URLs and checksums, import only public entrypoints, and keep rollback explicit. A reviewed local link remains suitable for repository development.

Use the adoption evidence record

Public, protected, and compatibility boundaries

Public first

Start with a public/product surface that needs no auth, tenant data, document handling, or workspace behavior.

Protected later

Axal adoption requires real authorization, tenant isolation, persistence, source handling, and audit evidence outside this public gallery.

Compatibility

Stable package entrypoints and one-release legacy adapters are preserved. Release tarballs are v0.1.1; private source manifests deliberately remain 0.0.0.

Rollback

Restore the v0.1.0 GitHub assets and exact overrides, regenerate the lockfile, and rerun package-backed verification. Package rollback does not require database, DNS, or workspace migration.

What remains unproven

Real consumer adoption remains incomplete. Broad external adoption, every framework adapter, full protected-workspace depth, every assistive technology, and production behavior across all four consumers remain outside this static evidence. See the adoption evidence template and per-consumer guidance before claiming rollout.