Sonnet 5 executor + Opus 5 advisor: where the tokens and dollars go (measured, Claude Code v2.1.226)
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
Two Opposing Forces
• Savings: most output is generated at Sonnet rates
• Overhead: every call re-reads the whole transcript uncached
• Break-even is a race of absolute amounts, not ratios
Uncached Input Dominates
• Advisor-side cache_read was 0 on every call
• Per-call input grew 53,210 to 77,611 tokens as the chat grew
• The advisory response itself stays small (2,828 output tokens)
Measured Outcomes
• Short task, 1 call: +25% vs fixed Opus ($1.238 vs $0.993)
• 435-line refactor, 2 calls: -15% ($3.094 vs $3.646)
• No calls at all: 43% cheaper than fixed Opus
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