The Changelog That Cannot Be Forgotten

Every working session on this site ends with a written record: what changed, what caused it, what we learned, and where the evidence lives. That record has existed for months. It had one flaw: it was internal. Whether an improvement ever reached the public depended on a human remembering to publish it. Memory is not a mechanism, and describing your own system by hand is how descriptions rot.

As of August 5, 2026, publishing is no longer memory dependent. Two rules govern it.

First, the same action rule. A change that alters how this site publicly works is not considered done until its public entry is written, in the same working action as the change itself. An entry deferred to later is an entry that never gets written, so later is not allowed. Purely internal changes are recorded too, in a separate internal track, with a single test deciding the split: would a reader asking how SleekNova gets better at catching errors care about this? If yes, it is published here.

Second, the session start check. Every working session begins by checking whether any written entries are still waiting to be imported. If any are, they are surfaced again, every session, until they are live. An entry can be delayed. It cannot be forgotten. The check sits inside the same boot routine that orients every session, so skipping it would mean skipping the routine everything else depends on.

The pages that describe our system now read this record live instead of restating it by hand. When the system improves, the description improves with it, and the dated entries underneath are the proof. This entry is the first one produced by the mechanism it describes.