I built this project to test Grok Bot and Atomic. I believe I went overboard lol still this is a good sample case of my weaknesses. It is far from over. It does not auto update yet and I'm still working on it. https://battle-harnesses.vercel.app/ 1. What are you trying to make happen? I want to use one real project, **Battle Harnesses**, to learn how a senior developer would frame and organize a software project from the beginning. Battle Harnesses is intended to be a public guide to AI coding harnesses. Behind the website, there is a private research system that gathers and evaluates source-backed information about the products. The website then publishes a useful view of that research. There is also a separate public pack containing only the material that is safe and appropriate to distribute. For this session, I am not mainly asking for help fixing the current repository. I want to reconstruct how I should have thought about the project before building it: - how to turn the product idea into clear system boundaries; - how to choose the smallest useful version; - how to define sources of truth and the data flow; - how to separate private research, public product output, and local AI working memory; - how to decide what belongs in GitHub and what must remain local; - how to define tests and proof before delegating work to AI agents. I would like to leave with a simple project-start method that I can reuse on future projects. 2. What have you tried already? I began by researching the product landscape and building the website with AI coding agents. Over time, the project developed several layers: - source-backed research ledgers and product dossiers; - generated website data; - a React/Vite website with product, comparison, and guidance views; - a private development repository; - a separate public distribution pack; - a local-only `AI_OS` layer intended to preserve decisions, current state, and instructions for AI agents.