Here’s the prompt (it’s not perfect, but changes were fewer): VISUAL PROJECT LOCK We are going to develop this image iteratively. Treat this conversation as one continuous design project, not a series of independent image prompts. Your job is to preserve decisions as we make them. RULES: 1. BUILD A RUNNING SPEC As I give you requirements, corrections, references, copy, layout directions, visual preferences, and “do/don’t” instructions, maintain them as one cumulative project specification. A new instruction ADDS TO the existing specification unless I explicitly say it replaces something. 2. LOCK ACCEPTED DECISIONS Once I approve an element, treat it as LOCKED. Do not redesign, reinterpret, improve, relocate, restyle, rewrite, remove, or replace a locked element unless I specifically ask you to change it. 3. CHANGE ONLY WHAT I ASK TO CHANGE When I request a revision, identify the exact requested change. Everything else should remain as close to the previous approved version as technically possible. Do not use a small correction as permission to regenerate the concept creatively. 4. CORRECTIONS OVERRIDE EARLIER VERSIONS If I correct something, the correction becomes the new source of truth. Do not revert to an earlier version in later generations. 5. REFERENCES ARE REQUIREMENTS When I provide a reference image, determine what I am referencing it FOR. For example: pose, angle, proportions, architecture, material, lighting, hairstyle, object construction, composition, etc. Preserve that specific characteristic in future generations unless I change it. Do not sacrifice physical/reference accuracy merely to make text, objects, or composition more convenient. 6. COPY IS LOCKED COPY When I provide exact wording, reproduce it exactly unless I ask for copy alternatives. Do not paraphrase, shorten, “improve,” add, or substitute copy during image generation. 7. KEEP A “NEVER DO” LIST Any time I reject something, treat the reason for rejection as a negative constraint going forward.

Q1 — Who I help / background I'm an ADHD business builder who spent 20 years not committing (a lot of it had to do with my extremely demanding day-job), but also part of it was that when I *did* have time to build (a few hours here and there), I didn't make much progress because I wasn't focused. Or, when I was building along with my trusted info-providers, I'd get stalled because the boring groundwork wasn't done. The parts I liked were polished; the back-office was a mess. (SIDENOTE: This reflected my real-life job/office too. I was a rockstar at work, my desk....a shameful mess. I LOVED operations management, I hated paperwork - LOL). Now I help easily distracted business builders fix that: organizing the files, chats, and systems so their they — and their AI — can find what it needs, their business run smoother, and get automated instead of constantly breaking. Q2 — What I teach/offer I teach people to organize their files and systems so the messy chats and scattered ideas that come naturally to an ADHD brain don't get lost — and stop being that nagging background stress they can't name. I help them adapt generic productivity advice to how their brain actually works. I teach them to build a knowledge base their AI can actually use. And I teach systems thinking, so workflows get built complete the first time instead of breaking because a piece got missed. Q3 — Transformation or skill? The transformation. They want to have something they can rely on, that runs without them having to constantly be thinking about it. At the end, they also get less stress and easier use — the result of finally having their systems together, but the reason they find me is annoyance.

@Darius Jones I think your answer to #3 is one of those instances where you don’t fall easily into either column when asked “Would you say you teach a transformation? Or a skill?” • Do they come to you to learn how to do the thing so they can do it for someone else? Yes, to drive others loads. • Or do 2 - they come to you to get the thing done for themselves. Also Yes, to have their own trucking business. Is this correct? Genuinely both 😯🤯