@Jake Van Clief I am building Onyx Commercial Roofing's system for maintaining our SOPs via github like you show in training. Here is what I have been able to come up with https://github.com/adib-gmap/OCR-SOP-structure-and-processes.git. Note: This is not the actual SOP's this is the Frame work built to Manage the SOP enviroment in a productive and scalable manner for our team. I have been writting sops for so long and managing them is hearding cats. Think of the SOP's as a individual soldier. I am trying to create guide for the O3 on how to manage a Company of soldier so your Company is dress right dress, not just in formation standing around, but also when conducting operations, the guide is how the Company moves as a whole. What rules the E8 is responsible for enforcing, if he wants to change them, how so? Same for E6's, E5's ect. I have been able to identify some gap, for each gap below I put in a placeholder rule. Is it right, what would you do instead? Changes and approvals 1. Major vs minor: MAJOR = someone has to do something differently; MINOR = more detail, no new obligation; PATCH = typos. Does a major change force retraining? 2. Who approves: the team owner approves MINOR; team owner + business owner approve MAJOR; never the author. Right people? 3. Safety / warranty SOPs (OSHA fall protection, manufacturer install specs): I added a qualified-reviewer sign-off. Needed, or overkill? Keeping it alive 4. Review cadence: safety/warranty every 6 months, ops 12, admin 24, plus an immediate review after an incident or repeated deviations. How do you set the S11 maintenance schedule: time, usage, or only when gaps show up? 5. Field deviations: the crew calls the PM first if it's safety or warranty, otherwise logs it within 24 hours. At the weekly meeting each one gets an outcome: one-off, coach the person, or change the SOP. Is that how you'd feed the S11 loop?

Hey guys, is there a central location with all of Jake's paper's he's written?

I started downloading and practicing the the folder structure taught here in January 2026. I used the training to immediately build tools to address my issues. Now I am where the community is trying to bring order to chaos. Before I start on a journey, we find it best practice to understand the concept and general route first to avoid guiding a team into a dead end costing man hours and team moral. We have SOP's written, guides, ect. roles employees. The big question: Post session 9 I was contemplating on how we want to structure the ICM for the company, build it by process or by team? I wanted to see how mapping the team with their underlying responsibilities and how to perform those responsibilities would compare to mapping the nodes by process and having the underlying roles responsible within the node. Contemplating and grasping the concepts of the sessions during my routes in the car.... I think I had my ah hah moment at this slide in session 12. I am pretty sure I have the battle plan, please advise if wrong. Thoughts on plan to build our companies "2nd brain" : Use ICM builder from session 9 to build the following : -org/people - Company roles (Job), employee roster(who has that job), position responsibilities(job description). -brand/voice - this is niche, offer, story, what we do, client success journey, pains, desires, company value, standard. -process - SOP's!!!! Within each SOP the user can be linked to all of the following within that step to complete the process. - Guide (video, ppt, transcript) - tools (softwares) - data bases -where data lives - this the knowledge base that holds all of the guides, agreements, Supabase data, proposals, estimates, ect... ---------------- Is there any major holes we are missing? Asking for a friend... lol JK :) Please dog me. I run on criticism.

Edited: 100+ have voted Results to follow Thank You Please take ten seconds to respond to this poll — it helps everyone see the real meta! I’ll like every comment. BONUS: If I can twist @Jake Van Clief ’s arm, we’ll pick one random commenter for 1 month of premium access — for free once we hit 100+ votes! Vote and reply! Main method you use for interacting with AI agents right now? WHAT"S IN YOUR TOOLBOX RIGHT NOW?

Hey @Jake Van Clief and everyone, I posted a question about how to implement ICM in CoWork as my organization only allows access to Cowork and not Claude Code, so the auto-hooks was a tricky thing to figure out but I think I did it. Below is the step by step process I've implemented on my work machine that mimics ICM in Claude Code nearly identically. Please go try it out and let me know if this worked for you or not. Here's the full detailed version: For everyone trying to run ICM in Cowork without CLI — here's the complete working setup from scratch, in order. Step 1 — Create your OS folder on Desktop: Open Finder, navigate to your Desktop, create a new folder. Name it [YourName]-OS. This is your permanent AI workspace. Desktop works because enterprise OneDrive syncs it automatically — you get cloud backup without any path complexity. Step 2 — Add your three core files: Place your IDENTITY.md, CONTEXT.md, and REFERENCES.md inside the folder. These are your three context files — identity, current state, and intellectual library. If you don't have them yet, you'll build them after setup. Step 3 — Point Cowork to your folder: Open Claude desktop → Settings → Cowork → Cowork files → Change → navigate to Desktop → select [YourName]-OS. This tells Cowork where your workspace lives. Step 4 — Add as a trusted folder: Still in Settings → Cowork → Trusted Cowork folders → Manage → Add folder → select Desktop/[YourName]-OS. This means Cowork connects without asking for confirmation every session. Step 5 — Set Global instructions in General settings: Settings → General → Global instructions → Edit. Paste this: "At the start of every session, read IDENTITY.md, CONTEXT.md, and REFERENCES.md from the connected folder in that order. Confirm when loaded." Step 6 — Set Global instructions in Cowork settings: