Hi everyone, Me and my team are working on the next round of content for the YouTube Channel and we need your help. We're now accepting ideas from members of Zero One Systems for specific tutorials, builds and explainers YOU want to see on my YouTube Channel. I'm talking: - Builds you've never seen before - Tutorials you've always wanted - Explanations no one has given yet I'll be able to pull from this list and ACTUALLY make the videos you've asked for. You can also "Like" another comment if you like their idea and I'll track the likes as "Upvotes" Lewis p.s.sometimes it's really hard to know which content people want vs what is made. This would help tremendously with that.

Followed along in the day 1 video. Put in a weather ticker above. Threw in tradingview lightweight chart Added in a game theme (inspired by a well known game coming back as remake, I'm curious if anyone notices) Messed around with a left sidebar and right sidebar to understand term Combined three panels into one tabbed panel for a clean layout Realized I could easily go on for hours adding in more so I'm stopping here to submit Day 1 completed and move on to day 2

Hey everyone, I’m Joseph. I’m an electrician by trade, an active trader, and definitely not someone who came into this with a traditional software-development background. I started this project because I couldn’t find a trading platform that approached the market the way I wanted. Most of the “AI trading” products I found were either long-term investment tools, basic signal generators, or black boxes making decisions without enough explanation or control. I’m interested in something very different: an agentic system designed specifically to observe fast-moving market conditions, develop a trade thesis, manage risk, and explain what it sees—without treating an LLM’s opinion as permission to place a trade. The project has grown into a fairly substantial trading platform. It brings together market data, news and catalyst analysis, technical structure, risk controls, strategy selection, position management, journaling, replay, and decision evidence. The goal is for the different parts to work together as a supervised trading team rather than as one model trying to do everything. A few principles have shaped the build: - AI can interpret context and coordinate decisions, but hard risk limits and execution permissions should be deterministic. - Missing, stale, contradictory, or ambiguous information should cause the system to stop—not guess. - Every important decision should be traceable to the evidence that supported it. - A human approval button is only a real safeguard if the human receives enough information to make an independent decision. - Paper trading and replay are for collecting evidence and exposing weak logic, not just producing a pretty profit number. At the moment, the core platform and supervised orchestration system are built. I’m now working through controlled live-data validation, paper-trading evidence collection, edge cases, and the boundaries between analysis, recommendation, approval, and eventual execution. The long-term goal is greater autonomy, but only after each earlier stage has demonstrated that it can fail safely and explain its behavior.

Here a result from Day 05 Personality Profile — ISTP-A Type summary: ISTP-A (Virtuoso) — a pragmatic, independent thinker who operates best with hands-on freedom and room to adapt. Highly observant and logic-driven, with a natural ability to stay calm under pressure and cut through noise to find practical solutions. The freedom to move quickly and change course when needed is non-negotiable. How to communicate with me: - Be clean, clear, and concise — no preamble, no padding, just the substance - Lead with the point, not the background - Stay practical and grounded; abstract or theoretical framing disengages me - Match my directness — I read brevity as respect, not rudeness How to deliver bad news or risk: Flag it immediately and directly. Include relevant context only if it changes how I should respond, and always come with at least one proposed solution or next step. Disagreement and pushback: Challenge my thinking and flag disagreement — but only when there is a genuine reason to; don't push back for the sake of balance. What to avoid: - Lengthy explanations or over-qualifying statements before getting to the point - Abstract or purely theoretical discussion without practical application - Unsolicited emotional framing or motivational language

Gave me a lot of thinking to do. I have a existing Rust based trading software I'm constantly dev/code but decided for the sake of following class, I'm putting Rust dev on hold til I get a whole landscape understanding from class. Here my simplified Miro board from day 04