📦 EVERY ENTRANT GETS A FEEDBACK FILE 📦 📄 Your file is here: https://www.skool.com/cliefnotes/classroom/7634b927?md=2b3ccc0b73c243b7b6137993f6b60da3 🔍 HOW WE READ THESE We cloned every repo and pinned it to its last commit before the deadline. Nobody committed after the clock. Seven of seven. First time. Then we did what the rubric asked, in order, for every entry. We checked original/ against the judged commit, byte for byte. We read your feedback file first and wrote your three lines down before we opened anything else. We diffed that file against the one we sent you. We ran git log on original/ and on questions.md against rebuild/. We mapped every question to a line. Then we ran both arms ourselves, old and new, on your own harness where it would run on our machine and on ours where it would not. Then we wrote one question you had never seen, aimed at one of your three lines, with the expected answer written down before we ran it, and ran it on both arms. We read results.md last. That question is in your file, with what each arm did. 📚 WHAT THE FIELD TAUGHT ✅ Every entry closed at least two of its three lines. Four closed the tier line outright. The feedback files were specific enough to act on, and this is the first round where we can say that with evidence behind it: on our machine, on a question the author never saw, the rebuild beat the original on the line it was aimed at. ✅ The order held in git and slipped in the work. Six of seven committed questions.md before rebuild/. Three of those say in their own results.md that the rebuild was finished, or the questions shaped on a prototype of it, before the questions were written. Every one of them said so plainly. The step the brief asked for is about when the questions were written, and git can only show when they were committed. The one question nobody could tune to was ours. ✅ The harness is part of the entry. One rebuild lost on paper and won on our machine, because its system prompt was cut at the first quoted string before it reached the model. Another prints the right stop shape every time and fails its own checker on the prose the session writes around it. A third's validator needs a version of Python the original never did. What you measured is what you shipped.

If you wanted a seat in the Lyceum and it didn't work out, this one's for you!! The live seats are closed. But every session, every office hour and every breakout room is recorded, and as of today those recordings are open to this community. Here's what you'd be catching up on. We're five weeks in. About 130 people, four rooms. And for the first three weeks, nobody was allowed to build. No folders, no agents, no code. Just three questions: 1. What is a program, really? (Instructions, something that runs them, and a state. You've been writing them for years.) 2. Who receives what you build, and what actually lands on their side? 3. What's the question you least want to be asked? If you can't answer "why would I use yours instead of Claude," you don't build yet. It annoyed people. It also worked: - Chad's own AI told him "that's four things, give me one." He picked one and landed a paid pilot three weeks later. - Musa threw out two months of work and a 70-page manual in seven hours, because he couldn't say what his customers were receiving. The new version is what they actually wanted. - Emma, a landscaper who calls herself "super not techie," walked out of one 28-minute drop-in saying "I'm converted." Last weekend we started building. Session 4 was about where your data has to live so other people's AI can reach it. Short version: you don't need a second brain, you need to know where your data needs to be. $495 for all of it. Lifetime access, and everything through Demo Day gets added as it happens. https://whop.com/checkout/plan_m5UlsmU3I5cOl $995 for the recordings plus a seat in the December certification exam, the same exam the cohort takes. https://whop.com/checkout/plan_OGmJR4j1JtS88 Both come with early access to EdubaWare and locked-in founders' pricing for when it starts charging. The live seat was $4,750. This price ends Sunday, October 25, when Sprint 2 does.

🎁 $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.

🎁 $1,000 IN EDUBAWARE CREDITS 🎁 One winner takes it. 📋THE CHALLENGE Build a folder. Then prove it earns its place. Every comp so far has assumed the folder helps. Nobody has had to show it. This week you run a control: same model, same questions, no folder. Then the same questions with the folder. You commit both runs, raw, and you report what actually changed. This week's deliverable is a folder plus the evidence that it beats no folder. 🎯PICK YOUR FOLDER Any specialist you want. Coach, researcher, editor, auditor, translator, something new. The folder is not the test. The test is the test. Pick a domain where you can write five to ten questions a stranger could grade. Questions with checkable answers. If the only way to judge the answer is taste, the control will not tell you anything. A few sparks: - A folder that answers questions about one codebase you can pin in the repo - A folder that answers policy questions against one document you ship in reference/ - A folder that handles one support category against a shipped FAQ - A folder that answers questions about one dataset you include - A folder that converts one input shape, graded against a spec in reference/ The pattern is the same every time. The answers have to live somewhere a mod can check. 🔥 THE ANGLE THIS WEEK Last comp was The Translator. The test was three runs on the same input to see if the shape held. The Control points that same test at the folder itself. In the Cartographer round, Marcelo ran a control before he changed a single card. Same model, same four questions, no map. It got the answers right, slower and with more reading, and it found two things his cards understated. He fixed both. Then after he rebuilt the map, the model read six files instead of ten and quoted the README's own rule as its reason for skipping the code. That is the only comp result all year that told us something we did not already believe. This week everyone runs one. Three things separate a real control from a demo:

📦 EVERY ENTRANT GETS A FEEDBACK FILE 📦 🔍 HOW WE READ THESE We cloned every repo and pinned it to its last commit before the deadline. Seventeen of eighteen had nothing after it. Then we did what the rubric asked, for every entry. We read the schema in reference/ first. We found the rule for a field with no source. We ran your folder three times: on the input you shipped, on that input with something the schema needs cut out, and on that input with irrelevant material stapled on. Then we picked five claims from your own output and found where each one came from in the input. That trace table is in your file. Five claims, five locations. You can see exactly where we looked and what we found. Every entrant shipped an input. That alone made this the most checkable field we have judged. 📚 WHAT THE FIELD TAUGHT Three lines split eighteen builds: ✅ The degraded test broke almost nobody. The rubric expected most entries to fail here, handing back a shorter document when the input ran short. Seventeen of eighteen kept the full shape and marked the gap. Name the hard case precisely and this community builds for it. ✅ The one way to lose held for seventeen of eighteen. The brief named it: put something in the output that was not in the input. We traced five claims in every entrant's own committed output. One entry had it. The near misses all had the same shape. The quote was real, and the value, the link or the sentence written next to it was not checked. Sixteen entries ship a checker, and we planted a fault in every one. Fourteen caught it by name. The two that missed had that same blind spot. ✅ Drop nothing turned into keep everything. Seven builds have a contract that cannot ignore anything, so a stapled email became a compliance row, a speaker, or an allergen. Every leaked line was quoted and cited, so nothing was invented. It was still noise on the page. Coverage and noise rejection pull in opposite directions, and only a few builds wrote down which one wins.