Welcome to Clief Notes. Here’s where to start. 👋 You don’t need to watch the entire classroom before trying something. Pick a starting point, make something small, and bring your questions back here. 🧭 Find your way around Navigating the Course shows you what’s here and how to get around. If you’re new to working with AI, start with The Foundation. We work through prompting, context, and organizing your files so you can give an AI a job you can actually check. You’ll find guidance for Claude Code and Codex, plus a regular chat route where you save the files yourself. 💬 Use the check-ins At the bottom of the lessons, you’ll find polls and discussion posts. Share what you tried, what worked, and what needed correcting. If something doesn’t make sense, post the lesson and timestamp. “I got stuck right here” is a perfectly useful question. 🏆 Put something into practice Visit the Competitions Mega Thread for the current challenges, rules, and prizes. It’s a good excuse to finish something and see how other people approached the same problem. 📦 Looking for more? Premium: Explore The Vault for practical packages, templates, meeting takeaways, and worked examples. VIP: Head into The Drawing Room for VIP sessions and resources. Post your work. Ask questions. Help someone else when you can. What are you here to build—or what’s one task you’d love to make easier? Tell us below.

High Tea 17 (10 Oct) and High Tea 18 (24 Oct) are both up. Each one comes with the full recording and a zip package built for the session. Drop the folder on your machine, open it in Claude or whatever you use, and say what you’re working on. It routes you to the right file, and every strategy file ends with a prompt to run on your own work. ━━━━━━━━━━━━━━━━━━━━ 📼 HIGH TEA 17: Outcome First (1:40) Get the outcome, then refine. • Why you run out of tokens, and how to fix it: say where your data lives, and push repeat jobs to a script or the cheapest model • Using Claude to replace Claude • A mounted Google Drive as the simplest shared folder for a team • HTML dashboards that live in your folder, and GitHub Pages in two clicks • Cutting big tender and RFP files down to the paragraphs that matter, with Jev as a filter • Pricing against software a company already pays for 📦 In the zip: 8 strategy files, plus 4 kits you can use today: a token diet worksheet, a shared Drive starter, an HTML dashboards folder, and a tender intake system with working scripts. ━━━━━━━━━━━━━━━━━━━━ 📼 HIGH TEA 18: The Next Yes (1:21) Get paid before the product exists. • Audit, pilot, contract, product: each stage pays for the next • Grants that take no equity, and using one to pay the client you want • How clients find you • Selling what you already know as the audit • Proving AI’s return when it seems to vanish across a team • One basket, and a plan B that gets better every year • Setting Claude up on a client’s machine 📦 In the zip: 9 strategy files, plus a pricing ladder, a grant-hunt kit and an ROI worksheet. ━━━━━━━━━━━━━━━━━━━━ Both zips also hold the full transcript, the member Q&A and a term sheet. Grab them in the vault. Questions go in the Discord. 💬

🎁 $1,000 IN PLATFORM CREDITS🎁 One winner takes it. 📋 THE CHALLENGE Pick your weakest entry from any past comp. Read the feedback file we sent you. Rebuild it. Then prove the rebuild is better. Every entrant since the Cartographer has a file that says what worked, two fixes, and the one thing that would have moved them up. Most of those files have been read once. This week you act on one. This week's deliverable is the original pinned, the feedback file, the rebuild, and a control showing old against new. 🎯 PICK YOUR ENTRY Any comp you entered. Cartographer, Auditor, Translator, Control, or anything earlier if you still have the repo. Pick the one where the feedback file stung the most. That is the one with the most room. If you have never entered, you can still play. Pick any public repo from a past comp whose author has posted that it is open for rebuilds, and treat the public results post as your feedback file. Credit them in the README. A few sparks: - Your Cartographer map, rebuilt so the territory ships pinned in the repo - Your Auditor, rebuilt so every finding resolves to a provision a mod can open - Your Translator, rebuilt so the shape holds on the input that broke it - Your Control, rebuilt around the question the folder lost on - Any entry whose README a stranger could not walk The pattern is the same every time. The feedback named a gap. You close it and show the closure. 🔥 THE ANGLE THIS WEEK Last comp was The Control. You ran the same questions with and without a folder and committed both. The Rebuild runs the same test on two versions of the same folder. Original on one arm. Rebuild on the other. Same questions, same order. The questions come from the feedback file, so the test is aimed at the exact thing you were told to fix. In the Cartographer round, Adam put his README in front of an outsider, watched her fail for twenty minutes, cut it from 904 words to 471, and kept the old version in the repo so you could see the change. That is a rebuild with the receipt attached. This week everyone ships one.