🏆 WEEKLY COMP #11: THE CARTOGRAPHER 🏆

👑

🎟️ 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.

This week is the sixth form. The system map.

A system map is not a company chart and not a run. It is a walkable graph of a folder someone will change. A repo. A vault. A client delivery. A scenario pack. A set of SOPs a contractor has to inherit.

The catalog is small on purpose. It points. It stores almost nothing. The cards live on the shelves. One reader walks in, asks one question, opens one card, and stops.

Nobody photocopies the library into a backpack. That is what context-stuffing is. That is what a 100,000 line codebase feels like to a new developer and to a model. The map exists so neither of them has to eat the tree.

If you load the ICM Architect skill and use it, that is the form it should pick. System map. Not pipeline. Not context map. Not a knowledge bundle of how you think.

Using the skill this week teaches you four things, whether the output is five cards or fifty.

1️⃣ Inventory before cards. You do not write the map until you can say what the nouns are and what is dead.

2️⃣ Live, leftover, ghost. A name on a file is not a live object. Ghosts are tripwires. Leftovers are honest. Mapping a wish as live is how the next reader implements the wrong world.

3️⃣ Hits / Does not hit. Every card names what a change touches, and names the obvious next noun that is the wrong one.

4️⃣ Catalog, then one card. If your README says load everything, you built a brochure. The skill will fight you on that. Let it.

You do not need to ship a map of a giant codebase. The one that inspired this week is far more advanced than the assignment. Three real noun cards that cite source beat a fake city.

🚫 TWO HARD LINES THIS WEEK

The input is not a failure. If you start from something that already broke, you built last week.

The territory is not the methodology. If the map is of ICM, of a skill, of a Claude project, or of a folder system about folder systems, it is out. Use the method. Do not map the method.

🗂️ THE METHODOLOGY

If this is your first comp, welcome. Here's what you need to know.

This week (and every week) you're learning interpretable context methodology. Folders as architecture. Each file does one job well.

You may use the ICM Architect skill. If you do, tell it the repeating unit is a folder someone will change. That is how it knows to build a system map and not a pipeline. https://github.com/RinDig/icm-architect

Whether you use the skill or you hand-build, the cartographer folder still has five things:

📄 identity.md Who the cartographer is. What kind of territory they can walk. Who the later reader is. Say out loud that the later reader may be a model.

📐 rules.md How they map. What counts as a noun. What counts as a movement. How they mark live vs leftover vs ghost. How they write Hits and Does not hit. How they refuse to copy the source into the card. How they refuse to slurp the shelves.

💬 examples.md One worked map of YOUR territory. Small is fine. Show the catalog. Show two or three noun cards. Show one ghost or leftover if you have one. Show one change and what it hits.

📚 reference/ The closed set of card types. The walk order. The naming collisions in this territory. Chat is not always Chat. Write the collisions down.

📖 README.md How a stranger uses this. What to feed it. How a cold model should walk. The one rule: load the catalog, then one card. Never the whole objects folder.

Drop the folder into a project. Point an AI at the body of work. The AI then becomes the cartographer.

The map it leaves behind is the product.

🔥 THE ANGLE THIS WEEK

A cartographer is NOT a diagnostician.

Last comp was The Diagnostician. That one works backward from a failure and names the cause.

This is different. The cartographer works from a body of work that is still in force. The job is to make it wanderable.

A cartographer is also NOT a tour guide, NOT an auditor, and NOT a second spec.

Three things separate a real map from those:

1️⃣ It has a catalog and doors, not a plot. A cold reader can ask what is X and land in two hops. If they have to read it top to bottom, you wrote a tour.

2️⃣ The cards cite the source. They do not replace it. If the card and the real file disagree, the file wins and the card is wrong. A map that copies the codebase into markdown is a photocopy, not a map.

3️⃣ It tells you what else moves. If you change this, it hits these. It does not hit that, even though that is the word everyone will reach for. Without that line, you wrote a glossary.

A cartographer does not walk the building for you. They hand you the catalog so you can walk it. That's the job. 🗺️

💼 WHY THIS LANDS ON YOUR RESUME

A new developer cannot hold 100,000 lines. A model cannot either, not in one gulp, not usefully.

The people who get paid are the ones who can leave a map the next person, or the next model, can enter without a two-hour call.

I built a system map so a cold reader can change [this] without slurping [that] is a portfolio line. It shows you understand context as architecture, not as a bigger prompt. 🚀

Win or lose, you walk out knowing the sixth form, and you have a map of something you actually own.

📐 THE BAR

Point your cartographer at a real body of work. A stranger, or a cold model with no memory, should be able to do all four of these.

Find the front door from the catalog.

Open one card and know what the thing is, and why it is shaped that way.

Name what else moves if they change it, and what the obvious wrong neighbour is.

Stop. Without loading the rest.

If the output is a story of how the week goes, you built a tour guide.

If the output is a list of everything wrong, you built an auditor.

If the output names why something failed, you built a diagnostician.

If the output is a second copy of the source in nicer prose, you built a photocopy.

If the README says add every file to the project, you failed the one rule.

None of those are the assignment.

📝 HOW TO SUBMIT

Drop a public GitHub repo link in the comments. Plus 2 to 3 sentences on what body of work you mapped, and who the later reader is. If the later reader is a model, say so. That is not a lesser answer. That is often the real one.

If you used the ICM Architect skill, say that too. We want to see what the skill taught you, not whether you hid it.

⚖️ JUDGING

Four things we're looking at:

✅ Can a cold reader wander. Catalog, then one card, then stop. Hits and Does not hit are present. Ghosts are marked.

✅ Is the territory real and specific. A body of work someone will change. Not a failure. Not the methodology.

✅ Is the methodology clean. Each file does one job. The map cites source. It is not a second spec.

✅ README quality. Can a stranger, or a cold model, figure out how to walk this without you.

🎟️ WHO CAN ENTER

Premium and VIP members only. No exceptions.

🆓 Free members watching this thinking I could win that? You're probably right. This week's prize is a free Lyceum seat. That's the same program biz owners pay full price to access. Upgrade to Premium and you're in the running.

📅 DATES

⏰ Submit by: Saturday, August 25th, 11:59 PM EST

🎉 Winner announced: Saturday, September 1st

Every entrant gets individual feedback this round, not just the winner.

🚀 One last thing.

Week 9 was The Editor. Week 10 was The Diagnostician. This week is The Cartographer. Different muscle. Same methodology. New form.

Editors make work better. Diagnosticians tell you why it failed. Cartographers leave a map a new person, or a cold model, can wander without eating the tree.

You cannot edit a room you cannot find. Map it first.

LFG 🚀

16 comments

🏆 WEEKLY COMP #11: THE CARTOGRAPHER 🏆