kevin@toronto:~/start $ cat field-manual.md
new here? pick a track.
48 posts. 7 tracks. Pick one — the rest follows. Each track is a themed reading path through the archive — read the top one, then follow the rest in order. Or skip to the full archive if you'd rather wander.
If you read 3 posts, read these.
The strategic ones. What 36 production agents actually costs, what the architecture looks like, what 10 commandments paid for in real failure.
- 01 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.
- 02 Cost-Optimized LLM Routing: When to Use Claude, GPT, Grok, and Free Models Decision tree across 25+ LLM providers. Real cost data. Why I run 200+ models at $2.48/agent/day, and how the free-fleet optimizer routes 80% of work to $0/month.
- 03 The 10 Commandments of AI Infrastructure 10 rules I follow operating 36 AI agents 24/7 across 5 companies. Every commandment paid for in production failure.
How the agent fleet is wired.
Component map, routing, dispatch, heartbeat, dreaming. The actual infrastructure behind 36 agents shipping 24/7.
- 01 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.
- 02 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.
- 03 OpenClaw Evolution: 6 Phases of Building a Self-Healing Agent Fleet Behind-the-scenes log of turning 36 agents from 'held together with duct tape' into self-healing infrastructure. Every phase paid for by a real failure.
- 04 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.
The routing + economics layer.
Why $2.48/agent/day is the right number. How 200+ free models stay in production. When the #1 model stopped mattering.
- 01 Running 200+ Free Models in Production (And When to Pay) Groq, Cerebras, Cloudflare Workers AI, OpenRouter. The escalation ladder I actually use, with cost data.
- 02 Frontier Model Convergence: When #1 vs #2 Doesn't Matter Anymore The top frontier models are now within 3-4 percentage points of each other on SWE-bench. When the gap is that small, model selection becomes a routing problem — not a vendor loyalty problem.
- 03 How I Track 36 Agents' Cost Without Burning Agent Cost A field report on the local-first cost loop I use to track 36 OpenClaw agents, catch spend spikes, and keep the watcher off the bill.
- 04 The Hidden Costs of AI: What SMB Founders Don't See A restaurant owner was paying $847/month for AI tools. The real all-in cost was $1,400. Here's what the subscription stack hides — and the math that actually works.
Daily-driver patterns.
Seven rules that separate sessions that ship from sessions that spiral. Forty-five tips referenced every week. The daily loop that actually works.
- 01 The 7 Golden Rules of Claude Code Non-coder operating 36 agents built these rules from 18 months of production failures. Not theory. The exact patterns that separate sessions that ship from sessions that spiral.
- 02 45 Claude Code Tips I Reference Every Week 45 numbered tips from the BIBLE — the quick reference I built for Claude Code patterns that actually compound. Context management, git, multitasking, and the meta-skills most people skip.
- 03 The Daily Claude Code Loop That Actually Ships The structured daily loop I run across 36 agents and 5 product brands — morning startup, session discipline, context rules, and the HANDOFF.md habit that prevents starting from zero every day.
- 04 Letting Claude Code Run Unsupervised for 8 Hours: A Field Guide What actually happens when you leave Claude Code running overnight — the setup, the checkpoints, the failure modes I've hit, and the security constraints that keep it from going sideways.
Failures + the fixes that followed.
Ten real agent failures with the signals that exposed each. Four shell-injection vectors I caught in my own agents. The config drift that broke a Tuesday morning.
- 01 10 Real Agent Failures + How I Diagnosed Them Ten real OpenClaw fleet failures from my 36-agent stack, the signals that exposed each one, and the preventive fixes I shipped.
- 02 4 Shell-Injection Vectors I Caught In My Own Agents A security field report on four prompt-to-shell injection paths I found while hardening my OpenClaw agent fleet.
- 03 Config Drift Killed My Deployment — Here's the Guard I Built openclaw.json is 139KB of routing + agent config + model aliases. Unauthorized changes break things silently. Here's the SHA256 guard I built after one Tuesday morning broke everything.
- 04 Anatomy of an 87% Dispatch Failure: How One Missing Schema Field Killed Our Agent Fleet 49% of our agent dispatches were failing for three weeks. The bug was one stale field in the adapter.
Methodology — the parts that pay rent.
Systematic debugging without guessing. Operationalize every fix. The decision tree that picks a build type before code is touched. Single source of truth for docs.
- 01 The Iron Law of Debugging: No Fix Without Confirmed Root Cause Every premature fix is a guess. Here's the investigation-first protocol — with the exact prompts, hypothesis-test loop, and operationalization steps — that eliminates repeat bugs.
- 02 Operationalize Every Fix: Turning 1 ESM Bug Into an 8-File Regression Test The patch is the down payment. The sweep is the principal. Pay both.
- 03 Quick / Deep / SaaS / Overnight: How I Pick a Build Type Before Touching Code The decision that happens before any code runs. 4 build types, 4 checklists, 4 model choices. The wrong pick costs days. The right pick costs minutes.
- 04 Single Source of Truth: How 5 Fragmented Docs Became One Canonical Reference Doc rot is a tax on every reader. Pay it down once; collect interest forever.
If you're non-technical, start here.
The 2026 founder's guide to AI. What can be delegated, what can't. Where AI actually pays for itself with 3 SMB cases.
- 01 The Non-Technical Founder's Guide to AI in 2026 50+ AI tools, every vendor promising transformation, none of them explaining what you're actually buying. Here's how to cut through it — no technical background required.
- 02 AI Agent Autonomy Tiers: When to Auto-Approve, When to Wait 4 tiers. 36 agents. A document that keeps them from breaking things they can't fix. What agents can do alone, what needs a human, and what's off-limits entirely.
- 03 Will AI Replace My Job? A Task-Level Analysis of 42 Roles I spent 18 months mapping 42 roles against current AI capability. The answer isn't 'yes' or 'no' — it's task-level. Here's the data.
- 04 Where AI Actually Pays for Itself: 3 SMB Case Studies Not every AI deployment delivers ROI. These three categories consistently do: customer support automation, ad copy generation, and data extraction. Real numbers from realistic operator scenarios.