A solo studio has a problem no team has: when you sleep, everything sleeps. Until this week, this whole operation (two products, a book, a knowledge base) ran on one laptop being open and one person remembering things. That was the thing we set out to kill.
The shape of it now
The studio grew a nervous system: an always-on agent that senses (commits, application errors, cloud health), a drop-box where automations deposit work for each other, and a publishing pipeline with a human hand on the last switch. Every piece is small; the point is the wiring.
Publishing without a build step
The part that unlocked the rest: posts on this site aren't "built." A post is one object in storage, rendered at request time — so publishing, the thing that used to mean a laptop, a toolchain, and a deploy, is now this:
// shipping a reviewed post = moving one object
await bucket.put(`posts/${date}.html`, draft.body);
await bucket.delete(`drafts/${date}.html`);Any agent that can write one file can publish (into a review queue; a human still ships). That single design choice is why the rest of the mesh could be assembled in days, not weeks.
Watchers, not operators
The monitoring half is deliberately boring: read-only watchers that turn application errors and cloud health into a quiet daily note instead of a 3am surprise. Nothing in the mesh can change production — it can only tell us to.
Fittingly, the pipeline described above produced the post you're reading. Inaugural output, machine-drafted, human-shipped.