⭐ I am waiting on some feedback on this, I could be off with my read, I am willing to be wrong in public so we can all be right when we are building in private! The rules feel like they contradict each other week to week. They don't. 📍 WEEK 6 AT A GLANCE — THE RESEARCHER https://www.skool.com/cliefnotes/weekly-comp-6-the-researcher?p=fa674d82 🔬 Build: a single folder-based AI researcher for ONE specific domain (you pick). Five files, single folder — so no handoff.md and no context.md this week. 🚫 The angle: a researcher is NOT a summarizer. It asks what's missing, questions the framing, weighs sources by credibility, and asks clarifying questions before it produces. That lives in rules.md ⚖️ New wrinkle this week: judging adds "does it weigh sources / flag uncertainty?" — bake that into rules.md. 📨 Submit: public GitHub repo + 2-3 sentences on what your researcher covers and what work it's best for. 🎟️ Prize: a free Lyceum seat (pick cohort — Technical / Business / Creator). 📅 Due: Sunday, May 31, 12:00 PM EST (shifted for Memorial Day). Winner Mon June 1. Premium + VIP only. 👇—My Take Below! How the rules have read to me since my first entry and getting a bit of clarity🔮 💡There's a spine that never moves and a set of dials that change every Sunday. Once you can tell those apart, the whole thing gets a lot less stressful. ⚠️This is the post I wish I'd had before I submitted, hopefully it brings clarity to an awesome community opportunity! These competitions are like mini boot camps, the tools you take away compound. 🧩 One part to focus on is the use of: context.md 📑The lessons teach ICM with a context.md in basically every directory. Then the comp spec lists five files identity.md, rules.md, example.md, reference/, README.md, and context.md is nowhere. 🤔 So, you sit there wondering if the spec is wrong, or if you're supposed to "know better" and add it. ⚠️ Here's how I am seeing it fits. context.md is a routing file. Its whole job is navigation: in a multi-directory system, it tells the AI what lives in a given directory and where to find it. It earns its place when there's enough material that the AI would otherwise waste effort hunting.

The last post I made was about the "what" and "why" of ICM. This one will be the "how." Actual folder structures, actual contracts. (If you've been wanting to try this but didn't know where to start, this is your blueprint.) ⭐ I'm going to walk through a real use case: (➡️ Adapt this to your own SOP) (Client) You're an IT Manager at a life sciences company and you need to automate SOP (Standard Operating Procedure) change control. If you've worked in pharma, biotech, or medtech, you know this pain. A single SOP change touches document control, impact assessment, reviewer routing, training assignments, and compliance sign-off.(or its supposed too anyway 😅) It's manual, it's slow, and it generates audit findings constantly. 📝Note* Every audit finding costs real money and real time. A single finding can trigger a CAPA (Corrective and Preventive Action), which means someone has to investigate the root cause, document the fix, implement the fix, verify the fix worked, and then prove all of that to an auditor. That's hours of work per finding, across multiple people. 🥅 The goal of the workflow below is to take an SOP change request, from the moment someone submits it, all the way through to a revised document with the right reviewers assigned and the right people flagged for retraining, without a human having to manually route, classify, chase approvals, or figure out who needs to be retrained. We're going to build an ICM workspace that handles the intake-to-approval pipeline. And we're going to do it using the 60/30/10 ratio so you can see exactly how the layers map to real architecture. Now for the 👇 🗂️ The Folder Structure ( Your 60%) ← ✅ This is your deterministic (predictable) infrastructure. It doesn't change, it doesn't need AI, and it does most of the heavy lifting. sop-change-control/ ├── CLAUDE.md ├── CONTEXT.md ├── _config/ │ ├── compliance-rules.md │ ├── reviewer-matrix.md │ ├── sop-template.md │ └── training-requirements.md ├── references/