Capture the plan before the outcome
A useful record preserves what you knew and intended at the decision time. Editing the original thesis after the result destroys the evidence.
Date / market / session / direction:
Playbook and regime:
Location and higher-timeframe structure:
Trigger and participation evidence:
Entry / initial stop / targets / planned R:
Position size and maximum planned loss:
Management rules:
Mood and process risk before entry:
Exit and realized R:
Rule adherence score:
One repeatable lesson:Separate process from outcome
Judge whether the decision followed the system before you look at whether the trade made money.
| Process | Outcome | Review |
|---|---|---|
| Good | Win | Keep the repeatable behavior; do not confuse one result with proof of edge |
| Good | Loss | Accept system variance and verify that realized risk matched the plan |
| Bad | Win | Record a process leak; profit does not make the decision safe to repeat |
| Bad | Loss | Fix the specific rule break before taking the same setup again |
Use the journal and edge commands as a sequence
Each command owns a different stage. The quality of the analysis still depends on honest, complete records.
/logtrade- Save the planned trade fields before or near execution.
/closetrade- Close the record with actual exit and result data.
/journal- Add session lessons and mood evidence, then review prior entries.
/review- Score one trade across process, risk, and psychology.
/mytrades- Inspect your recorded history and find missing or inconsistent fields.
/myedge- Analyze expectancy, profit factor, drawdown, process score, symbols, and sessions.
/systemstats- View aggregate community metrics only after enough closed records exist.
Measure the distribution, not the highlight reel
Win rate alone cannot tell you whether the system has edge. Pair it with payoff, expectancy, drawdown, adherence, and sample size.
| Metric | Question it answers | Common mistake |
|---|---|---|
| Expectancy | What is the average result per trade? | Assuming the planned target equals the realized average win |
| Profit factor | How much gross profit exists for each unit of gross loss? | Trusting a high value from a tiny sample |
| Average R | Are wins large enough relative to losses? | Mixing currency P&L with inconsistent position sizes |
| Max drawdown | What decline occurred from peak to trough? | Ignoring open risk or chronological order |
| Process score | How often did execution follow the rules? | Rewarding a profitable rule violation |
| Sample size | How much evidence supports the conclusion? | Calling five trades an edge |
Run the weekly review
Review a group of decisions at the same time each week so the loudest outcome does not control the story.
- 01
Verify that every trade has complete plan and result fields.
- 02
Group trades by playbook, regime, market, direction, session, and rule adherence.
- 03
Compare planned R with realized R, including fees and slippage.
- 04
Save one clean example, one avoidable mistake, and one valid pass.
- 05
Choose one behavior to practice next week; do not rewrite the entire system from a small sample.
Next steps
Use the review to sharpen one layer of the process.