@sanchika/tokens
OKLCH theme variables, semantic roles, and motion variables.
tools.complyeaze.com/sanchika
Sanchika design-system docs.
Sanchika is the package family for shared compliance UI tokens, primitives, workflow patterns, and reviewable gallery examples across ComplyEaze surfaces.
Static documentationNo account requiredNo file upload requiredReviewable package contracts
Packages
Package scope stays narrow.
Each package has one reason to change. Consumers should be able to adopt tokens, primitives, patterns, or gallery examples independently.
@sanchika/primitives
React-ready contracts for accessible base components.
@sanchika/patterns
Compliance workflow patterns for evidence, review, and source posture.
@sanchika/gallery
Inspectable examples for package consumers and reviewers.
Adoption
Adopt from private product surfaces outward.
The order keeps public surfaces conservative and avoids turning Tools into a persistence, collaboration, or workflow product.
| Step | Adoption rule |
|---|---|
| 1 | ComplyEaze uses Sanchika first for internal compliance UI conventions. |
| 2 | Axal follows with workflow surfaces that need shared review posture. |
| 3 | Pack adopts only portable contracts that preserve its no-login extension boundary. |
| 4 | Tools adopts public documentation and utility surfaces after Pack. |
Verification
Package output must be reproducible.
Sanchika changes should pass package validation, API type checks, consumer checks, tarball checks, and the combined verification gate.
pnpm validate
Required before treating package output as ready for consumers.
pnpm typecheck
Required before treating package output as ready for consumers.
pnpm build
Required before treating package output as ready for consumers.
pnpm typecheck:api
Required before treating package output as ready for consumers.
pnpm artifact:check
Required before treating package output as ready for consumers.
pnpm consumer:check
Required before treating package output as ready for consumers.
pnpm publish:tarball-check
Required before treating package output as ready for consumers.
pnpm verify
Required before treating package output as ready for consumers.
Trust boundary
Keep public claims tied to current artifacts.
The public route documents the package family and its boundaries. It does not promise future components, official certification, or product persistence.
Docs before claims
Public docs describe what exists now, not future support.
No tenant data
Packages must not read credentials, clients, documents, or workspaces.
Managed history
Repository settings and branch protection stay reproducible.
Reviewable output
Built artifacts and tarballs must be reproducible by consumers.
Review the package source before adopting it.
The Sanchika repository is the source of truth for package contracts, branch protection, generated artifacts, and publish checks.