A request crosses independent layers from TLS at the edge to OpenTelemetry
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
Layered Ingress
• TLS, WAF/auth, and input screening are separate stages
• Each stage can fail closed on its own
• No adjacent pair shares one point of failure
Guarded Core
• Policy gate scopes tools before the agent runs
• The agent executes sandboxed, never trusted
• Output guard applies DLP and PII scanning after
Shared Evidence
• All layers emit to OpenTelemetry
• Audit trail spans the full crossing
• Eleven layers total; the hot path shows the core eight
Architecture 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