Did some digging as I was curious about the security implications with respect to utilizing MCP. Made some interesting findings! What are your personal takes? Is it `MCP to the moon!` or do you guys think users should be pumping the brakes?

📦 AND SOMETHING NEW: EVERY ENTRANT GETS A FEEDBACK FILE 📦 🔍 WHAT WE DID DIFFERENTLY THIS TIME Every submission was cloned at the exact commit that was public when we read it, and read file by file. The brief. The identity. The rules. The reference layer. The code. Where a repo made a claim we could check, we checked it. Arithmetic recomputed by hand. Sample photos opened and compared against the outputs that cited them. Files diffed. Self-tests traced. Thirty-two repos, read at the code/word level. And one lens over everything, because it's the lens this whole community is built on: does the build keep the human's judgment where it pays and put the deterministic work in code, where it can't hallucinate? 📦 THE FEEDBACK PACKAGE This is the new thing, and it's for everyone not just the podium. 📦 COMP #8: THE WILDCARD - The Vault Every entrant gets a markdown file. Three parts: 1️⃣ The read. What your build actually is, and the strongest thing in it cited to your own files. Rule numbers. Function names. Your own examples. 2️⃣ One push. The single change that most improves your build. Not a list. One. 3️⃣ An idea worth naming something original in YOUR build, credited to you, that the rest of the community is told to take from. Plus links to the builds your feedback points at. Nobody walks out of this comp empty-handed. Thirty-two builds, thirty-two named ideas. The roster alone is worth the download. 📍 The package + the full write-up (what held up, what was missed) live in the new Feedback module: 📦 COMP #8: THE WILDCARD - The Vault 📚 WHAT THE FIELD TAUGHT Three lines split thirty-two repos: ✅ Enforcement. A must in a markdown file is a request. A must in code is a constraint. (That line is from one of your repos. It's in the package. Go find whose.) ✅ Evidence. The builds that shipped receipts of a REAL run transcripts, dated logs, before-and-after fixes read differently every single time.

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. 🛠️ Never ran a coding agent or folder strcutre? Jump into Module 4 This is a good starting point if you want to work through a practical example. The short videos mix animation with actual app screenshots, and there’s a fictional practice folder you can follow along with. - 4.1: Install and First Use — Get oriented and try your first task. Grab the Foundation Practice download from Resources here. - 4.2: Working With Files — Turn meeting notes into a decision list, then check where each decision came from. - 4.3: Think, Then Build — Compare your options, choose an approach, and approve a short brief before asking for the finished work. - 4.4: Project Instructions — Leave useful instructions with your project so you have less to explain next time. - 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.

We have been left with no other choice but to temporarily set the DM's to LEVEL 5. If you need further assistance you can always DM one of the admins. Thank you for your patience in this matter

You built your first folder. Vote below, then drop a screenshot in the comments so we can see what you came up with.