Product modes
Match evidence grammar to the work at hand.
Use the comparison to choose the right density, proof object, and persistence boundary for ComplyEaze, Axal, Pack, or Tools.
Four modes · no fifth Sanchika product mode- Rendered example
- AX-031 is rendered four ways below.
- Contract / API
- @sanchika/patterns productPatternContracts
- Limit
- Sanchika is the system beneath these products, not a fifth product mode.
- Failure state
- If a product cannot preserve its evidence or persistence boundary, it is not a valid mode fit.
Compare operating character
| Mode | Work character | Dominant proof | Persistence | Meaningful edge |
|---|---|---|---|---|
| ComplyEaze / core | Focused publication | Product route map with a compact review excerpt | No gallery persistence; route choice only | Unavailable route with an inspectable reason and safe alternative. |
| Axal / workspace | High-density desk | Three-pane ReviewDeskPreview | Workspace-owned record and audit history | Blocked work when source evidence cannot be opened. |
| Pack / local utility | Sequential custody proof | LocalArtifactFlow with receipt | User-controlled browser download | Permission denied with a visible manual portal path. |
| Tools / browser-local artifact bench | Scannable directory | Local ToolDirectory with complete no-JavaScript inventory | Browser session and user-downloaded draft only | No results and failed output with reset or safe retry. |
One record, four rooms
AX-031 changes shape without losing responsibility.
The record identifier is intentionally repeated; the product job, persistence boundary, and proof object change around it.