The archive is the studio's notebook. Dispatches when we ship something, notes when an idea is too short for an essay but too useful to keep private, essays when the topic earns the room.

We're keeping the editorial register restrained on purpose. Short sentences. Plain English. Posts that respect the reader's time and don't oversell. If a release note can be three paragraphs, it will be three paragraphs.

What you'll find here

  • Dispatches — what we shipped this week, what changed, what's next. Quick to read.
  • Essays — longer pieces on craft, the writing process, the intersection of writers and AI. The front of the book.
  • Notes — single observations. A quotation worth keeping, a craft tip we picked up, a small idea.
  • Releases — version notes for product changes. For existing users who want the receipts.

A note on the format

Every post is a markdown file in the repo. No CMS, no admin UI. We write, we commit, it ships. Authoring at the cadence of git is the right speed for a small editorial team.

You can read the archive two ways: as a standalone page at /archive, or as a slide-out from any landing page when you click the archive in the nav. Same posts, two surfaces — pick whichever fits the moment.