Each harness pattern is written behind an interface — a seam — with an offline local implementation swappable for an Azure-backed one, turning a bare model call into production agent infrastructure
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
One Contract
• Every pattern hides behind an interface
• The seam is the single swap point
• Callers depend on the contract, not the backend
Two Implementations
• Local impl is deterministic and offline for CI
• Azure impl is the managed production backend
• Swapping one for the other changes no caller
Seven Seams
• Model, memory, tools, and identity behind seams
• Policy, telemetry, and checkpoint behind seams
• A bare model call becomes production infrastructure
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