1991issue C021-7
A fuzzy membership checklist for trade signals
Build the trade decision as one graded pre-trade checklist. Score every rule input on a 0-to-1 membership scale, collapse those scores with a single min or max step, and only then decode a crisp enter, exit, or stand-aside signal so the whole procedure can be tested as one rule.
- Fuzzy decision scores occupy the interval from 0 to 1, so a market condition can be treated as partly true to that degree instead of only true or false.
- AND combinations take the min operator and OR combinations take the max operator, collapsing left-hand-side scores into one rule membership before any action is decoded.
- Defuzzification reverses the same membership table used in fuzzification, reading the action score back to a crisp instruction.
- Editorial: treat scoring, the min-or-max collapse, and the final decode as one pre-trade checklist so enter, exit, and stand-aside stay testable as a single procedure.
One checklist from score to signal
A pre-trade checklist is a single procedure that scores rule inputs against market state, combines those scores, and maps the result to an enter, exit, or stand-aside signal. Fuzzy decision scores occupy the interval from 0 to 1, so a market condition can be treated as partly true to that degree instead of only true or false.
The archive workflow keeps those steps inside one rule path. Inputs are scored first. The scores are then collapsed. Only after that collapse is a crisp instruction read out.
Scoring inputs with membership functions
A membership function is a 0-to-1 mapping that states how fully a crisp observation belongs to a linguistic label. It maps a crisp reading onto that scale by assigning 1 at the designated typical value, 0 outside the accepted band, and interpolated scores in between.
A second-order curve is often used in place of a straight line while keeping the same 0-end, midpoint, and 1-end. Fuzzification is this conversion of a measured market variable into membership scores on linguistic sets.
Production rules in an elementary expert system
An elementary expert system is an inference engine plus a knowledge base of if-then production rules. The knowledge base is the collected production rules that the inference step consults. The inference engine is the module that presents current data to the rule set and decides which rules fire.
A production rule is an if-then statement pairing a condition set with a conclusion the procedure may execute. The left-hand side is the condition portion that must be satisfied before the rule fires. The right-hand side is the conclusion portion that becomes a candidate action when the rule fires. A rule fires when every left-hand-side condition holds, and the right-hand side then becomes a candidate for execution.
Fuzzy rules and the min-or-max collapse
A linguistic label is a graded category such as positive-big or negative-big used in place of a binary true-or-false flag. A fuzzy production rule requires crisp inputs such as price and a price-to-earnings ratio to be converted into linguistic labels before it can fire. One demonstration rule sets the action to negative-big when both inputs belong to the positive-big set.
AND combinations take the min operator, which returns the smallest membership among the conditions. OR combinations take the max operator, which returns the largest membership among the conditions. With a price score of 0.5 and a ratio score of 1.0 on positive-big, the rule membership and the action membership are both 0.5.
Reading the action back to a crisp instruction
Defuzzification is the reverse lookup that turns an action membership score back into a crisp instruction. It reverses the same membership table used on inputs, reading the action score back to an index and then to a crisp instruction.
A spreadsheet with linguistic columns and real-world rows can serve as both the fuzzify and defuzzify interface. Editorial: keep that decode after the min-or-max collapse, so enter, exit, and stand-aside remain outputs of the same checklist rather than separate true-or-false checks.
Membership tables and the generator
Membership tables may be linear or curvilinear and either sigmoidal or bell-shaped. The usual seven labels run from positive-big through zero to negative-big, and neighboring curves should overlap so no value in the variable's range is left unlabeled.
A membership-function generator can build those tables from user-specified 0-edge and 1-edge points, automatically choosing which side of a sigmoid is high, joining opposite sigmoids to form a bell, and writing a seven-column matrix of labels against indexed crisp values.
Stated construction advantages
Stated construction advantages of this checklist form include encoding verbal expert statements as executable rules, simple programming on modest hardware, and execution speed associated with real-time applications. Smaller rule sets and smoother control actions are also asserted.
Editorial: those points are construction claims from the archive workflow. They are not a performance record and they are not a present-day market claim.
All readings on this track · 135 readings
- 1987Pair each checklist step with its decision state
- 1987Position secrecy as decision-process control
- 1987When profits break the trading process
- 1988Treat action-seeking as a veto before any signal
- 1988Entry, exit, and abstention as one practiced procedure
- 1988Making inner conflict a testable trading rule
- 1988The chart is only half the trading procedure
- 1988Negotiate conflicting parts before the signal
- 1989Commitment turns trading rules into one procedure
- 1989Confidence, discipline and the fit of a trading procedure
- 1990Encoding expert hunches into a mechanical trading loop
- 1991The consecutive-loss halt as the trading system
- 1991A fuzzy membership checklist for trade signals
- 1991Overconfidence as a skipped pre-trade checklist
- 1991A source-reliability audit for trade signals
- 1991Shared rules fail without an execution checklist
- 1991The daily study block as a low-risk checklist
- 1992A bear-market loss review that rewrites the pre-trade checklist
- 1993Unspoken beliefs that veto system rules
- 1993Why a mechanical system beats betting harder when the story looks cheaper
- 1993A usable process over a perfect trader standard
- 1993Remold the decision-map after a traumatic trade
- 1994Keep entry, exit and sit-out as one procedure
- 1994Pre-trade gates for belief and state
- 1994Known failure points inside the yen triangle phase checklist
- 1994When a comfort ceiling, not market state, is the failure mode
- 1994Trading commitment as a balanced decision process
- 1994Constructing a pre-trade discipline checklist
- 1995Futures systems start with whether to trade
- 1995Stopping points as checklist and stop failures
- 1995When analysis and execution must become one procedure
- 1995A decision-process database from analyst to trader
- 1995Decisive execution as one tested procedure
- 1996The unfinished-system trap in simple decision rules
- 1996When risk breaks practiced system execution
- 1996Treat the mechanical signal as a draft, not a decision
- 1996Critique of decision states that break system rules
- 1996State-gate checklist for trading decisions
- 1996Personality-fit rules before earned intuition
- 1996The commitment gap as a testable decision process
- 1996Test decision style as one trading procedure
- 1997Mechanical trading before subjective judgment
- 1997Belief checklists that invalidate mechanical systems
- 1998Mechanical rules against mindtraps
- 1999The profit target as a trading discipline lens
- 1999When mechanical rules replace judgment in the trade process
- 1999Trading discipline as one testable procedure
- 1999Daily pre-open map as one procedure
- 2000Session veto from daily readiness
- 2000Anger buildup as an untested system input
- 2000Construct separate research and live-trade question checklists
- 2000Operator-state as a first-class trading rule
- 2001Day-trading rules need a pre-trade decision process
- 2001Review the operator before you rewrite the plan
- 2001Critique of the informal trading pause
- 2001Specificity turns wishes into checkable trading rules
- 2002The pre-entry plan that locks exits and size
- 2002Risk identity as a pre-trade system gate
- 2002When elapsed time rewrites trade rules
- 2002One written system, faster exits, and the belief gate
- 2003Countable decision trees for entry and abstention
- 2003Constructing a pre-trade stop and review procedure
- 2004Psychological wounds that override a tested system
- 2004A hot streak does not retire the trading checklist
- 2005Why mechanical trade plans fail without execution discipline
- 2005Resentment as a construction input for trade decisions
- 2005A daytrade as one written procedure
- 2006Write the pre-trade plan as one procedure before entry
- 2006When a winning streak makes the trade checklist optional
- 2007An entry needs a pre-trade risk bound and a post-trade debrief
- 2007A pre-session futures plan that locks entries, exits, and stops
- 2007Maxims fail without one testable procedure
- 2007Personality-fit and holding horizon before the pre-trade checklist
- 2008Push-button systems versus a testable decision process
- 2008Written rules omit the operator and the implicit filters
- 2008A Pre-trade checklist before emotion takes over
- 2008System design between the mechanical black box and checklist judgment
- 2008Trade history as a checklist for entry, exit, and abstention
- 2008Mechanical rules without a decision process
- 2008Parable checklists for entry, exit and abstention
- 2010Keep rule-based entries clear of news bias
- 2010Self-control zones before the pre-trade checklist
- 2010Treat the pair-desk day as one testable procedure
- 2010Use a five-factor checklist instead of pattern labels
- 2010Listed currency futures versus spot forex as a pre-trade venue checklist
- 2010Rule overload, unfinishable checklists, and tight stops
- 2010Pre-trade checklist versus automatic stops
- 2010Skipping signals after a losing streak is a new system
- 2010Stand aside until the relationship breaks
- 2010A software catalog fails the checklist without one testable procedure
- 2011Checklist rules versus unwritten indicator judgment
- 2011The handoff test for self-coached trading plans
- 2011Unify locate status, written rules, and self-talk on one checklist
- 2012A pocket card and a setup-chart as the session-plan
- 2012Close system construction with a review checklist
- 2012A pre-trade checklist versus in-trade emotion
- 2013The ten-question alignment gate when traders lose the path
- 2013A stuck-point audit for stalled trading decisions
- 2013Why rule-based entries need false-trigger checks
- 2013One procedure for liquidity rules and abstention
- 2013The month-open window is unfinished without cash default and a substitution checklist
- 2014Waiting fails when the pre-trade checklist is too wide
- 2014A swing procedure with a checklist, layered stops, and an emotion handoff
- 2014System design as a critique of forecast-worship
- 2014Consultant hiring as an accept-or-abstain checklist
- 2014One procedure for entry, exit and abstention
- 2014A trading system that cannot decide before the chart opens
- 2014The checklist veto when tools override the plan
- 2014Write the holding-period style before any daytrading rules
- 2015A pre-trade checklist when volatility turns rules into panic
- 2015A checklist, psychology gate, and moving-average procedure
- 2015Write forex entry and sit-out rules before you score the links
- 2015Daily if-then checklists versus year-ahead market forecasts
- 2015Workstation readiness in the pre-trade execution checklist
- 2015An unprepared trade fails the pre-trade checklist
- 2015Evaluate a system with one pre-trade checklist
- 2015The pre-trade checklist as one testable procedure
- 2015News-aware forex process with defined stops
- 2016Slow thinking over gut feel in complex markets
- 2016When a market-structure story rewrites a checklist yes
- 2017Constructing an options trading-plan from a self-inventory
- 2017A price-first checklist for noncooperative market games
- 2017A pre-trade risk checklist versus profit-first thinking
- 2018A forex onboarding ladder is not a decision process
- 2018Pre-trade regret scripts for entry and abstention
- 2018Audit the plan while the tape stays forgiving
- 2018Constructing a sortable pre-trade checklist
- 2018Forex myths that break a testable decision process
- 2018Why trading checklists must beat inherited confidence
- 2019Leverage as a pre-trade gate in mechanical systems
- 2019Critique of impulse trading as a testable system
- 2020One checklist for breakout entry, stops, and sitting out
- 2020A continuity checklist for a blank Sunday-night system desk
- 2020After an extended bar, the checklist must still be able to refuse
- 2020Write one procedure before outsourcing system decisions