User
Write something
Afternoon Tea is happening in 6 days
Pinned
Did Google Steal my research?
Personally. No I don't think they did, I think the researchers are discovering what I did already ! And I'm happy they are. I would love if you all could comment, share or tag Google in this though as I would love to work with them ! Video below. https://cloud.google.com/blog/products/data-analytics/how-the-open-knowledge-format-can-improve-data-sharing
Pinned
Welcome to Clief Notes. Here's where to start.
1. Watch the intro video and introduce yourself in the intro post here 2. Start with The Foundation (free course). 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, move to Implementation Playbooks (Level 2). When you're ready to build your own tools, Building Your Stack (Level 3). 5. Post your work. Ask questions. Help others when you can. What are you here to build?
Poll
6639 members have voted
Pinned
I'll never post one of these videos on YouTube again.
This is a recording from my VIP sessions in my community I usually don't post these online so that we can talk about personal business things, but I felt I wanted to share this one. I will never be sharing these publicly again. For my VIP members if you want your files I promised they are uploaded at the bottom of the drawing room post in a ZIP here: Session 8 6/13/2026 - The Drawing Room (VIP) · Clief Notes Time stamps: 00:00 Welcome: the Ledger and the ICM deployment layer 02:11 Member intros and what people are building 04:07 Engelbart, 1962, and software as collaboration 08:15 Fable pulled, and why output beats features 15:18 Getting unstuck on ICM 19:47 The three questions and a live ICM routing demo 33:08 AI as your runtime, humans in the compute layer 38:40 Productionize your opinion 41:40 Ingest agents and distilling your brain into files 46:39 You are not behind 49:23 London Tech Week: the rooms and the money 52:27 The buyer is changing: selling to agents 54:08 Everyone is overbuilding, and the talent layer opening 61:13 Placement fees, freelancing, and the college problem 66:47 No "best," and a bet on humans 70:05 Chicago: hollow output and the 60/30/10 rule 73:53 When to hire a human instead of automating 78:27 SkillOpt: training your skill files 90:29 Launching this week, and close
🏆 WEEKLY COMP #7: THE OPERATOR 🏆
🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. ---- 🇬🇧 We're back. Good morning from London. 👋 Thanks for the patience last week. Jake and I needed a few days to breathe before London Tech Week kicked off, and you all responded with nothing but support. We don't take that for granted. Now let's get back to building. ---- 📋 THE CHALLENGE Build a folder-based AI operator that handles ONE operational workflow end-to-end. You pick the workflow. This week's deliverable is one operator folder that someone could drop into a Claude project and use to handle a real business workflow without babysitting. ---- 🎯 PICK YOUR WORKFLOW The workflow is yours. Pick something specific. Pick something you'd actually use. A few sparks to get you thinking: - 🎫 Customer support triage (which tier handles this ticket?) - ✅ Content review and approval - 📨 Lead intake and qualification - 💸 Refund request handler - 🤝 Partnership pitch evaluator - 🎙️ Podcast guest pitch sorter - 💼 Freelance project intake - 📄 Resume screen for one specific role - 📅 Meeting request triage (book, decline, delegate) The more specific, the better. "Customer support" is too broad. "Refund request triage for an ecommerce store doing under 200 orders per month" is right. 📎 If you want a fully written client brief as a reference, the attached PDF walks through one example. Don't build the example. Use it as a template for how to think about scoping your own operator. ---- 🗂️ 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. Your operator is a folder with five things: - 📄 identity.md (who the operator is and what workflow they own) - 📐 rules.md (the decision logic: criteria, edge cases, escalation rules) - 💬 examples.md (decisions in action, including at least one edge case) - 📚 reference/ (checklists, templates, rubrics) - 📖 README.md (how to use it)
I gave a Three Hour Lecture today
Hello everyone! I gave a three-hour lecture today for JT Fox and his webinar on AI and Employment. For those of you who attended I would love to hear your thoughts! Explain to others here in your own words what you learned! (slide deck attached) !!!!!Disclaimer!!!!! I did not agree on selling anything WITH him yet, we meet tomorrow at his office in person to decide if we want to work together more! if you are purchasing anything with him that is fine! but know I am not in the deal structures or part of his sales as of now and can not endorse what he is selling until I see more of it! !!!!!Disclaimer!!!!! Waiting on him to give me the video asap so I can share it with you all on my YouTube!
1-30 of 1,773
Clief Notes
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)
Powered by