2013issue C0176
Mechanical trading systems as complete signal procedures
Treat a packaged mechanical trading system as one testable procedure. Write the entry, exit, and stand-aside rules first, then use a vendor listing only to compare rule inputs, markets, and execution constraints.
- A mechanical trading system issues buy, sell, or stand-aside signals from rules specified in advance, in place of discretionary interpretation.
- The same mechanical procedure may be delivered as software, as a live signal service, or as a written rule set followed by hand.
- Compare systems as designs by rule inputs and execution constraints, not by how often a listing is opened or by vendor copy.
- A catalog built from vendor listings can inventory options without publishing track records or editorial rankings.
Write the rules before you compare products
A mechanical trading system can replace discretionary interpretation by issuing buy and sell signals from rules specified in advance. It is a complete procedure that turns predefined rules, market state, and execution constraints into entry, exit, or stand-aside signals.
Editorial reading: treat a packaged system as that one procedure, not as a bundle of marketing claims. Write the entry, exit, and stand-aside rules first. A signal is a buy, sell, or stand-aside instruction produced by specified rules rather than by discretionary interpretation.
The procedure can arrive in more than one form
The same mechanical procedure may be delivered as software, as a live signal service, or as a written rule set followed by hand. Editorial reading: the delivery form does not change what has to be specified. The procedure still has to produce a signal from rules, market state, and execution constraints.
A system may combine more than one analytical discipline, including indicator collections and custom rules, rather than depending on a single technique. Editorial reading: the design question is whether those parts are written as one advance procedure.
Compare systems as designs
Comparing systems as designs requires asking which indicators they use, which markets they cover, which companion applications they need, what support is offered, and what their primary features are.
Those questions map to rule inputs and execution constraints. Rule inputs are the indicators, market coverage, companion applications, and other stated conditions a system needs before it can issue a signal. Execution constraints are practical limits such as required software, supported markets, and available support that determine whether the written procedure can be run as designed.
Editorial reading: use a product catalog only to compare those inputs, markets, and operating constraints. Do not treat click traffic or vendor copy as a test of the procedure.
A catalog is an inventory
A catalog of systems can be assembled from developer- and vendor-supplied descriptions without publishing track records or editorial rankings. Vendor-supplied system descriptions can change after posting, and the listing operator does not endorse those descriptions or accept liability for them.
An inventory of trading-system options can sit alongside related categories such as brokerages, data services, education, and software. Editorial reading: that placement puts systems next to other operating choices. It does not rank them.
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