Pinned
👑
Jul 1 •
Welcome to Clief Notes. Here's where to start.
1. Go check out 📚Navigating The Course to see how to get around and what's here. 2. Start with The Foundation. Concepts, folder architecture, prompting framework. Everything else builds on this. 3. Check in at the bottom of each lesson. Polls, discussion posts, other members working through the same stuff. Use them. 4. When you're ready to build real things join in on our Biweekly competitions and win some real cash. ⭐ Competitions Mega Thread 5. If you are wanting to dive into the masterminds, grab all the past templates, artifacts and resources. Upgrade and head into the The Vault for Premium and The Drawing Room (VIP) for VIP 6. Post your work. Ask questions. Help others when you can. What are you here to build?
Pinned
👑
10h •
I have a request for my VIP and Premium Members.
You can now leave reviews on the about page (only paying members which is a little annoying but that's Skool settings not mine) It would seem there is a review page, even if you may not be staying long or have gotten your fill out of the content, if I have helped in any way please leave a review by clicking on this link to help others understand what is in here! https://www.skool.com/cliefnotes/about
Pinned
👑
2d •
🏆 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.
👑
2d •
🏆 COMP #10 RESULTS — THE DIAGNOSTICIAN 🏆
34 entries. Jake, Don, David on isolated piles, then a panel. This one was hard. A few of you built things that would have won a different competition, and you should hear which one. Every entry got feedback, link at bottom of post! 📋 What we actually judged The post asked for one folder a stranger can drop into a Claude project. identity.md, rules.md, examples.md, reference/, README.md. It reads something broken and says why. Not how to fix it. Four questions, from the post: 1. Does it diagnose? One cause. Not a list. Not a prescription. 2. Is the domain specific enough to be useful? 3. Does each file do one job? 4. Can a stranger figure it out? That is an outcome. Can a person who is not already in your head use this to see why something in their world broke. A lot of the field went further. Refusal paths. Verifiers. Blind runs. Preserved failures. Those are real, and they are extra. We did not pick a winner on the extra. We picked a winner on the ask. this does not mean extra is not better, in many cases I LOVED the solutions created. If the outcome had been different, the name on this post changes honestly 🥇 Winner: Colm Whelan — Inbox Autopsy https://github.com/RockfieldIT/inbox-autopsy A stranger holding a bounced invoice can drop the folder in and see why it bounced. That was the assignment. 🔄 Where someone else wins 🔧 If the outcome was "the instrument that can prove itself wrong" — Sergey Manevitch, Radix https://github.com/sergeymanevitch/Radix Why a machine failed in a plant that already has notifications, rounds, and historian trends. Fourteen cold runs. He left the breaks in his own claims standing. A plant engineer is holding something serious. 🧪 If the outcome was "every claim reproduced, including the one that failed" — Pemmy Broke, Visual Momentum https://github.com/hoodwanders/visual-momentum-diagnostician Why an AI explainer lost momentum. She published the run that broke her own doctrine, changed the rules, and the re-run abstained. That is the standard the rest of the field should steal from.
10d •
First paid project!! Wohoo!
Following a meeting today with an existing IT services and cyber security client, I have come away with the go-ahead to build an ICM to address a particular issue that exists within their business and within their industry as a whole. The client doesn't understand what an ICM is but I demonstrated an internal ICM that we use to him, and he was quite taken by it. The problem they are trying to solve is the management of what are called EOT claims in the construction industry. A delay happens in a construction project e.g. a subcontracting company arrives on site a few days late. Materials are delayed. There's some planning problem. There's some code problem. That kind of thing. These delays then have a double knock-on effect. They affect the contract between the subcontractor and the main contractor, and the contract between the main contractor and the customer. There may be, there often are, financial consequences to these delays that are covered in clauses in the contract. The job of this ICM is to take a standard delay report (we also need to build a GUI for this, as they are currently submitted, willy-nilly) from a monitored mailbox, and based upon the standardized delay incident details contained in the report, locate the appropriate upstream and downstream contracts and examine them for clauses or language that refer to delays. It will generate a human-readable report for the project manager detailing what has happened, what contractual impact it may have, and what to do next and post that to a Teams channel. That's the first stage: the proof of concept that's also a working product and process. Questions welcome.
1-30 of 3,137
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
1
+1133
2
+857
3
+662
4
+566
5
+521
Powered by