← all topics
→
###/topics/architecture5 posts
kevin@toronto:~/topics/architecture $ cat *.md | head
Architecture.
5 posts tagged Architecture. Newest first. /posts for the full archive with live search.
How I Know All 36 Agents Are Alive Right Now
The file-based heartbeat layer I use to detect quiet agents, separate warnings from resets, and keep a 36-agent fleet observable.
→
How My 36-Agent Fleet Is Wired Up
A diagram-heavy look at the router, dispatcher, workers, heartbeats, cost controls, and trust tiers behind my 36-agent OpenClaw fleet.
→
Multi-Agent Orchestration: Routing Work Across 36 AI Agents
How work actually flows through a 36-agent fleet: 5 routing flows, channel rules, escalation paths. Not theory — production config.
→
The Architecture Behind My 36-Agent AI Fleet (Across 5 Companies)
Not a concept piece. A working system: 36 agents, 5 brands, 24/7, at $2.48/agent/day. Gateway, orchestrator, specialist layer, free fleet, memory — all of it.
→
How I Organize Multi-Agent Output Without Losing My Mind
36 agents produce a lot of files. Without a routing system, everything ends up in the wrong place and nothing is findable. Here's the file strategy that keeps it sane.