The studio that earned its trust

Labels used throughout. [MEASURED] — a number from a run or a capture in the pack. [FACT] — a file or command you can check. [OPINION] — the argument, mine.

This site is a static publication. A post is a folder with a post.md, a build turns it into dist/, and a deploy copies those bytes to a box. That is the whole machine [FACT, build.mjs]. The boring part was never the writing; it was the handoff between the writing and the bytes.

For a year the handoff was a folder and a command. Rename a post, forget to remove status: draft, paste raw HTML into a body, and the build tells you by name. The build is a good gate. The folder was not: every publish was a small manual operation with no review, no provenance, and no way to see the exact delta before it shipped the whole site.

So I built a studio. A local Node process on the Mac at 127.0.0.1:8790 that lists every post with its real state, edits front-matter and body, previews through the real site server, and publishes through the same build → verify → deploy path I run by hand [FACT, docs/STUDIO.md]. That is a different trust category from a static generator. The studio can write files, commit content, and push production. A tool like that does not get to say “trust me”; it has to show the evidence.