the reading room

every essay here gets typeset by the same small set of machinessidenote 11 the pipeline lives in one script — obsidian note in, typeset page out. this footnote is itself part of the demonstration.. this piece exists to run all of them at once — partly so you can see the room, mostly so i notice the moment any of it breaks.

the shape of the room

prose sits at a 560px measure. wide enough for a thought, narrow enough that your eyes never lose the return trip. headings are the serif; everything structural is the mono.

margin voices

footnotes don't live at the bottom of the page here. on a wide screen they step into the right margin beside the sentence that called themsidenote 22 like this one. if you're reading it in the margin, you're on a wide screen; if you tapped to open it, you're not.; on a phone they fold inline and open on a tap. either way you never lose your place.

a fenced block

code comes through the same pipeline, colored from the site's own palette at publish time — the page ships zero highlighting javascript:

// classify the garden's tiers
const TIERS = ["seedling", "budding", "evergreen"] as const;
function classify(tended: string, planted: string): string {
  const moved = tended > planted;
  return moved ? "tended" : "planted";
}
console.log(classify("2026-07-23", "2026-07-01"));

figures in the field

images ride the vault pipeline — optimized at publish, captioned in the small voice:

growth, eventually

this piece is a seedling. when it gets tended, the growth log will appear right below this section — dated one-liners, oldest first, nothing hidden. that's the whole idea of the garden: the revisions are the proof of care.