The written change note: the only legal door from research into production.

The rule

One sentence in the QA section carries the whole directive.

Among the maintenance and upgrade rules sits the operative clause: do not promote EV Lab or scenario-profile results into live rules without a written change note. Everything else about the prime directive describes a boundary; this describes the gate through it. The requirement is not approval by a committee, or a waiting period, or a statistical threshold — it is a document. That is a lower bar than most governance frameworks impose and it is chosen deliberately, because a bar an operator will actually clear every time is worth more than a rigorous one that gets bypassed under pressure.

Why writing works

The artifact converts a drift into a decision.

Undocumented adoption does not feel like a violation while it is happening. It feels like an operator gradually becoming persuaded — consulting the new profile for one decision because it seemed relevant, then another, until the live system is running on a rule nobody ever decided to adopt. The written note interrupts that specific mechanism, because it is impossible to drift into writing a document. Producing the artifact requires stating what is changing, which forces the change to have a boundary, a date, and a rationale that can be read back later by someone who no longer remembers being persuaded.

The reconstruction problem

Without the note, a bad quarter cannot be diagnosed.

Consider a system three months into underperformance. The diagnostic question is whether the market changed or the system did — and answering it requires knowing what the system was during the period under review. With change notes, that is a lookup: these rules were live, changed on these dates, for these stated reasons. Without them, the operator is reconstructing their own past decisions from memory, at exactly the moment when memory is least reliable and most motivated. The note costs a few minutes when things are calm and is worth a great deal when they aren't.

• The note dates the change — so before/after evidence can be separated cleanly.
• It states the rationale — so a failed change can be distinguished from a failed reason.
• It bounds the scope — so it is knowable which results were produced under which rule.

The adjacent rule

Never overwrite formulas to force a desired result.

The QA section pairs the change-note rule with a blunter one worth reading alongside it: never overwrite formulas to force a desired result — fix upstream inputs or formulas properly. Both target the same underlying temptation from opposite ends. The change note stops a research finding from entering production informally; the formula rule stops production from being edited into agreement with what the operator wanted to see. A system where either is routinely violated will keep producing numbers, and the numbers will keep looking reasonable, and none of them will mean anything.

The scale point

This is the rule that makes the framework transferable.

For a solo operator, change notes can feel like bureaucracy performed for an audience of one. But the artifact is what turns a personal trading practice into something that can survive being handed to someone else, audited by a prop firm, or picked back up after a six-month gap. The system's own claim is that it converts discretionary trading into governed trading — and the difference between the two is largely whether the rules that were operating at any given moment can be established after the fact. Undocumented rules are not governance; they are habits with good intentions.