Writing
Operating Notes
Repeated work eventually asks for a system.
Not always software. Sometimes the right system is a checklist, a memo, a naming convention, or a weekly review that forces decisions into the open. The useful question is not whether a process is elegant. It is whether the next version of the work gets easier to begin.
I like writing operating notes because they compress lived experience into something another person can test. They are not doctrine. They are a record of what has worked under actual constraints.
A good note should make the next attempt less mysterious.
That is enough of a standard to start with.