Iris & Argus
Ten diagrams of how Luke's AI setup fits together: Iris, an assistant that runs as Claude Code on his PC; Argus, a second agent in WSL; the Brain that keeps working between sessions; and the Premier systems they read from. Each diagram opens in its own tab and is interactive.
The whole setup
How Luke reaches Iris, what Iris works on, and what keeps running when no session is open. Most boxes here have their own diagram below.
Open the overview →The detail diagrams
Numbered in reading order
Iris core
What every Claude Code session loads, how hooks and skills steer it, and the ~31 MCP servers it reaches.
A session's life
One session from grounding to close, and how its lessons become next week's start pack.
Memory
How every turn is kept, distilled into facts and a journal, and read back through one router.
Telegram
A message from Luke's phone to a full Claude Code session and back, and how alerts reach him.
Iris Brain
The always-on scheduler: 45 jobs, a watchdog, code that replaces itself, and quiet telemetry.
Control Centre
Luke's desktop cockpit: one local server that gathers the Brain, memory and services, and can act on them.
Argus
The sister agent in WSL: her models, Honcho memory, 35 crons, and how she and Iris talk.
Premier data
Read-only access to Premier's systems, and the cashflow app, portal and intranet pages built from them.
Plumbing
Scheduled tasks, Windows services, Docker and WSL, and how health reaches Iris each morning.
Reading a diagram
- Click a boxHighlights everything it connects to and shows its details.
- Play storyWalks through the diagram's main paths one step at a time.
- Amber cardsKnown issues found while mapping, left in on purpose.
- Light / DarkThe toggle at the top right of each diagram.