Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
What is this?
Less
More
7 contributions to ZeroOne · Your First AI Agent
Jul 28 • 
Ask
What is the correct approach to test Markov v2?
Executed Markov 2 on TAO but seeing inconsistent results. What is the correct approach to fine tune it?
What is the correct approach to test Markov v2?
1 like • 12d
Before tuning it, I'd check the reporting. The screenshot shows 27 closed trades, but 16 wins and 10 losses. Is the other trade a breakeven? The rows also show different strategy versions, so I'd freeze one version and replay the same data twice to check whether the results match. Otherwise it's hard to tell whether the inconsistency comes from strategy changes or the test itself.
Getting Kairo ready for the build 🛠️
Before writing a single line of EA code, I spent a long session making sure the foundation is solid. Here's what got done: 1. Risk rules first, in hard numbers I wrote a dedicated risicoregels.md (risk rules) file. Every number in it becomes a fixed constant in the code, not a setting anyone can tweak: - Demo account only, €250 start, EUR/USD only, max 1 open position - Risk per trade: 0.5% of balance below €500, 1% from €500 - If even the minimum lot (0.01) risks too much → no trade, no "just this once" - Daily stop: −2% in a day → no new trades until tomorrow - Max spread 1.5 pips, no new trades 30 min before/after major news, everything closed Friday 16:00 New York time - Loss limit with two safety nets, whichever is stricter: one third of the highest equity is never touched, and half of the highest profit is always kept. At the start that means the account can never drop below €83.33. 2. Thinking in pips, not euros My first instinct was "keep the profit target tiny so I don't give it back." The maths showed the opposite: a €0.50 target against a €1.25 risk needs a 76% win rate just to break even. So instead: - Take profit = 1.5× the stop distance (in pips) - Once a trade is 1× the stop distance in profit, the stop moves to entry +1 pip → that trade can no longer lose - With that setup, a ~44% win rate is enough to break even Small fish swimming with the whales, but letting the current carry you a bit. 🐟🐋 3. Clear roles between me and AI I briefly wanted to give Claude "carte blanche" to build and run everything. We talked it through and settled on this split: Claude researches, proposes (with reasoning) and builds; I decide and approve every step. Hard limits can only be changed by me, in the code. No AI, and no person, gets uncontrolled access to my money. 4. Python ↔ MT5 bridge working - Took a Hyper-V checkpoint of my trading VM first, so there's always a way back - Found out the MetaTrader5 Python package doesn't support Python 3.15 yet (max 3.14) → installed 3.14 next to it and created a dedicated virtual environment just for Kairo - Wrote a read-only connection test script: it connects to MT5, checks the account, balance and symbol data, and never places an order
1 like • 17d
Glad you checked! The daily stop clearing when the price recovers is a useful catch beyond the restart issue. I'd keep that as its own test: hit the limit, let equity recover, and confirm trading stays locked for the day.
0 likes • 17d
@Michael Rousseau A separate backstop could help if the main EA's logic fails. I'd still test what happens when the whole terminal disconnects, though. If both depend on the same terminal, the backup may be unavailable exactly when you need it. That's a different failure from the restart bug we were discussing.
Ive made a solana bot using claude code fable 5.1 high and sonnet 5 max
Im trying too improve it so far its only on paper trades testing strats but i mainly need the bot too improve
1 like • 17d
Anthony, before creating another strategy, I'd check a few trades where you and the bot made different decisions. What did you see that it didn't? That seems more useful than asking Claude to improve a strategy when you're not yet sure it captured your entry rules.
0 likes • 17d
The source and update times under each panel are a nice touch. Makes it easy to tell what's live and what's saved. Are you planning to use this as your daily start page?
Day 3 - First Agent
First agent: billing drawings & terrain models. Highest score, targets exactly the bottleneck from Day 2, and lower-risk to validate than a trading bot. Success = a correct, ready-to-use quantity takeoff/DWG that you only need to check instead of recalculating from scratch.
0 likes • 17d
Can each quantity point back to the drawing or model section it came from? That would make the review much quicker. If a total looks off, you could check the source straight away instead of redoing the whole takeoff.
1-7 of 7
Stefan Pantelich
2
15 points to level up
@stefan-pantelich-9258
Senior Software Engineer | Product Engineering & Architecture | AI & Security

Active 2d ago
Joined Oct 25, 2026
Powered by