2019issue C0159
Treat mechanical system listings as specification audits
A systems directory is a research starting point, not a ranked shortlist. A mechanical trading system becomes usable only after its automated signals, markets, software needs, and support are written as one testable entry, exit, and abstention procedure.
- A mechanical trading system replaces discretionary interpretation with automated signals from preprogrammed rules, whether delivered as software, a live signal service, or a published rule set.
- Use a specification checklist on every vendor listing: indicators, markets, extra applications, support, and primary features must form one testable entry, exit, and abstention procedure.
- The directory is a research starting point without track records or rankings, and click order measures site interest rather than system quality.
- Vendors remain responsible for their listings, which are stated as accurate at publication and may change later.
A listing describes a procedure, not a pick
A trading system is presented as a way to replace discretionary interpretation with automated signals generated from preprogrammed rules. An automated signal is a buy or sell instruction produced by those rules rather than by discretionary judgment.
A mechanical trading system is a complete procedure that maps rule inputs, market state, and execution constraints into entry, exit, or abstention signals. The TradersWeek editorial reading is that a listing is useful only when that full procedure can be inspected.
Delivery form does not complete the design
A system may be implemented as computer software, as a live signal service, or as a published rule set that a trader follows. A live signal service is a real-time feed that issues system signals instead of requiring the user to execute the rules locally. A published rule set is a documented procedure a trader can follow without running dedicated system software.
One system may draw on a single method or several, including machine-based techniques, classical chart methods, indicator collections, or custom rules. The TradersWeek editorial reading is that delivery form and method mix are description facts. They do not, by themselves, show that entry, exit, and abstention are specified as one procedure.
Use a specification checklist
Evaluation is framed around inspectable design facts: which indicators are used, which markets are covered, whether extra applications are required, what support is offered, and what the primary features are.
The TradersWeek editorial reading treats those questions as a specification checklist. A vendor listing is a self-submitted product description. It becomes a candidate for testing only when those facts can be written so the mechanical trading system can be run as one procedure.
Click order records traffic, not quality
The directory is described as a research starting point and does not include track records or comparative rankings of listed systems.
A most-clicked product list is identified as a measure of site interest rather than an editorial rating of system quality. Click order is a popularity sort based on how often listings were opened. It is distinct from any quality rating.
Vendors remain responsible for their own listings. The publisher disclaims endorsement of the businesses and individuals shown. Posted listing details are stated to be accurate at the time of publication and subject to later change.
All readings on this track · 22 readings
- 1985Treat a shared mechanical printout as a public script
- 1988Pessimistic margin ranking for mechanical systems
- 1991From a differenced-average sketch to coded rules
- 2003Commodity enthusiasm is not a complete system
- 2005Reader surveys as system evaluation checklists
- 2008Critiquing unchanged mechanical signals in evolving markets
- 2010Read a mechanical trading system catalog as a specification checklist
- 2011Specify mechanical system signals as one testable procedure
- 2012Treat a packaged mechanical system as one inspectable procedure
- 2013Mechanical trading systems as complete signal procedures
- 2013Testable cycle rules as one procedure
- 2014Evaluate mechanical trading systems as one procedure
- 2015Mechanical trading systems as one testable procedure
- 2016Evaluating mechanical trading systems as testable procedures
- 2016Reading a systems catalog as one mechanical procedure
- 2018Mechanical systems as testable signal procedures
- 2019Treat mechanical system listings as specification audits
- 2019Match the automation stack to mechanical system constraints
- 2019Bar size as a mechanical system construction constraint
- 2020Interrogating mechanical system listings as one procedure
- 2020Mechanical systems still need emotion rules
- 2020Comfort, not theory, keeps mechanical rules in use