Field note
How to read a Solana runtime release note in order
A Solana runtime release arrives as a tag, a list of merged changes, and a feature-gate section that may activate on a later epoch than the day the binary is published. Readers who start in the middle tend to blend “this is in the code” with “this is live.” The binders in Jeongeup exist to keep those two moments apart.
The order on the runtime shelf is fixed. First the short summary at the top of the release. Second the feature-gate list, with a pencil mark beside anything scheduled rather than already active. Third the notes that mention RPC methods, account layouts, or default flags an operator would notice in logs. Fourth the previous annotation in the runtime binder, so a warning already recorded is not written again as if it were new.
Only then does the reader write three lines in their own words: what activates, what their role has to do before the next epoch boundary they care about, and what can wait for a later sitting. A line that cannot be supported from the document stays blank. Memory and side threads do not fill the blank.
Agave notes and any second client the shelf is tracking are read as separate documents, even when both claim to follow the same consensus behavior. Differences in logging and default flags belong in the margin. A blended summary hides the flag you would actually change.
When the three lines still feel shaky after that pass, the change is a better fit for an update briefing than for another late reread. Bring the blank line with you. The ninety minutes start there.