The previous post had a tidy ending. Meeting notes were riding along with the calendar event itself, and the week's review finally had outcomes in it instead of just a list of rooms I had sat in. It shipped, it ran, the demo filmed. And then I opened a meeting that actually matters and the drawer was empty.
A recurring meeting I care about. The notes exist, a running document updated every week. The calendar event has nothing attached and nothing written in it. The link lives in the invite chat, or in someone's memory, or nowhere. The note was real. The calendar did not know where.
One Link Field
The obvious move was a notes app: index everything, full-text search, tag meetings, a sidebar. Each is a rabbit hole that ends the same way, a new surface to secure, a new copy of my data, a new thing that breaks at 3am. I have built that app and been paged for it. So the real question was smaller: a meeting has notes, the calendar does not know where they are, and I do.
The answer was one link field. Paste it, Almanac checks the doc is there and I can open it, then pulls the three things that matter, what was decided, what is open, what someone has to do. No new app, no second copy. And because a recurring meeting has one running doc but a dozen calendar entries, a pin on one follows the whole series, so last week's entry carries last week's notes where the review looks. The work was never the pin; it was making the pin land where the reading happens.
Local, and That Is the Point
The document never leaves my account. Almanac reads it with the same access it already has for the calendar, keeps the three things that matter, and drops the rest. Nothing is copied to a third party, indexed by someone else's search engine, or trained on. The estate is small apps on my own machine talking to my own accounts. I keep writing this like a constraint I am working around; it is the design. Local and private is why this exists. A cloud notes app would close the gap faster and cost me the only part of the system that is actually mine.
Just Enough Is a Discipline
The suite is eight apps now, and the thing that ties them together is not a stack or a protocol. It is a habit of asking how small a change can be and still close the gap. The pin is one link field. Following the series is one small step so the pin lands on every instance. None of it would impress anyone on a feature list. All of it made a meeting I care about show up in my week.
Just enough features is not minimalism for its own sake. It is the only way I have found to ship eight apps by myself and still have them talk to each other. Every feature I do not build is a feature I do not maintain, secure, or explain. The ones I do build have to earn their place by closing a real gap with the least wiring that can hold.
Next week's review will start with what that meeting decided last week. That is the whole point.