🏆 COMP #11 RESULTS: THE CARTOGRAPHER 🏆

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

Test A: his VA walked the account against his notes and found nine things he had wrong. He built that account himself, his docs had already drifted, and he published the count.

Test B is the most honest receipt in the field. A true outsider, someone who had never opened a CRM in her life, read the README for twenty minutes and never reached the catalog. Her words are in the file: I didn't think that they were all related. It is on tape, with his coaching left in, untouched. He then cut the door from 904 words to 471, put instructions first, and kept the old version in the repo so you can see the exact change.

Nobody else in this field has a README whose quality is a measured result. We kept coming back to that sentence.

The cards are the other half. The Maria card describes something running on another platform, outside the mapped territory. The card marks it declined and says why: LIVE requires that the object was found in the account, no walk can change that, so this map has no standing to give the mark. Every claim on every card names who confirmed it and on what date. The receipts live outside the drop-in folder so a walk can never leak its own answers.

Adam, you made the failure of your own work the centerpiece of your entry. Nine errors in your own docs, a stranger bouncing off your front door on video, your coaching left in. That took more nerve than anything else this round.

🎟️

@Adam James

takes the Lyceum seat. 🎟️ Get with

@Shirsho Guha

for your onboarding documents.

🥈 Honorable Mentions

@Marcelo Michelsohn

, Pipeline Coral. A map of a Flask app that an events company's coordinator uses in production every day, and the most rigorously evidenced entry in the field. He ran a control. Same model, same four questions, pointed at the raw code with no map, before he changed a single card. Nobody has done that in three cycles. It got the answers right, slower and with more reading, and it found two things his cards understated. He fixed both. Then the human walk. A person who had never seen the folder worked in a text editor, with the expected answers committed before he started, and took seventy-one minutes against a thirty minute limit. The file says so, unsmoothed. Then the finding worth the whole week. After he rebuilt the map for the person, the model got faster. Six files instead of ten. On the last run it quoted the README's own rule as its reason for skipping the code. The door a person needed turned out to be the door a model uses too. That is a new result, and it came out of a comp entry.

@Jodi Paige-Lee

, job-fit-cartographer. Published seven cold walks, three failed. In one, the reader answered from the catalog row, never opened the card, and got the rule wrong. The card was right, so she rewrote the row and left the card alone. Her verifier runs the engine instead of reading it, which is how it caught demo data claiming 68 when the code returns 64.

@Duane Garnes

, bramwell-cartographer. A pipeline wrote the cards. A separate verifier resolves every citation and checks every Hits line against an extracted dependency graph. It failed his own map live: every citation resolved, and two pointed at neighboring lines that said something else. That failure sits in the journal next to the fix. The territory ships pinned, so anyone can plant a bad citation and watch it fail by name.

@Jeff Van Leenen

, wayfinder-cartographer. A live n8n sync where 183 files exist and about four run the system, and the map flags the redeploy script that would silently revert production. He has the field's best answer to the private territory problem: an index generated from the base schema instead of typed by hand, carrying the rule that if the two disagree, re-walk the base. He also made it fail loud instead of passing blind.

@Jorge Castro

, dont-read-the-ledger. The invoicing records behind his own business, shipped as a real pseudonymized export the cards cite line by line. His self test is the shape everyone else approximates: fourteen broken fixtures, each blocked by its own named check, plus a clean one proving the gate stays quiet on honest prose. The gate also states in its own output what it cannot catch.

@Alexandre Schwager

, cruise-data-cartographer. Sixty tables. The card that earns the map covers a foreign key whose name lies. The join runs, returns plausible garbage, and people have mistaken it for data corruption. Two more tables both hold zero rows and mean opposite things. One emptied when a test destroyed 640,000 rows. Nothing has ever read the other. The cards say which is which instead of letting the row count decide.

@Craig Howard

, folder-cartographer. Eight codebases with no per repo tuning, three of them public frameworks a judge can clone. We did. We cloned Express at his tag, ran his command, and the map came back clean. We planted a bad line number and his gate caught it by name. We read his card against the real file and it was right, including the wrong neighbor. His is the only entry whose cards we confirmed against source he does not control.

If your name is not on the podium, that does not mean you built nothing worth having. Read your file.

🎟️ ONE LAST THING ABOUT THE SEAT

This was the last competition with a Lyceum seat on the line. It goes to the entry that put its own front door in front of a stranger, watched it fail, and rebuilt it. That feels like the right way to close the chapter.

🚀 WHAT THIS MEANS GOING FORWARD

Every entrant gets a file. The read, what worked with the file path behind it, two fixes you can act on this week, and the one thing that would have moved you up.

One thing to carry into next cycle. Twenty-nine of the forty maps we read describe something a reader cannot open. The cards cite a file and a line, and the citation resolves for the author and nobody else. Three entrants solved it, and all three solutions are in the package: pin the territory in the repo, ship a generated index instead of the source, or ship excerpt files so the private tree never opens.

Read your file. Then read two others. The overlaps are the point.

LFG 🚀

30 comments

🏆 COMP #11 RESULTS: THE CARTOGRAPHER 🏆