Writing.
Notes from running an agent fleet as coworkers. Multi-agent systems, fleet operation, infrastructure underneath. New pieces shipping as I finish them.
Every long-running agent lives in a detached tmux session named after its job. Six months of fleet operation distilled to one rule.
Token saturation is the only signal that matters. Wall-clock time, idle time, vibe, all decoys.
A SQLite-backed memory layer agents can write to and retrieve from across sessions, providers, and machines.
The recursive structure that lets a single architectural rule survive across sessions, providers, and tier boundaries.
From single-prompt user to fleet operator: the eight components of a personal AI OS, and what shipping each one taught me.
For solo developers and agent-driven sites, vanilla HTML beats React, Next, and Astro. The framework tax is hidden until you remove it.
Three of the four CLIs and servers I run every day are now Rust. The fourth being JavaScript is my fault, not its fault.
A 200-line Rust binary that does literal substitution between HTML comments. Smaller than every templating system I've used.
Most CMSs treat HTML as a build output. Freedom CMS edits the HTML file directly via contenteditable, autocommits to git. No database, no schema, no build step.
A memory layer for AI sessions: MCP-backed local SQLite, semantic retrieval, lifecycle tiers, and conflict detection. How and why I built context-vault.
A folder tree as agent configuration, three orchestration layers, and a self-improvement loop where agents log friction that becomes the next round of issues.
The first overnight run of an autonomous agent orchestrator: 686 cycles, 11 merged PRs, 8 self-healed stalls, and 94% idle time. What worked, what didn't, what's next.
A CLI orchestrator that turns AI agents into long-running workers against a GitHub backlog: a 3-layer master/workspace/project model with a vault-backed feedback loop.
A practical Git workflow for vibe coding with AI: clean branches, atomic commits via git add -p, intent-driven messages, and PR review as the final gate.
Three things I wish someone had told me when I started Webflow eight years ago: use Relume for layouts, follow Client-First for class naming, and switch to REM units.