📦 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.

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

My son was born this week, Azrael is his name. Creation is a wild thing, I decided to spend some time (the little time I have) writing with just my own two hands as a celebration of the human life. No ai used in the script or writing, I hope y'all enjoy it. If you do please like and share and comment on YouTube.