Frontend request path with auth, cache fallback, persistence, and async trace
Guided views
Explore this system
Step through curated paths without changing the source diagram.
Beat
Next
ReadyChapter 01 / 01
Guided chapter
Diagram guideExplore this system
Inspecting compiled semantics
E ExportT ThemeS Style0 Reset+ Zoom in- Zoom outEsc Close
Find a node
⌕/
No matching nodes
Semantic passport
Route probeChoose a start node
Pick two semantic nodes on the diagram
Choose the source, then the destination. Direction matters.
Semantic lensCompare system roles
Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.
Choose a kind to inspect its nodes and touching relationships.
Semantic radar
Building overview
Click nodeDrag to pan
Happy Path
• The main request is Web App -> API -> data source -> response
• Return messages are quieter than forward calls
• Activation bars make ownership duration visible
Policy + Fallback
• JWT verification is colored as a security interaction
• Cache miss is visible without overpowering the main path
• Database access only appears after cache fallback
Async Trace
• Trace emission is dashed and secondary
• It does not block the response path
• The diagram separates user-facing latency from observability
Sequence diagram • Built with Archify • Create yours ↗ • Hover to trace • R route • Click to focus • +/− zoom • M radar • [/] views • P play story • T theme • E export