Selected · CA review needed
Sanchika · a working collection
Make regulated interfaces that show their work.
Sanchika gives coding agents and engineers a repeatable way to turn source, uncertainty, and human review into clear, accessible product UI.
It supplies contracts and a review loop—not compliance judgment, customer evidence, or an application runtime.
01 · Decision proof
Leave room for the human who must decide.
AX-031 keeps a linked synthetic source, an interpretation boundary, and a named CA checkpoint visibly separate.
Settled proof shown. Motion is optional.
Work queue
Priority orderWaiting · Evidence requested
Ready · Source linked · Due soon
GST notice
The extracted difference is visible, but interpretation remains with the assigned CA reviewer.
- Owner
- AK · CA reviewer
- Due
- Due 18 July 2026
- Source state
- Source linked
- Synthetic exposure
- ₹12,48,900 synthetic exposure
- Automation
- Draft assistance only
- Blocker
- None recorded for the selected synthetic item
- Next safe action
- Open the linked source before deciding
CA decision required before the response advances.
Approve, revise, or request evidence only after opening the linked synthetic source.
- Preparation
- Draft assistance only · review needed
- Owner
- AK · CA reviewer
- Evidence
- Source linked · open before deciding
- Blocker
- None recorded; hold if the source cannot be opened
- Next safe action
- Open the linked synthetic source
- History
- 09:42 · audit trail retained below
02 · Range without sameness
One grammar. Four working conditions.
ComplyEaze, Axal, Pack, and Tools keep evidence legible while changing density, custody, and the next safe action.
Four operating modes
Related by evidence. Different by work.
Sanchika holds typography, boundaries, source grammar, and focus behavior steady while density and proof objects change with the product.
ComplyEaze / core
Choose the operating boundary before work begins.
Editorial clarity and professional calm for a public product family.
- Boundary
- The page explains account, upload, custody, and review before routing.
- Proof
- Product route map with a compact review excerpt
Axal / workspace
Keep source, owner, blocker, and judgment in one review path.
Owner AK · source linked · blocker none · next: open source
Open the workspace proofPack / local utility
Trace custody from the portal response to a user-controlled file.
- GST Portal session
- Pack local action
- Chrome Downloads
No handoff: Credentials, session cookies, and downloaded files do not transfer to ComplyEaze.
Trace local custodyTools / browser-local artifact bench
Find a bounded draft tool by the work on the desk.
- Notice response outline Drafting
- Evidence index Documents
- Due-date sheet Dates
Edge: no match → clear filters; output fails → retain input and retry safely.
Find the local tool contract03 · Method
Contracts first. Craft loop clearly labelled.
- TokensSet semantic color, type, focus, and motion roles.
- PrimitivesDefine finite states and accessible behavior.
- PatternsCarry the boundary into a product-shaped job.
Local index
Find the contract behind the interface.
Generated from routes and package metadata. No request, tracking, or external index.
61 routes
No contract matches that search.
Try a product mode, component, state, or boundary.
04 · Current truth
Useful, bounded, and still in review.
- Release
- v0.1.1Tokens, primitives, and patterns are the stable package set. No next package release is currently announced.
- Proof
- Synthetic AX-031The gallery demonstrates contracts, not customer evidence.
- Adoption
- ComplyEaze firstAxal, Pack, and Tools remain separate adoption work.
- Next action
- Inspect a contractThen test it in the consumer that owns the runtime.