A common pattern among people who use AI tools regularly: every session begins with a reset. The same preferences re-stated, the same warnings repeated, the same context rebuilt from memory. On a focused morning, the re-setup is thorough and the work is excellent. On a distracted morning, parts get skipped, and quality drops in direct proportion to what was omitted.
The pattern exposes a structural weakness. Quality that depends on what someone remembers to type each morning varies with their mornings. Standards that live only in a person's memory are subject to everything that memory is subject to: fatigue, interruption, competing demands. The AI's context window is well-understood to have limits; the limits on human recall at session start are less often discussed, but equally real.
The fix follows directly from Lesson 5: facts in a poor location belong in a better one. The rules built through Lessons 3 through 6 all belong in a single plain document the AI reads at the start of every session: verify before confirming, check the source, maintain one authoritative location for facts, diagnose root causes before patching symptoms. Most AI tools provide a designated place for this kind of document. Different tools call it by different names: a system prompt, custom instructions, or a profile. The general term for this document is standing instructions: rules the AI reads at the beginning of every session, regardless of what the operator remembers that day.
Once standing instructions are in place, session-to-session variation largely disappears. A focused-morning session and a distracted-midnight session receive the same baseline quality, because neither depends on the operator's recall. When the system produces a new kind of error, the appropriate response is not just to correct it. Apply the Lesson 6 loop, identify the missing rule, and add one line to the document. The standing instructions grow at exactly the places where real use has scraped them.
Over time, a well-maintained standing instructions document shifts the dynamic measurably. The system requires less direct operator input each month, not because the AI has changed, but because every rule learned through experience is encoded in the document and runs automatically. Sessions evaporate when a conversation closes. Rules in a standing instructions document accumulate.
A practical test for any process: does it need less involvement from the person running it each month? If yes, it is functioning as a system. If it needs the same amount of involvement or more, it is a habit wearing the name of a system. The purpose of building standing instructions is to make that shift.