Giving a Rule Set a Version Number

With even one undated edit in the file, every comparison a review makes is between two different systems wearing the same name. The running record orb trading review consultoriainnova holds is versioned for that reason alone, since a strategy for the opening range accumulates small amendments faster than anyone remembers making them, and a sample that spans three quiet changes to the entry rule is not a sample of anything.
What Counts as a New Version

Any change that would alter which trades are taken or how they are sized. A new filter threshold, a different timeframe for the range, a changed stop loss method, a revised position sizing formula. Cosmetic edits to the wording do not count. The test is simple: run the old rules and the new rules over last month and ask whether the trade list differs. If it does, the version number moves.
The Minimum Viable Scheme

Two numbers and a date. The first number increases when the entry or exit logic changes, the second when a threshold moves within the existing logic. The date is the first session the version was in force. That is enough to tag every entry in the trade journal and to slice results by version afterwards, which is the only thing the scheme has to support.
Tag the Trades, Not Just the File
A version number that lives only at the top of the rules document is nearly useless. It has to appear on each logged trade, because the question a review asks is always about a subset of results. One extra column does that. Without it, separating out the trades taken under the current rules means reconstructing dates from memory, which is where the errors come from.
Sample Size Resets
The uncomfortable consequence of versioning honestly is that a change to the rules resets the count. Forty trades under the previous entry model do not tell you much about the new one. That discomfort is the point, since it makes the real cost of a small adjustment visible: another two months before anything can be said about whether it helped.
Keep the Old Versions
Superseded rule sets stay in the file with their dates. They are the only record of what was actually being run when a given stretch of results was generated, and they answer the question a later review will ask about why a period looks different. Deleting them saves nothing and destroys the ability to interpret your own history.