Agent middleware wraps the RawAgent and context providers, atop a swappable ChatClient pipeline
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
Agent Layer
• Middleware wraps every run with pre and post hooks
• The RawAgent holds the core agent loop
• Context providers inject memory before the model call
Client Layer
• The ChatClient is a separate, swappable pipeline
• It is the only component that talks to the model
• Swapping clients never touches agent logic
Why It Layers
• Agent concerns and transport concerns stay independent
• Middleware composes without editing the RawAgent
• The model endpoint is reachable only through the client
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