What has to be written down before a process can honestly be called systematic? This note lists those parts, using a momentum ranking on the Russell 2000 as the public example, and keeps the list separate from any claim about results.
Systematic, in this note, means that a second person can carry out the steps from the writing alone and can tell whether they were carried out. It does not mean complicated, and it does not mean successful. A hunch with a spreadsheet is not systematic merely because the spreadsheet has many columns. A simple ranking is systematic if the ranking rule, the data version, the clock, the costs that were or were not included, and the decision to stop are all written down. The writing is the process. The code is evidence that the writing was followed, not a substitute for it.
The policy reason is review. A reviewer cannot approve a mood. A reviewer can check a text against a log. If the text is missing, the review is theater. Writing the process down also makes retirement possible. A rule that was never specified cannot be removed, because nobody can say what was running. Removal is part of a systematic process, not an afterthought for rules that embarrass the author.
A systematic process is a written procedure a second person can follow and check, including the data clock, the rule, the search that was tried, and the conditions for stopping.
A momentum ranking on the Russell 2000 can be specified without being endorsed. The writing would name the index and the point-in-time membership, the trailing window, the treatment of missing prices, the day the rank is formed, and whether costs are inside or outside the picture. It would say how many variations were tried before this window was the one being shown. That paragraph is the process. A chart without the paragraph is a picture. Policy asks for the paragraph before the picture is used in any discussion that sounds like a decision.
The example is public so the requirement does not depend on a secret formula. If a process only feels systematic when the reader cannot check it, the feeling is secrecy, not system. Secrecy about a position is a different topic and is not created by refusing to write the research steps down inside the firm. Internal writing is how the firm knows what it did. External pages are a separate choice, governed by /legal, and they do not have to contain the internal text in order for the internal text to exist.
Personal information does not belong in the write-up of a market process. The Russell ranking does not need a name attached to each row. Hiring files, web logs, and mail stay out of it, under the handling described at /privacy-policies. A systematic process that requires a personal identifier to run is a sign that the process is no longer about the public index in the example.
A complete write-up can describe a rule that should be retired. Completeness is not an argument for keeping it. The policy is that decisions refer to a text, and that texts which fail their tests are marked as failed. A later reader should find the failure easily. Buried failures are how the same process gets rewritten under a new name.
Writing down a systematic process means producing the text a second person can follow, illustrated here by how a public index ranking would have to be specified. It does not mean the ranking is used, and it does not change the site's terms. Those remain at /legal and /privacy-policies.
This piece does not claim that a momentum ranking is a strategy, that a written process has worked, or that this page states a legal status. A spreadsheet with many columns is not a written process, and a chart without the rule is not one either. See /legal and /privacy-policies for the site's governing text. The ranking example stays a classroom for how specific the writing has to be before anyone calls the work systematic.