Why the user is choosing a route.
public-product pattern
ProductRouteMap
Compare workspace, local utility, and browser-local routes without flattening their boundaries.
complyeaze/core · candidate · @sanchika/patternsProduct job
Choose the correct product route by persistence, custody, account, upload, and review needs.
Compare workspace, local utility, and browser-local routes without flattening their boundaries.
Anatomy and required fields
Highest-context route with live proof preview.
Alternative product modes.
Account, custody, upload, and review distinctions.
Named destinations for each route.
Availability or limitation for each route where applicable.
Optional evidence attached to a route claim.
Sanchika evidence path without forcing it into the product list.
- routeSummary
- primaryRoute
- secondaryRoutes
- boundaryLabels
- routeActions
- currentStatus
- colophon
Default and edge states
All documented routes are available.
- product names
- operating modes
- boundary labels
Routes retain priority and boundaries in a narrow composition.
- primary route
- bounded alternatives
- next actions
A route is available with a named limitation.
- limited
- scope
- fallback
A route needs a reason and fallback.
- unavailable
- reason
- fallback
The design-system evidence path is shown outside the peer product routes.
- Sanchika
- evidence link
- not a product route
Composed synthetic exemplar
Primary workspace
Axal
3 items need reviewReview client obligations with sources, owners, and human approval visible.
Workspace account · saved client contextInspect the Axal review deskReview queue
CA review needed
Synthetic entity A · Due 18 July 2026Evidence requested
Synthetic entity B · Evidence requested 14 July 2026Due soon
Synthetic entity C · Due 20 July 2026Local utility
Pack
Move supported filed-return files into Chrome Downloads on this device.
Local browser action · no file uploadInspect Pack proofBrowser-local drafts
Tools
Create a first draft for a specific compliance task without an account.
No upload · professional review requiredInspect Tools proofState coverage
Default and consequential edges remain inspectable.
Trust, source, and consumer obligations
- Do not imply government affiliation, guaranteed outcomes, or unstated production readiness.
- Name account, upload, local-processing, external-destination, and human-review boundaries before action.
- Supply current product copy, sources, destinations, prices, review ownership, and all runtime behavior.
- Stack routes in priority order on narrow screens.
- Keep each boundary label with its route action.
- Retain labelled boundaries, native link underlines, focus outlines, and status text without authored color.
- Keep all claims, proof, boundaries, and actions visible without entrance or layout motion.
Compact API reference
- Package
@sanchika/patterns- CSS
@sanchika/patterns/styles.css- Base class
sk-pattern-product-route-map- Group
public-product