This is a letter written to our community. (No Emjois in this one) I have thought about posting this, and I decided that it needed to be posted. I have been away for a bit, mostly because I have been focused on 7 lives that needed me the most. Firstly, I am an IT manager, I am a leader of a team that puts their best into everything they do every day. We have been through the thick and thin together, we have faced adversity and success together, and lately we have faced challenges and expectations that effect all 8 of us. I have had no other option but to focus my energy on the things that keep us moving forward in our own lives. This does not mean this community does not mean to the world to me, but it means I have been focused on other things. I do not apologize for doing what I felt is the right thing, I apologize for not being here for the community. My heart is heavy. Beyond the obligations I have set in stone for the people I lead, I have had a tremendous loss in my life. Today the world has lost a bright light, someone who showed up in my life in a time that I needed most, her name is Marina Berthal and she should be celebrated not only mourned. To all of you she was a stranger, to me she was my world, she was the mom life never afforded me. I have lost 3 moms now in life. The first was my biological mother, the second my grandmother, and now Marina, a person who found me early in life, a broken and lost soul looking for guidance. I know our community is supportive, committed and above all else caring. You have all quickly became the family I have searched for in a lifetime. I want to apologize for my absence and want you all to understand that it is not by want, but by need that I am away currently. In my life I have experienced more loss then most, and this loss has landed in a time when I just could not hold it. I will be back; I just need some time to process this loss. I know we will win together, even when things seem tough. I believe in my heart, as Marina has taught me in life, we will learn together, we will grow together and we will win together.

Can't see a high tea in the calendar for today but I went to my first one last week. I loved the idea of getting a deep dive from Jake and his material was excellent. I just personally found it very difficult, because Jake is extremely generous with his time and happy to help anyone during the session which is a lovely thing to do. I just struggled because the discussions veered into what was not relevant or interesting to me, Jake didn't finish his presentation two hours in and it was late so I missed the last part because I had to go to bed. I am used to a more structured approach like presentation first questions in Q & A and addressed at the end or in a separate community session, so I will probably just watch the recordings instead in future. Not a criticism I think it's cool that this community works like that rather than some culty limited access to a charismatic leader deal but I just prefer something more structured so I can see the bit I attended for in full

Just upgraded to VIP so I wouldn't miss another high tea but there doesn't seem to be any scheduled. What's the secret handshake? Thanks!

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. 📋 THE CHALLENGE Build a folder-based AI diagnostician that reads something broken and tells you WHY it's broken. Not how to fix it. Why it failed. This week's deliverable is one diagnostician folder that someone could drop into a Claude project and use to figure out why something in their world isn't working. 🎯PICK YOUR DOMAIN The domain is yours. Pick something specific. Pick a failure you've actually seen happen. A few sparks to get you thinking: - 📉 Why a landing page isn't converting - 📧 Why cold emails to a specific buyer aren't getting replies - 📋 Why a product spec keeps getting pushed back by engineering - 📄 Why a resume isn't getting callbacks in a specific industry - 🚪 Why users drop off at one step of an onboarding flow - 💸 Why a pricing page isn't converting trials - 🎥 Why a YouTube video underperformed the channel average - 🤝 Why a sales deal stalled after the demo - 📱 Why an app's retention craters in week two The more specific, the better. "Diagnoses marketing problems" is too broad. "Diagnoses why cold emails to enterprise IT buyers get opened but never answered" is right. 🗂️THE METHODOLOGY If this is your first comp, welcome. Here's what you need to know: This week (and every week) you're learning interpretable context methodology. Folders as architecture. Each file does one job well. Your diagnostician is a folder with five things: - 📄 identity.md (who the diagnostician is, what they diagnose) - 📐 rules.md (how they diagnose: what they look at, how they separate cause from symptom) - 💬 examples.md (2-3 example diagnoses showing the reasoning) - 📚 reference/ (common failure modes, diagnostic frameworks, benchmarks) - 📖 README.md (how to use it, what to feed it) Drop the folder into a Claude project. Claude becomes the diagnostician. Reusable. Shareable. Portable. 🔥 THE ANGLE THIS WEEK A diagnostician is NOT an editor. Last comp was The Editor. That one critiques craft. It looks at a draft and says "this part is weak, go fix it."

Take ya votes plz <3