Building the Control Plane: How I Made My Infrastructure Programmable
Four Docker hosts and 86 containers with no API meant every operation started with SSH. So I built an Admin API that made containers, GPUs, and alerts programmable.
Read Article
Four Docker hosts and 86 containers with no API meant every operation started with SSH. So I built an Admin API that made containers, GPUs, and alerts programmable.
Read Article
A DR rebuild silently killed all 24 of my MCP servers. I rebuilt 21 of them in a single stack with 207 tools, centralized secrets, and semantic filtering.
Read Article
Before building infrastructure, inventory what the estate already runs — the playwright MCP backend made the browser image unnecessary. And a QA checker's first
Read Article
A vendor config migration is only proven when every leg has a discriminator that fails if the leg is absent — and generated artifacts (lockfiles, extracted tree
Read Article
A workflow is not codified until its scripts are proven against captured evidence from the runs that produced them: bundling replay fixtures (pre-state, post-st
Read Article
An alert pipeline's visible activity is not its action path. This stack runs advisory RCA (a read-only bot posts analysis into a chat thread) alongside a separa
Read ArticleI have run orderly systems for a long time. Across all of it, one thing has been consistently true: the parts of my work I
Read Article