markhadrian
|
trade according to rules set out in...
Star this Commitment
markhadrian commits to:
trade my locked K3/K3X/K4/K5 live strategies exactly as defined in my worksheets. No rule changes or BA servant mods allowed except bug fixes. Every trade will be logged honestly, including errors. Any rule change or servant mod breach must be reported in the monthly review and results in a £200 penalty. Full terms and verification process are defined in the signed Trading Consistency & Accountability Commitment document.
No more reports due
|
My Commitment Journal
 markhadrian
June 1, 2026, 6:14 AM
|
|
| See journal entry about discusses and approved changes in May and the proposed Reset V4 implementation-verification month for June. | |
|
markhadrian
May 31, 2026, 8:02 PM
|
|
|
In the first half of the month, there was a significant overhaul of the strategy setup and rules, despite previous assurances that this would not happen anymore. This technically breaks the original post-reset agreement, and I fully acknowledge that. However, this was not done to add new strategies, increase discretion, or create an excuse for further tweaking. It was done because the system was still in live-testing, and several important structural issues had not yet been properly exposed. The purpose of Reset V4 is simplification, not expansion. It removes low-frequency, confusing, or research-heavy branches and leaves a cleaner binary structure with lower cognitive load: K3 = front-runner backs K4 = backmarker lays The whole framework is now based on two clear structural race-position angles: back strong front-runners and lay clear backmarkers. This is much more aligned with the original K-system principle of exploiting early market overreactions caused by obvious race positioning. One earlier reset had also moved away from higher-odds K4 lays because of concerns about liability, Betfair outage risk, and future scalability. This was a misguided decision as scalability is a future staking-management issue, not a reason to abandon a potentially valid structure and given K4’s strict exit rules, the expected profit sacrifice from liability staking appears materially larger than the realistic tail-risk reduction it provides, even considering worst-case trading scenarios. I now recognise that the original freeze was imposed too early, while the system was still in live-testing and some core structural issues had not yet been exposed. The V1–V4 changes were not attempts to evade discipline, but corrections made from live evidence. The direction of every major change has been toward fewer strategies, cleaner positioning logic, stricter exits, safer execution, less cognitive load, and a more coherent framework. For this reason, I am proposing June to be as a Reset V4 implementation-verification month only. This is not permission to optimise, experiment, or keep changing the system. The sole purpose is to confirm that the updated worksheets, servants, staking structure, and execution rules now match the corrected V4 framework and function as intended. |
|
This Commitment has no photos.
Displaying 1-1 of 1 result.
May 1 to May 31
Successful
Success
Success
AdamDorogdi
- Referee approval report
markhadrian
- Committed user success report
See journal entry about discusses and approved changes in May and the proposed Reset V4 implementation-verification month for June.
.
