Building with AI The Vibes Don't Scale Vibe coding works great for the first few PRs. Then you do it two hundred more times and the codebase quietly stops making sense. The fix isn't better prompts — it's building a machine that compounds.
Swamp Skills Are Context, and Context Needs Tests Skills are context. They're the thing an agent reads before it decides how to use swamp. If the skills are wrong, everything downstream is wrong — so we test them in CI the same way we test code, using tessl for quality and promptfoo for routing, across every model we care about.
Swamp The Lifecycle of a Swamp Issue We use swamp to build swamp. That sounds like marketing until you look at how an issue actually moves through our process — not as a GitHub thread with comments piling up, but as a state machine with versioned plans, adversarial reviews, and checks that refuse to let the agent skip steps.
Swamp Execution Drivers in Swamp Swamp model methods can run anywhere — directly in the host process, in a Docker container, or in a custom driver you write yourself. This post covers how execution drivers work, how config cascades from model to workflow to CLI, and how to build your own.
Swamp How We Built Datastores in Swamp Swamp tracks everything at runtime — model state, workflow runs, audit logs. For a while that lived in .swamp/ in the repo. It fell apart the moment we wanted a team sharing state. So we built a proper datastore abstraction with S3, distributed locking, and a local cache.
Swamp Deploying Ghost on DigitalOcean with Swamp I asked Claude to build me a blog on DigitalOcean and it worked hand in hand with Swamp to build one!
ai Featured AI: Why I'm All In I'm an AI maximalist, and I think operations is about to get left behind: again. This blog is about closing that gap from the inside.
