A panel on the desk, dressed as a mailbox: folders, a message list, and the letter itself. Almost none of it is real. Every letter here was written by me ahead of time, and the folder chrome doesn't do anything but sort them. The one live control is Compose: write a message there and it opens in your own mail app, already addressed to me. That's the real contact form. Everything else is honest set dressing. So read this like a letters page, not a live inbox. The letters are real things I actually did. The inbox around them is the costume.

A short, honest list of the last few things that actually shipped, in case you don't want to dig through the notes for it. The notes list turned into a real feed this week, newest first, sortable by reading time instead of upvotes (I don't have real votes, so I didn't fake them). The calendar next to it plots the same real dates, note publish days and the handful of posts about what shipped, nothing invented. This mail panel is the third piece of that same push, a compose window wearing an inbox's clothes. Before that: PROOF, the plan board this whole stack runs on, went from a static page to something that streams as the work happens. PANTRY's mindmap shipped the same week, a way for an AI already on your machine to read a codebase without running a model of its own. If any of that sounds interesting, the notes feed has the long version.

There's no server behind this site that could receive a message, so send had to mean something else here. The Compose form below builds a mailto link out of whatever you type, then hands your browser to your own mail app with the subject and body already filled in. You press send from your own inbox, which means you also keep a copy in your own sent folder, a small honest side effect I like more than I expected to. The address itself doesn't sit in the page as plain text either. It's assembled from two pieces once the page loads, mostly to keep the simplest scrapers from finding it. If JavaScript is off, the address won't assemble that way, so there's a plain mailto link right in the form's hint text instead. Either path reaches the same inbox.

grain's build ran and came back clean: typecheck, lint, and the component tests, all green, in that order. This inbox doesn't actually watch a pipeline. I wrote this letter the same way I wrote the rest of them, ahead of time, standing in for the kind of mail a real CI system would send. If you want the actual build logs, they live in grain's own repo, not here.

The Pages deploy for this site finished and went live. A push to main, a build, a swap, the same three steps every deploy takes here. Nothing on this page is watching that pipeline in real time. This letter is set dressing, same as the rest of the mailbox, written to fill out what a notifications folder usually looks like.

batch's nightly run finished clean: every binding test and every snapshot passed, nothing flaky to chase down this time. A quiet night like this one doesn't really deserve a letter, but the folder needed a third message from a sender other than The Desk, so here it is anyway.

Nothing lives here yet, because nothing's been sent. If this were a real Sent folder, your message would land here right after your own mail app fired it off, since the actual sending happens over there, not on this site. This row exists mostly so the folder isn't lying about having a Sent folder at all. Write something in Compose and see for yourself: the sending happens in your mail app, not here.

Whatever you're part way through typing lives in the Compose form below, in your browser, in the actual form fields. Nothing here saves a draft server-side, so if you want to keep it, keep the tab open, or paste it somewhere safer. This folder is really just a signpost pointing down at the one place a draft can exist on a static site: the form itself.

The whole site runs on one design system: every surface addressable by a human and an AI through the same shared vocabulary, and the AI's hand stays visible on the page as grain rather than pretending to be a human's clean ink. One vocabulary, one direction. There's more on that over at grain.

PANTRY's whole-codebase mindmap shipped. It's AI-legible, not AI-powered: it runs no model of its own, it just makes a project easy for an agent already on your machine to read. There's more on that over at pantry.