The deployment pipeline is the publish button

There is no publish button for these notes. No save-draft state, no preview mode, no scheduling. I write a TypeScript object, add it to an array, commit, and push. GitHub Actions runs lint, typecheck, and 41 tests. If everything passes, the site deploys. The note is live. That is the entire publishing workflow. It works because the content and the code are the same thing. The notes array is type-checked — if I misspell a field name or forget a required property, the build fails before anything deploys. If a note has a malformed date string, TypeScript catches it. The CI pipeline that validates the checkout flow also validates the blog. Every note in this section went through the same pipeline as every feature commit. Same branch, same tests, same deploy. The friction is so low that writing a note takes less time than opening a CMS. That is not an accident. The whole system was designed so that documenting the work is part of the work, not something separate that happens after.