💰 $500 CASH 💰 One winner takes it. 📋 THE CHALLENGE Build a folder-based AI auditor that checks something against a specific standard and reports where it falls short. Not your opinion of what's good. An actual standard that exists in the world. This week's deliverable is one auditor folder that someone could drop into a Claude project and use to check their work against the rules of their industry. 🎯 PICK YOUR STANDARD The standard is yours. Pick one that actually exists. Pick one you could point someone to. A few sparks to get you thinking: - ♿ WCAG 2.1 AA accessibility audit of a web page - 🔒 GDPR audit of a privacy policy or data flow - 📋 SOC 2 readiness audit of a security policy doc - 📄 Contract audit against standard SaaS data-handling clauses - 🏗️ Code audit against a specific style guide (PEP 8, Airbnb JS, Google Java) - 🏥 HIPAA audit of a patient intake process - ♻️ Brand compliance audit against a published brand guideline - 📊 Financial model audit against FAST modeling standards - 🎓 Grant proposal audit against a specific foundation's published criteria - 📱 App Store submission audit against Apple's review guidelines - 🧾 Invoice audit against a client's stated payment terms The more specific the standard, the better. "Audits for quality" is not a standard. "Audits a React component against the WCAG 2.1 AA success criteria" is. 🔥 THE ANGLE THIS WEEK Last comp was The Cartographer. Forty of you built maps where every card cited a file and a line, and we cloned the territory to check the cards against source. The ones that held up were the ones a stranger could verify. The Auditor is that same discipline pointed at a rulebook instead of a codebase. ⚖️ Every finding cites a provision the way every card cited a line. The standard is the territory. The audit is the map of where the artifact sits against it. Three things separate a real audit from an opinion: 1. The standard is external and citable. Your auditor should be able to say "this fails WCAG 2.1 success criterion 1.4.3" not "this contrast looks low to me."

It is funny to read one of my favorite newsletters, Every.to with cutting edge ai news this week in Septemrb 2026 just blog about folders systems like they are the hottest new shit and I have been in Clief Notes since April. One of the interesting layers that author describes is the dispatch layer, which he uses to orchestrate all of his 44 Agent Folders. It was a kind lie, like getting a verification because I did build a similar layer for comp 8 This is a quote from the judges in their first feedback "An idea worth naming, and it is yours: the Commons roundtable — multi-agent coordination as a human-readable, plain-text shared log with an open-handoffs checklist, " Has anyone else built a coordination layer, for the work being done, especially when it is not a direct pipeline where the outcomes feeds into the next folder. https://every.to/source-code/the-folder-is-the-agent-rerun

📦 EVERY ENTRANT GETS A FEEDBACK FILE 📦 🔍 HOW WE READ THESE We cloned every repo and pinned it to its last commit before the deadline, so nobody got judged on late work. Only two repos had any post-deadline commits at all. Cleanest field this competition has had. Then we read file by file. Identity, rules, examples, the reference layer, the code. We ran every checker in the field on our own machine. Three would not run. For eleven entries we went further. We cloned the territory, or the entrant shipped it, and checked the cards against the source. Eleven is all the field allowed. Everyone else pointed at something private, unpinned, or gone. Two of those eleven were public codebases nobody in this community controls. On one gate we planted a bad citation to see if it would fire. Comments got you through the door. The judging happened inside the folders. 📚 WHAT THE FIELD TAUGHT Three lines split forty builds: ✅ The one rule held. The brief was blunt: a README that tells people to add every file has failed. Not one entry made that mistake. Every search hit was either a rule against it or a fixture broken on purpose. Name a failure precisely and this community stops doing it. ✅ Enforcement is now the baseline. Sixteen entries ship a checker that runs offline with no API key. Last cycle that was the headline. This cycle the checkers got better. One broken fixture per gate is now normal, and the best gate also ships a clean fixture to prove it stays quiet on honest prose. ✅ The cold walk decided the round. About half the field shipped a receipt of a reader entering a catalog, opening one card, and stopping. The top of the field is almost exactly that set. A map can be accurate and still hard to walk. This week we scored the walk. 🥇 THE WINNER @Adam James The Cartographer, a map of a live GoHighLevel account, built so a VA can change one message without guessing which of a dozen lookalike workflows owns it. He wrote down his test method before any test ran. Then he did what almost nobody does. He handed his work to people who could make him look bad, and let them.

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ ($4,750 Seat) Pick your cohort. Technical, Business, or Creator. Your call. 📋 THE CHALLENGE This is a weird one, and you may feel lost at first. But it's up to you to make a map for those who come after and if there is no map, you must get lost to make one. Build a folder-based cartographer that can walk a body of work and leave a map a later reader can wander and show what that map is. The later reader is often an AI. Sometimes it is a new person. Same map. Same job. Not why it failed. Not how to fix it. Not a tour of how the week goes. What the nouns are. How they move. What else moves if you touch one. What is live, what is leftover, and what is a ghost with a name and no wiring. This week's deliverable is one cartographer folder someone can drop into a Claude project, point at a real body of work, and get back a map a cold reader can enter without reading the whole thing. 🎯 PICK YOUR TERRITORY Pick a body of work you have actually been inside. Something a new person or a cold model would get lost in. Something someone will change, not something you will only describe. A few sparks: 💻 A repo you own. Even a small one. The map is for the next developer, or the next session, that has never seen it. 📂 A client delivery folder a VA or a contractor has to inherit next month. 🧩 A Make, GHL, or n8n pack someone else will edit without you on the call. 📒 An Obsidian or Notion vault a collaborator has to add to without breaking the spine. 🧾 The live records behind how a job gets quoted, approved, and invoiced in your shop. The files. The objects. Not the story of a bad month. 🎓 A course or L&D library someone will update after you. 🏭 The asset and work-order objects in a plant system you actually touch. The more specific, the better. Maps how our business works is too broad. Maps the five objects a new hire has to understand before they touch the invoicing folder is right. 🧠 WHAT YOU ARE ACTUALLY LEARNING ICM has six forms. You have been living in the first ones. Pipeline. Coach. Editor. Diagnostician.

Open Evidence is a really large VC backed AI company which specializes in giving physicians an ai companion connected to medical journals. Its business model is give them free access and then sell their search information to big pharma. In May 2026 they shut down access to all European doctors because they were not compliant with the EU AI Act and didn't want to put the effort into being compliant. For some reason I find this really compelling to build something to fill that hole. I used ICM and Claude Code to build the backend based on the folder system and then uploaded the folders to github and had Replit connect to the repo to build and host the frontend. The app is working really well. Right now I have a few testers and not quite sure where the journey will go. I used Talisman's Ontology Pipeline to build a semantic layer, which helped the search results.