The Fifteen-Minute Monthly Refresh
10 min read
A stale Brain is worse than no Brain. With no Brain, the assistant asks questions and you notice the gap. With a stale one, it answers confidently from facts that stopped being true in June, and the wrongness arrives dressed in your own voice, quoting your own old prices, easy to miss on a busy day. The whole one-document design converts your maintenance job from "keep five skills current" to "keep one file current," and this lesson is that job.
The first-Monday ritual
On the first Monday of each month, before anything else in your Monday block, spend fifteen minutes on four steps:
1. Rewrite Right Now (five minutes). Delete last month's section entirely and write this month's from scratch. Deleting first matters: editing invites you to keep sentences that no longer apply. New promotions, closures, staffing gaps, anything with a date in the next six weeks.
2. Sweep for changed facts (five minutes). Walk the other five sections with one question: did anything here change last month? Prices, a new service, a policy you adjusted after that one awkward customer call, a voice rule you have been breaking on purpose (which means the rule is wrong, not you). Fix what you find.
3. Date and log (two minutes). The Brain's first lines are a changelog. Add one line per change:
## Changelog
2026-08-04 Service call $139 -> $149. Added fall promo.
2026-07-01 New red line: no install dates promised in
vacation windows. Right Now rewritten.The changelog is how you will later answer "when did we start quoting that?" in ten seconds, and it is the first thing to check when an output looks wrong.
4. Archive the old version (one minute). Copy last month's file to `/archive` before saving the new one as `brain-2026-09.md`. Old Brains are cheap to keep and priceless the one time you need to reconstruct what a skill was told in March.
The spot-check
Once a quarter, add a five-minute test to the ritual. Open a fresh conversation, paste the current Brain, and ask three questions you know the answers to cold:
Based only on this document:
1. What would you charge for [your most common job]?
2. What do we promise about [your firmest policy]?
3. What promotions are running this month?You are not testing the assistant. You are testing the file. A wrong answer with a current Brain means a section is ambiguous or contradicts another, and that discovery costs you five minutes here versus a mispriced quote in the wild.
Event-driven updates
The monthly ritual catches drift; some changes cannot wait for it. Adopt one standing rule for yourself and anyone else who touches prices or policies: the change is not done until the Brain knows. Raised a rate? The task has two steps now, and the second one is a one-line edit plus a changelog entry. This is the same discipline as "the job is not done until it's invoiced," applied one document further down.
The rule earns its keep at handover time too. In Chapter 6, when your office manager runs the workflows, "update the Brain" is a task you can assign, audit, and cover during vacations, because it is a file edit, not a telepathy session.
The failure mode to respect
The Brain does not fail loudly. It fails the way a bulletin board fails: one outdated notice at a time, until one day nobody trusts anything on it and everyone goes back to asking you directly, which is the exact situation the system was built to end. Fifteen minutes a month is the entire price of avoiding that. It is the least glamorous habit in this course and the one we would defend last.
Try it now
Put the recurring appointment in your calendar now: first Monday of each month, fifteen minutes, titled "Brain refresh." Then run the quarterly spot-check today on the Brain you wrote in the last lesson, with your three questions. Yes, you wrote it this week; test it anyway. A fresh Brain that fails the spot-check is telling you a section is unclear, and unclear is the seed drift grows from.