I am known to take Claude outputs and put them into ChatGPT for blind-spot checks. Today I decided to create a "council of 5" skill that runs any question, problem, solution, document, etc., through 5 distinct personalities, with 3 rounds of discussion, then a consensus. 1. The professor: peer-reviewed/cited sources only 2. The teacher: logical, wonders, "is this the right question to be asking" 3. The founder: can this be done, and what is the fastest way 4. The outside: zero context, thinks outside of the box 5. The contrarian: hunts for the fatal flaw in everything. Sharing the skill here if it could help anyone.

"Hi. My name is..." Most of you thought *Slim Shady*. You didn't choose to. Your brain finished the line for me. That's not a memory. That's a file. Eminem put a .mp3 on enough devices that 27 years later the phrase auto-completes in your head before you've decided whether to. The .mp3 isn't the song. The .mp3 is the install. And the install is what survives everything else. Not the tour. Not the chart position. The file on the device. So I stopped thinking about reach as eyes-on-content and started thinking about it as files-on-devices. The yardstick Distribution is not marketing. Distribution is legacy. The PDF won. Not because it was the most elegant document format. It won because it ended up on more devices than anything else. The MP3 did the same. So did the JPEG. The format that earned a life was the format on the most machines. Not the most correct. Not the most beautiful. The most installed. The work that lasts is the work that travelled. What an install actually looks like Three signs you've installed, not just been seen. 1. Re-entry without prompting. Someone opens your thing before they decide to open it. The switching cost has disappeared. 2. Installed before adopted. It became part of a workflow before anyone consciously chose it. 3. Outlives the moment. Years later, the file is still on the device. Not because you maintained the relationship. Because the format earned its keep. The files I've shipped that travelled were not the files I pushed hardest. They were the files good enough to keep, in a format easy enough to spread. In a ICM workspace the output folder is the product I spent a long time charging for the hours. The client doesn't experience the hours. They experience the file. The deliverable. The thing they put in a folder and reference six months later when the person who commissioned it has moved on. So I started pricing the folder, not the working. The hours are overhead. The output is the product. The output is what survives the invoice.

So, yesterday I delivered a presentation to a family that requested a Wealth Development Analysis. I took 18 years of their Tax Returns to understand their past, and projected their next 25 years based on diferent economic scenarios. I've used Cowork, Code and Design. It went great, but this is not the main topic here. I've recorded the whole 100min meeting, transcribed it, uploaded to Claude, and asked it to analyze the whole meeting. I asked questions like: What is my style of presentation? Where did the storytelling worked and didn't work? What was the impact of my presentation on each participant? What didn't I see during the meeting? What a system's thinker would tell me about the meeting? The output was amazing. I got deep, lengthy feedback that will help me improve in my next preparation and presentation. It felt like closing the loop. So, don't stop at delivery, add another step of self-reflection in order to keep evolving!

Welcome to Ari’s Space. Think of this as your always-open support thread inside Clief Notes. If you have a question, feel stuck, need direction, want feedback, or just need a little clarity, drop it here. This space is for: - Questions about Clief Notes or ICM - Help applying what you’re learning - Feedback on your ideas, content, offers, or next steps - Accountability nudges - “Am I thinking about this the right way?” moments - Anything you’d usually wish you could ask me directly No question is too small. If it matters enough for you to ask, it belongs here. I’ll be checking in regularly and answering as much as I can. Use this thread like an AMA that never closes. Drop your question below whenever you need support with. Welcome to Ari’s Space. <3

I wrote an article about why you should use ADRs and what they are. It's a simple read, maybe like five minutes. https://kuality.design/en/blog/why-solo-developers-need-architectural-decision-records-adrs