Rulebook v2.2 · Engines v10

The specification is written first. The code implements it second.

Most screeners are a pile of filters with a story attached afterwards. StockFaves works the other way round: the rulebook is written and argued over, every rule is given an identifier and an evidence grade, and only then is an engine built to execute it. When code and rulebook disagree, the rulebook wins and the code gets fixed.

5rule engines in production
~750NSE & BSE names scored
4independent decision axes
0discretionary overrides