Know what local work carries—and what it does not.
This is a public reading surface for people who need the browser-local boundary before they need a component catalogue.
How this route should be read
A local artifact is useful precisely because its limits stay visible.
Source
The Sanchika gallery and source repository show the interface contract behind this page. They are public material to inspect, not a claim about a visitor's files or work.
Draft
Tools can shape a browser-local working artifact. It does not turn a draft into a filing position, authority decision, or stored client record.
Export
A clear label helps a practitioner choose what leaves the browser. A saved trail, assignment, or recurring workflow belongs to Axal.
Public proof, not a product workspace
The contract can be inspected without asking anyone to trust a hidden system.
- This route is
- A static explanation of how the Sanchika contract helps a public Tools surface communicate source, draft state, and export boundaries.
- This route is not
- A filing result, a compliance conclusion, a client vault, an audit trail, or an account area.
- When work persists
- Use Axal for a saved workspace, collaboration, assignments, and recurring operating flow.
Inspect the contract. Keep custody explicit.
The gallery shows the current interface evidence. The repository makes the underlying design-system work reviewable.