Every post in this series so far has been about a specific trading decision — a revenge trade, an oversized position, a signal fought instead of adapted. This one is different. It’s about a mistake that happened after the trading was already over: two rule breaks from Day 9 of the $50K-to-$100K Challenge that never made it into the rule-break log at all. Day 9’s post covers the trades themselves in detail; this post is about the bookkeeping gap that followed them.
What actually happened
Day 9’s oversizing problem produced two clear rule breaks in the trade log — “MGC risk too big” and “6B frontrun PDH.” Both were flagged in the daily notes. Neither one made it into the formal rule-break log, which is a separate running record meant to track every logged violation over time so patterns can be spotted across weeks, not just within a single day’s post.
The rule-break log kept running from a prior date without those two rows added. On paper, the cumulative rule-break count for the challenge looked lower than it actually was, for a stretch of days, because two real violations weren’t in the tally.
Why this is the mistake that makes every other mistake worse
Every mistake in this series up to this point is a single-day problem with a single-day cost, however painful. This one is different in kind: a gap in the logging system doesn’t cost money on the day it happens — it costs accuracy in every future review that relies on that log. The monthly audit, the weekly review, the pattern-spotting across a full challenge — all of it depends on the rule-break log actually reflecting what happened. Two missing rows means every downstream analysis built on that log is working from incomplete information, and there’s no dollar amount attached to alert anyone that something’s wrong.
This is the accountability layer failing, not the trading layer. A trader can have a genuinely sound process and still lose money to variance on any given day — that’s normal. What isn’t normal, and what erodes trust in the whole system, is a record-keeping process that quietly under-counts its own failures. If the log says four rule breaks when there were actually six, every conclusion drawn from “we only break rules 0.40 times per day” is built on a number that’s wrong in the safe direction — which makes it easy to feel more disciplined than the trading actually was.
The self-trust problem underneath this
Journaling and review are required for growth, but they only work if the trader trusts the journal to tell the truth. A journal with quiet gaps doesn’t just produce bad data — it produces a false sense of security. Confident, low-rule-break self-image built on an incomplete log is worse than an accurate, higher-rule-break self-image, because the false version can’t actually be corrected. You can’t fix a pattern you don’t know exists.
This connects directly to why outcome bias and self-assessment are such persistent problems in trading — Britannica’s overview of behavioral biases in finance notes that self-serving bias tends to inflate a trader’s sense of their own discipline over time unless something external and mechanical forces an honest count. The rule-break log is supposed to be that mechanical check. A log with gaps in it stops functioning as a check and starts functioning as reassurance instead — which is close to the opposite of its actual job.
The bookkeeping analogy
A business that forgets to record two real expenses doesn’t stop owing that money — it just finds out about it later, usually at a worse time, usually as a surprise instead of a line item it had already planned around. The expenses were real the moment they happened. Not writing them down doesn’t make them smaller. It just delays when the business finds out how much it actually spent, and removes any chance to react to the real number while there was still time to adjust the plan.
Two unlogged rule breaks work the same way. They happened. They’re real data about the account’s actual behavior. Not logging them doesn’t erase them — it just means the next review runs on a number smaller than the truth, and any decision made from that smaller number is a decision made on bad information.
The fix
The correction here was simple once caught: both missing rows got added retroactively, with the original trigger, rule broken, and lesson exactly as they happened, dated to Day 9 rather than backdated to look like they’d always been there. The bigger fix is procedural — the rule-break log gets updated the same day as the daily post, not as a separate step that can be skipped when the day feels busy or the day’s number looks fine. Tying it to something that already happens every day (the daily post) removes the chance for it to quietly slip.
By Day 13 and Day 14, the corrected process held — both days’ rule-break rows were logged the same day as the trades happened, no gap. That’s the actual proof this fix worked: not a promise to do better, but two consecutive real incidents that got recorded correctly the first time.
Takeaway: A trading mistake you don’t log doesn’t stop being a mistake — it just becomes a mistake nobody can learn from, including you. The log is only as useful as it is complete, and completeness isn’t optional just because a specific day felt too busy, too good, or too embarrassing to write down accurately.
Check your own trade log for the days you didn’t feel like writing down. Those gaps are usually hiding the exact lessons you need most.
