2005issue C091-3
Resentment as a construction input for trade decisions
Ordinary sessions produce sudden swings of greed, fear, shame, regret, anger, and anticipation for skilled and struggling operators alike. In this editorial reading, post-loss resentment is treated as a missing construction input, so a written belief inventory and a morning rehearsal sit inside the same procedure that reads market state and can emit entry, exit, or abstention.
- Ordinary sessions produce the same swings of greed, fear, shame, regret, anger, and anticipation for skilled and struggling operators; the operational difference is how those states are managed.
- Resentment typically follows a loss when personal responsibility is not accepted, and a resentmentConstraint can divert focus and drain energy even after a small incident.
- Release cannot be issued as a command; it follows an attitudeShift built from a beliefInventory, a check against lived results, and a dailyRehearsal.
- Editorial reading: when resentment is still consuming attention, the same procedure that reads market state should emit an abstentionGate instead of an entry or exit.
Resentment as a construction input
Ordinary sessions produce sudden swings of greed, fear, shame, regret, anger, and anticipation. Skilled and struggling operators meet the same states. The operational difference is how those states are managed.
Editorial reading: resentment is not a side topic. It is a missing construction input. The same procedure that reads market state should also read whether a post-loss grievance is still consuming attention, then emit entry, exit, or abstention from one rule set.
How a post-loss grievance becomes an input
Resentment is treated as an especially toxic state. It typically follows a loss when the operator does not accept personal responsibility for the outcome.
Loss situations that can seed resentment include an interruption at a critical moment, others' market actions, a partnership based on misrepresentation or poor business choices, a purchased system whose stated results do not match later experience, and support work that produces avoidable damage.
After such events, resentment can divert focus, reduce productivity, and drain energy even when the triggering incident is small. Frequent loss makes trading a setting where resentment is especially likely. In this construction the resulting state is the resentmentConstraint: a post-loss emotional state treated as an execution input that can block a signal until focus and energy are restored.
Write a belief inventory first
Release is the last move in the process and cannot be issued as a simple command. It follows from an attitude that is itself based on a belief philosophy. The attitudeShift is a change in operating philosophy that makes release possible. It is treated as a prerequisite rather than a one-step command to drop the feeling.
The self-directed sequence begins by writing truthful answers to prompts about people, life quality, others' reliability, failure, role models, the future, accidents, loss handling, and the world, then checking whether those written answers are actually believed. That written set is the beliefInventory. It surfaces the assumptions that keep resentment inside the decision loop.
Each belief is checked against lived results. An alternative belief is then imagined with all senses and restated in words so a different picture can begin to replace the one that has been dictating experience.
Rehearse the alternative picture each morning
The alternative picture is rehearsed every morning for one month before the eyes open. That dailyRehearsal is a morning visualization of an alternative belief picture, restated in words, used to overwrite the prior loss narrative. Later experience that matches the new beliefs is said to make those beliefs more influential.
The recommended handling is to release resentment so it does not consume positive feeling or energy.
Emit entry, exit, or abstention from one rule set
Editorial reading: the beliefInventory and the dailyRehearsal belong in the same procedure that reads market state and execution constraints. The procedure still produces a signal over the system holding period. The extra input is whether a resentmentConstraint is active.
If resentment is still diverting focus or draining energy, the no-trade output is an abstentionGate. Entry and exit remain available only when focus and energy are restored. That keeps entry, exit, and abstention rules testable as one procedure.
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