I was creating a second version of a pricing engine I built. Claude decided to deploy onto my live site, and then overwrote the local file where the latest updates for that code lived, apparently. The last commit to git was two weeks ago. So, I think I just lost 2 weeks of de-bugging code cause I didn't commit the latest version to git. Is this real? Did I just skip the most important step -- saving my work? This is a real thing, right?

If you’re using AI to build something bigger than one image or one afternoon’s work, don’t make the chat your production system. I learned that building our 104-page graphic adaptation of Arthur Conan Doyle’s *The Lost World*. And by “our,” I mean me and ChatGPT. I made the creative decisions; ChatGPT helped execute and keep the work organized. The method was what I call **folder factories**. Each part of the job had its own saved inputs, working files, decisions, and checks. The next step could begin from those files without needing to reread a months-long conversation. Three things made the difference: 1. **Design the world before making the book.** We established character and creature designs, costumes, props, vehicles, locations, and a consistent painterly look. Every new panel had specific visual rules to answer to. 2. **Prove the process before scaling it.** We tested one finished panel, then a complete page, then a difficult ten-page run. Only after that did we build the 100 story pages and 372 panels. 3. **Treat review as production, not cleanup.** A panel can look great alone and still fail beside the next page. We checked continuity, page turns, dialogue, lettering, and eventually the print-safe area. When something failed, we could return to the part of the process that owned it without starting the whole book over. We learned why this mattered when trying to load hundreds of images crashed the chat. The work survived because the source art, approved decisions, and revisions lived in the folders. That’s the lesson I’d pass on: **generation is not completion.** A creative project becomes manageable when you can find what was decided, see what changed, and hand the next person or tool a usable file. The complete graphic novel is free to read on The Gutter: https://the-gutter.racon-gunner.chatgpt.site/comics/the-lost-world/complete-graphic-novel/?page=1

I searched through the community to see if anyone posted about the foundation layer of every business: accounting. If I missed a thread on this, please point me toward it! If it hasn't been covered yet, here is what I’m thinking. I'd love to get some ideas on how to design a basic folder setup that every member here could use to kickstart their own accounting department—essentially an ICM Accounting System. I follow a guy on TikTok who leverage trades crypto, which is an absolute accounting nightmare. A member asked him how he handles his taxes, and his answer stuck with me. He said wealthy people rely on three key professionals to minimize their tax burden and preserve long-term wealth: a bookkeeper, an accountant, and a tax attorney, in that exact order. I prompted Gemini for a structure using the ICM methodology framework and got a solid blueprint. Before I take it further: Has anyone else in the group tackled this yet? If not, do you think it would be valuable to build out a basic starter folder structure to share with the group? Just thinking out loud, so I’d really appreciate your input!

A FEW WEEKS AGO... I posted that I had made a business, spun-off of one of my competition entries. Full disclosure, it's not exactly any of them (if you happen to go look). I just took what I had learned while building and applied it to a business strategy I wanted to try. And you know what!? I got a client. It's the first client I've gotten for another venture, outside of the main business I've been running. Considering I have spent 10's of thousands of dollars on other "tests," over the years, this was a HUGE win to actually make money from something. AND NOW I BUILD... Now I'm using ICM to automate the dumb stuff and enrich the good stuff. I'm constantly asking myself if what I'm building make sense, or if I'm falling into the trap that Jake talks about, where folks overbuild or build something that doesn't matter. I am pretty sure I'm doing it right because newer AI models won't affect what I've made, except to streamline the dumb stuff more... Anyway, I'm looking at the unit-economics of the business I'm building now, based off this one client that I'm trying to give the most amazing experience to, and I am blown away by the potential. It feels like it can't be real. I'm probably putting the cart before the house, so to speak, but I can't help to be optimistic looking at the numbers, of which, I will admit, I'm making a lot of assumptions about. SUCCESS LEAVES CLUES... I have been studying business for a long time now, to try to understand how riches are truly made beyond what the typical small-business owner does (average is like $50K a year or something). I feel I will lose my mind if it takes me 20 years to build wealth because I had tunnel vision and chose a very slow moving vehicle to get me there. And look, I know it's *all* hard, the grass is always greener, yadda yadda yadda (Seinfeld, anyone?), but it's still true that there ARE easier opportunities to make wealth. There just are. I've come back to this fact time and time again while searching for my next business model.... In simple business terms, if your CAC (cost to acquire a customer) is extremely low, 0, or even negative, and your LTGP (lifetime gross profit -- what the client pays you in total, for the entire duration they use your business) is high, then you're printing money. And if the profit margins are 80% or more? Then you're swimming in gold.

I was invited to sit on a panel this morning: "AI in Action: The Mindset Behind the Moves," at Auxiom's Community Appreciation Event, attended by 120 business leaders in Detroit Metro. Grateful to Founder and CEO Matt Loria for the invite. Auxiom is a local IT and cybersecurity company. Before the panel, Ashok Sivanand (Nous) ran the room through a workflow-redesign workshop. He opened with a stat from McKinsey: 80% of companies doing generative AI work saw no change in profitability. He paired it with another: only 1 in 5 companies had actually redesigned a workflow before pointing AI at it. Same 1 in 5, both times. He called it a coincidence. This is similar data I referenced in David's Corner, The Tool is 10 Percent. His worksheet was amazing though: name the constraint, name the workflow, name your customer, find the leak, pick one fix, run a 30-day experiment with a guardrail and a report-back date. His line on the handout: diagnose before you prescribe. All 120 execs walked out of that room with a real next step; that's rare for many speakers. On the panel, I got to talk about an idea I've been writing about here: AI does two different jobs. It's good at mining your own record for what's already true, and it's good at amplifying whatever you give it. Skip straight to amplifying, and the output sounds like everyone else's. Someone asked what my own transition looked like, going from a 12-person team to running alongside 20-plus specialists. Two years chasing tools before I found ICM. Two weeks after that, I converted all my unstructured data into structured markdown and built my routing map and orchestrator, Duke. After, a CIO on the panel asked me how I was able to orchestrate across 50k markdown files. I said, "Simple: a map, and dropped Jake Van Clief and ICM as the solution." The closing session was Aaron Salko and Kelly Johnson on human performance. A line I wrote down: "Technology creates capability; human performance determines the outcome". If you've got performance gaps today, AI doesn't fix them. It multiplies them across more people.