27d • Releases
How updates work: one release a month
Everything you install here keeps getting updated. This post explains exactly how, so you know what you are paying for.
When: the first working day of every month. Predictable, so you can ignore it the rest of the time.
Where the updates come from: I use this system every working day on real client work. When something breaks, when a better route shows up, or when a task keeps needing the same correction, I fix it in my own system first. Those fixes are what you get. This is not content written for a course, it is a system that gets sharpened by use.
How to get it: type update my Brain. Your agent fetches the new version, tells you in plain language what changed, and runs any migration for you. About two minutes.
What an update never touches: your notes, your cards, your board, your own rules. Only the system folder gets replaced. That is why you never have to check anything before updating.
Why monthly and not weekly: updating costs you something every time, however small. Weekly gets ignored after a month or two, and then everyone is running a different version and helping each other becomes impossible. One good release beats four thin ones.
Want it sooner? There is an edge channel that moves continuously, for people who like being first and do not mind the occasional rough edge. Say so in Q&A and I will switch you over.
Quiet months happen. Some months bring three real improvements, some bring one. I will tell you which it was rather than dress up a small change as a big one. A quiet month means the system is stable, not neglected.
Every release gets one post in this category: what changed, and what it actually saves you.
0
0 comments
How updates work: one release a month
