eye-eye-ai

Anatomy of a Claude Code Request** is a live **3D Architecture Map**: it turns software architecture into a navigable 3D model where motion and visual effects *carry meaning* — colour is category, glow is activity, wireframe-vs-solid is build status, particles along a conduit are data flow, an orbiting satellite is an AI agent at work. You fly through the system, swap **Lenses** (Logical ↔ Deployment ↔ Request-flow), and watch AI-proposed changes light up their "blast radius" before you approve them. The map's subject is **how a Claude Code request actually works** — your prompt travelling from the terminal, down through the API/serving layer, into the GPU inference fleet, and back as streamed tokens. The architecture shown is an honest *common-sense model*, not leaked internals, and that's the whole thesis: > a 3D map lets you reason **spatially about any system** — even a black box you > can't read the source of. It's deliberately self-referential — the demo visualises the very pipeline that generated it. **The meta angle (our headline):** this project was **built by a fleet of Claude Opus 4.8 agents** running in parallel, conducted by a human director through a custom tmux orchestration. The build process is itself part of the story — a human directing a team of AI engineers, each in its own worktree, coordinating only through a shared "seam." See §7. + all-Docker on a DigitalOcean host behind a shared Caddy.