User
Write something
High Tea is happening in 30 hours
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
6593 members have voted
Pinned
🇬🇧 GOOD MORNING FROM LONDON! 🇬🇧
Jake and I made it across the pond. We're here for London Tech Week all week. We got invited out for this one, which still feels surreal to type. We've got multiple pitch slots in front of investors over the next few days to talk about what we're building at Eduba and where this community is headed. Big moments lined up. Big rooms. Big swings. 🚀 If you're at the conference, DM me! Would genuinely love to meet anyone from the community in person. We'll be all over the Techscaler booth and floating between sessions. Even if it's just a hello and a handshake, hit me up. 🙏 And if you've got a second, send some good energy our way this week. We're about to walk into some rooms that could change the trajectory of what we're building. Wish us luck. Light a candle. Whatever your version of that is. We'll take all of it. Now to the real reason you're here. 👇 ---- 👇 🏆 7-DAY LEADERBOARD WINNER: @Bas Rosario 🏆 🔥 Bas just won it AGAIN. Back-to-back. Last week he won as a Premium member and we converted him to free Premium for life. This week he's already Premium for life, so we're bumping him up. ✨ Free VIP for life. ✨ The Drawing Room. High Tea. Bespoke folder builds with Jake. All of it. Forever. No charge. ---- ⏰ The 7-day clock just reset. Next Monday we crown the next winner. Could be you. 🎯 How it works: - 📝 Post bad ass stuff - 💬 Help people in the comments - 🛠️ Share what you're building, what's working, what's breaking - ❤️ Engage with other members' posts The leaderboard tracks all of it. Whoever sits at #1 next Monday wins. ---- 🎁 The prize, depending on where you're at: 🆓 Free member? You get lifetime Premium, free ⭐ Already Premium? We convert your Premium so you stop paying 👑 Already VIP? We convert your VIP so you stop paying Either way, you stop paying. Forever.
Pinned
🏆 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 made a pet. His name is Gordon. 🐛
Drop him into the project you've been avoiding. He lives in a folder. Every morning at 9am he wakes himself up, checks how long your project has been sitting there, and pops up on your screen to tell you about it. Move in to a project you haven't touched in three weeks and his first words are: "i just moved in. nothing here has been touched in 23 days. the last thing was 'my-big-idea.md'. no judgment. some judgment." He names YOUR file. He counts YOUR days. Work on the project and he notices that too: "the folder moved while i slept. 'index.js', specifically. activity counts as affection. house rule." https://hubbardjoshua9-a11y.github.io/gordon-worm/GORDON.html --- He has five moods. Hopeful. Content. Peckish. Wistful. Wounded-but-dignified. Miss a few days and he goes peckish. Miss a week and you open your laptop to a slightly purple worm with drooping eyes being very brave about it. He doesn't guilt-trip. He journals about it instead, which is worse. --- His belly is an archive 🗂️ Got files cluttering your project you're not ready to delete? Drop them in his food folder and tell your agent "feed Gordon." He reads each one, has opinions, then dates and archives it out of your way. Not a bin. Still there if you need it. Just quieter. He archives them. He just doesn't do it silently. --- You can also make him talk 🗣️ Open your project with Claude Code and say "check on Gordon." He'll speak. He remembers things between sessions via his diary. He'll bring up your files by name like an old friend. --- Here's the thing though. Gordon is a fully compliant ICM build. STATE.md is the single source of truth. Nothing about Gordon is true unless it's written there. Each folder has one job and a stage contract that defines its inputs, outputs and edge cases. The diary is append-only memory the agent reads at boot. The food folder is an input gate. The belly is a write-once archive.
I made a pet. His name is Gordon. 🐛
Are API prices about to soar?
Everyone’s talking about the cheap subscriptions coming to an end thanks to new releases like Fable 5. Does anyone have less speculative news or insight as to what us freelancers and small businesses have to expect? will our businesses be unsustainable due to these rate hikes? it’s really making me question my objectives. I know there’s a difference between model subs and API costs but if our workflow becomes successful and the API costs soar then the business model shatters, no?
1-30 of 1,715
Clief Notes
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by