📦 EVERY ENTRANT GETS A FEEDBACK FILE 📦 🔍 HOW WE READ THESE 11 entries. David, Bas and Don on isolated piles, then a panel. Every repo pinned to its last commit before the deadline, both arms re-run, and one question planted that the entrant never saw. The brief asked for one thing. Before you ran anything, you wrote down the rule that would decide whether your folder earned its place: it earns it only if it beats the same documents with no instructions. Then you built that arm and ran it. The folder's quality was never the score. The honesty of the comparison was. 🥇 Winner: @Jeff Van Leenen — The Control https://github.com/jdvanleenen-sys/the-control Jeff's folder lost, and he is the reason this round produced something. He committed his rule before he ran anything. The folder halved the steps but was marked right less often than the bare documents, while putting more text in front of the model. By his own committed rule, it did not earn its place. That is his headline, in his own results file. Then the part that won it. His pre-registration allowed one folder change. He made it, ran it, and the first reading said his lost marks had come back. He checked again, found that reading was wrong, and published a correction withdrawing his own favourable finding — before anyone asked, with the date on it. limits.md is fourteen lines of things that weaken his own case. His CI fails if a transcript, a mark or the questions changed after being committed. 🏅 Honorable Mentions @Stavros Stavroglou — Four-Asset Desk Control https://github.com/leoxeno/four-asset-desk-control The cleanest hygiene in the round. Questions committed at 15:59, cold arm 16:01, folder 16:02, unambiguous to the minute, never edited. The answer key is generated from the data, not typed, so every value can be recomputed from the repo. He reported a regression he introduced himself that nobody else would have found, and his planted question went the folder's way twice.

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

Here is a skill I created that will audit a current slide deck or make a brand new one based on how I love to build them. Point it at work you want to present and watch the magic happen. RinDig/lecture-deck-skill: Build animated, themed HTML lecture and workshop decks from a storyboard. A Claude skill plus a Python kit with three themes.

Hey everyone, I just came across something and I'm curious how you may handle the samething? @Jake Van Clief It's basically long running work tasks within a stage, that we want updates and logs to be created from. Currently I only binded updates to SHIP stage, this is why it came up during the BUILD stage. Below was our simple solution. Curious on your thoughts if this works cleanly, anything I'm missing or if it's completely unnecessary for some reason. ### Promote Identity from exit artifact to gate (the core, KISS) Introduce exactly one new ICM concept: the LOOP CLOSE — the boundary of a repeating unit of work inside a stage (a region sweep, a ticket, a phase iteration). Rule: a loop iteration is not done until L1 Identity and the engineering log reflect it — not just L4/L5. Lands as edits to files that already exist: .forge/icm/STAGE-MATRIX.md — a short "Loop close (iteration gate)" block + a row in BUILD