› initializing interface
› mounting modules
● online
~/architecture
Seven production architectures: a personal multi-agent OS run by Claude Code, distributed microservices, multi-tenant SaaS, and engineer-built automation. Every node was extracted from the real codebases, not sketched.
built on Claude Code
The brain of the whole system is Claude Code. The orchestrator is an interactive Claude session that fans work out to custom Skills via the Agent tool; email watchers spawn headless claude -p workers; the mobile bridge runs the Claude Agent SDK; MCP servers wire it into the vaults. I build with Claude, not just on top of a model API.
These seven diagrams were generated and verified by Claude Code multi-agent workflows: one sub-agent authored and rendered each diagram, then independent agents audited it against the real codebase and knowledge base for accuracy and reviewed the render for legibility. This page was built by the system it documents.
Every domain as a column, every shared platform drawn once as a capability band. Scan down a column to see what a project depends on; scan across a band to see who shares a platform. This is how five very different systems compose into one engine.
An always-on multi-agent operating system run by Claude Code. The orchestrator fans work out to custom Skills via the Agent tool; systemd-timed watchers spawn headless claude -p workers; a layered memory (session → project → vault) compounds research and ops. Local models on an RTX 3080 handle the free tier; the iOS bridge runs the Claude Agent SDK.
A polyglot, event-driven recording platform built for graduate distributed-systems work (CAS 735). Six services across Node and Python, each a hexagonal ports-and-adapters bounded context owning its own data, choreographed over a RabbitMQ topic exchange plus a dedicated work queue for FFmpeg media processing.
Four roles (member, instructor, admin, platform owner), each with distinct authentication and capabilities, gated through a single pipeline: role-scoped JWT → edge middleware → multi-tenant subdomain routing → app-level studio isolation. The isolation boundary is enforced in the data layer by a scoped-Prisma wrapper, not by database RLS.
The same product traced by data movement: a synchronous request spine (booking, auth, card checkout) split cleanly from a durable, event-driven async tier (payment webhooks with HMAC verification, Inngest functions, scheduled cron, realtime push). One shared serverless Postgres, every row studio-scoped.
Engineer-built automation for an operations role: an email-triggered, fail-closed document pipeline. A systemd timer claims each thread exactly once via a Gmail-label state machine, spawns a detached Claude worker that validates or generates documents, writes a markdown ledger, and replies on the same thread. Idle cost is zero. (Genericized: no employer internals.)
A resume-tailoring ML product with paying users. A JWT-gated request enqueues a durable, step-checkpointed Inngest pipeline that drives the OpenAI Responses API with Zod-validated structured outputs. Shown sparse on purpose: only the publicly self-reported stack, nothing inferred.