Activity
Mon
Wed
Fri
Sun
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
What is this?
Less
More
AI Automated Trading Systems

3.2k members • Free

Trading Tribe

26.4k members • $1/m

Ray Collective

50 members • $47/month

AI Trading Collective

150 members • $5/month

ZeroOne Systems

14k members • Free

AndyNoCode | AI Video Systems

201 members • $9/month

AndyNoCode

35.9k members • Free

Setterlun University™

4.4k members • $17/month

AI Automation Society

439.3k members • Free

74 contributions to ZeroOne Systems
Your honest thoughts 👀
Who watched/attended live THE BIG EVENT by Lewis? I think this community could give some honest feedback. 💰What were the expectations? 🤖What were the thoughts during the event? 👉🏼Have you stayed till the end? What do you think overall about Louis' big event?😉 Let's be transparent. I think that feedback, good or bad, is always valuable for the creator themselves.
Your honest thoughts 👀
0 likes • 7d
@William Renfroe That's an interesting way to look at it, all of us sharing our honest feedback here is basically training data for him too 😄 Appreciate you pointing that out.
0 likes • 7d
@Glenn Mogford Appreciate this, Glenn. The 6 emails counting down to buy is a pattern coming up again and again in this thread. And that's a great point about timezones, easy to forget how rough these live sales pitches are for anyone outside US/EU hours.
Day 50 done
Highlighted a few inconsistencies. I will be running this prompt again sometime in the future if I change my setup in case I refine the processes and make some efficiency alternations.
1 like • 11d
Day 50 already, nice checkpoint! Smart to flag it for a re-run rather than patch it silently — keeps the audit trail honest if your setup changes later.
Day 29 Complete.
I have a Personal Claude.md file now.
1 like • 11d
Nice, having a personal CLAUDE.md locked in is a great milestone — makes every session after this way more consistent. Day 30 right around the corner!
Day 39 — SOP Review
Read my own SOP back as if I'd never met myself. Found 24 gaps in a document I'd spent six days writing. Two patterns did most of the damage. Contradictions from my own edits. Day 36 tightened a threshold. Day 37 changed a rule. Day 38 moved a deadline. Every time the later section was right — and the earlier one still said the old thing. Six of those. An agent reading top to bottom hits the stale version first. Steps that never existed. My outputs section described a screenshot. My error handling described a sync failure. Neither had a step that produced them. Six missing steps, invisible until I traced backwards. The check that caught them: for every output and every failure mode, ask which numbered step produces this? If you can't point at one, it doesn't happen. One more, and it stung: two tools reported success on things that hadn't happened — including my own symbol search returning 15 results, which I read as "doesn't exist." It did exist. A negative finding needs the same verification as a positive one.
Day 39 — SOP Review
0 likes • 15d
24 gaps found by re-reading your own SOP cold is a great argument for doing that pass regularly. The stale-rule-from-earlier-edits problem especially seems like it'd bite silently for months if left unchecked.
0 likes • 11d
@Anders Hallgreen 36 copies of 6 numbers explains a lot — a single parameters block is exactly the right fix, that's basically turning a maintenance problem into a config problem. Smart that you're keeping the cold read around for the "missing steps" class of bug too, since that's structurally a different failure mode.
Day 38 — Error Handling
Last section of the SOP. The one that changed how I think about the whole build: Silence was ambiguous. My agent stays quiet when no setup passes the confluence gate. That's by design — I don't want "found nothing" spam, or the alert stops meaning anything. But an agent that found nothing and an agent that crashed at 08:03 look identical on my phone. Both produce no message. I could go three days thinking the market was quiet when the process had been dead since Tuesday. Worse: my alert layer runs server-side, independent of my agent. So the trigger still fires — into nothing. No error, no crash report, no trace. Fix isn't a notification. It's a heartbeat: every completed run writes one line to my morning brief. No ping, no noise. But next time I sit down I can see it ran. Plus a watchdog that messages me only if that line goes missing for 24 hours — the one alert that fires when the system is quiet. Second thing: I split partial failures by blast radius. One ticker fails → use the rest, but name the gap. Shared dependency fails → stop everything. Half-built output → discard entirely. Throwing away good work because unrelated work failed is bad. A gap you don't name is worse — that's when you think you've seen the whole market.
Day 38 — Error Handling
0 likes • 15d
The heartbeat-line idea is a great fix — silence-as-ambiguous is such an easy trap to fall into with any monitoring system. Splitting failures by blast radius instead of an all-or-nothing response is a really mature way to handle partial breakage too.
0 likes • 11d
@Anders Hallgreen Good catch calling that out yourself — "documented but not running" is a sneaky failure mode because it feels like progress. Sounds like the honest next step is just building the heartbeat before writing anything else, so the safeguard actually matches the post.
1-10 of 74
Nora Saulīte
4
30 points to level up
@nora-energija-8526
Self-learning trader, trading gold with the most vibrant community, ATTVIP. Also learning AI automation along the way.

Active 14h ago
Joined Jul 24, 2026
Dubai
Powered by