Observable behavior · permissions · interruption ladder
6Z Trading Psychology: A Behavioral Control System
Moving a stop because “the market just needs room” can look like discretion. If the wider level was not permitted before entry, it is a rule breach. Useful psychology starts by separating the trader's internal story from observable state and allowed action.
Translate feelings into controls
Separate Internal State, Market State and Account State
Internal
What the trader experiences
Urgency, frustration, fear of missing out, attachment to a thesis, fatigue or the desire to win back a loss. Record it without treating it as a signal.
Market
What can be observed
Price, quote direction, spread, depth, event timing, data freshness, order status and contract lifecycle.
Account
What constrains permission
Open quantity, realized and unrealized loss, correlated exposure, margin, cash buffer and daily interruption state.
| Story | Observable question | Control |
|---|---|---|
| “It has to come back.” | Is the frozen invalidation true? | Exit under the declared branch; do not widen |
| “I will miss the move.” | Does spread, depth and event state pass now? | No pass, no order |
| “I am trading well today.” | Is quantity still within the fixed budget? | Profits do not authorize size escalation |
| “One more trade fixes it.” | Has an interruption threshold fired? | Lock new risk until recovery criteria pass |
| “The stop was hunted.” | What were trigger, arrival, fill, spread and depth? | Diagnose execution from records, not attribution |
Make the hard decision while flat
Build Permissions That Leave Little Room for Bargaining
Session permission card
- Allowed instruments
- Exact 6Z expiries and account; no continuous-chart orders.
- Risk cap
- Per trade, open portfolio, day and event limits in dollars.
- Entry permission
- Named setup plus data, spread, depth, time and event gates.
- Modification
- Which orders may change, by how much, for which observed reason.
- Interruption
- Loss, deviation, fatigue, technology and execution-error triggers.
- Restart
- Objective evidence required before new risk is re-enabled.
- Default is disabled. New risk requires affirmative evidence.
- Quantity is externally visible. The ticket, risk sheet and journal must agree.
- Protection cannot be weakened. A modification may reduce risk only under a prewritten rule.
- Outcome cannot change classification. A profitable breach remains a breach.
Design out unnecessary temptation
Make the Trading Environment Enforce the Plan
Willpower is a weak primary control because it is most needed when attention is already impaired. Interface design, permissions and alerts should make the authorized action easy to see and the unauthorized action difficult to perform.
| Risk | Environment control | Acceptance test |
|---|---|---|
| Wrong contract | Hide unused expiries; display full month/year and ZAR/USD orientation beside the ticket | A simulated wrong-month order is blocked before submission |
| Oversizing | Quantity defaults to zero and cannot exceed the approved risk output | Changing quantity causes a fresh calculation and authorization |
| Stop weakening | Alerts or order permissions flag increased open risk after modification | A wider-stop test disables the submit action |
| Event impulse | Calendar buffer automatically disables new entries and shows the named source | Orders remain blocked until the explicit restart state |
| Loss chasing | Session loss and deviation counters lock new risk at the declared threshold | Restart cannot occur from a timer or application relaunch alone |
| Duplicate exit | Position and open-order reconciliation precedes every manual backup order | Rejected or delayed acknowledgements trigger review, not blind resubmission |
Accessibility is part of control quality. Critical state should not be encoded by color alone; use text labels, symbols and clear focus states. Risk values need readable units and enough contrast. Keyboard-only operation should preserve the same confirmations as pointer use. Alerts must identify the contract, side, quantity, reason and required action rather than merely making noise.
Before the session
Reduce decision load
Load the verified expiry, calendar, risk limits and checklists. Remove unrelated instruments and disable order shortcuts that bypass confirmation.
After the session
Review control friction
Record warnings ignored, blocks triggered, repeated fields and near misses. Improve the system without weakening a gate merely because it was inconvenient.
A script, alert or order template is not authoritative simply because it is automatic. Version it, test it and provide a fail-closed fallback. If control state is uncertain, disable new risk.
Stop escalation early
Use a Four-Level Interruption Ladder
Name the trigger
Urgency, repeated ticket editing, missed data check, rising spread or uncertainty appears.
Disable new orders
Reconcile positions and open orders; preserve protective exits.
Remove exposure
Follow the declared impairment branch if risk or operational state is no longer controlled.
End risk for the session
Triggered by hard loss, repeated deviation, unresolved technology or inability to complete the checklist.
New risk remains disabled until position, orders, data, market quality, account state and decision record are reconciled. Time alone does not repair missing evidence.
Restart is earned
Apply a Recovery Protocol After a Breach
- Flatten or stabilize.Resolve unintended exposure and open orders using the prewritten operational branch.
- Freeze the record.Save screenshots, order messages, timestamps, prices, quantity and the rule version before explanations change.
- Classify the failure.Mechanics, sizing, execution, event, technology, evidence or behavioral-control failure.
- Repair the control.Make one versioned change that would have prevented or contained the incident.
- Test without risk.Replay or simulate the workflow until the control behaves as intended.
- Return at reduced permission.Only if restart evidence passes; size does not automatically return to the prior level.
Measure behavior like any other process
Audit Permissions, Deviations and Near Misses
| Metric | Definition | Use |
|---|---|---|
| Unauthorized-order rate | Orders sent without every required gate divided by all orders | Hard control quality |
| Modification rate | Post-entry order changes by allowed and disallowed reason | Bargaining detection |
| Interruption latency | Time from trigger to new-risk disablement | Containment speed |
| Residual exposure time | Time unintended quantity remained after detection | Operational severity |
| Near misses | Breaches caught before exposure | Leading indicator, not success to hide |
| Outcome-independent adherence | Rules followed regardless of profit or loss | Prevents luck from training bad behavior |
Weekly output
Keep, repair or disable the process
Do not respond to a losing week by inventing a personality label. Use the audit to locate the failed permission, measurement or execution control, then test the repair prospectively.
Sources, methods and editorial disclosure — reviewed August 25, 2026
- CME Position and Risk Management for predeclared risk, stop and account controls.
- NFA Investor Best Practices for risk-capital, leverage and margin-call context.
- 6Z mechanics authority for contract and quote controls.
This page is an operational decision framework, not mental-health treatment and not evidence that 6Z has a fixed psychological “personality.” It reports no original trading-performance result.