ClientServer channel — an independent runtime per channel
process X connects to auth and report separately · the client starts the connection
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
Verified source
Authored reach
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
Semantic radar needs more MAP space.
An independent runtime per channel
• process X holds an auth Client and a report Client, making an independent runtime per channel that manages the auth connection and report connection separately.
• auth and report don't share connection targets or lifetimes. Even when the same process Z takes part in both channels (Z1·Z2), each channel runtime manages its connection to Z separately.