User
Write something
High Tea is happening in 11 days
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
6399 members have voted
Pinned
📣 Quick Note to the Community
Hey everyone, Going to be transparent with you all. We're pausing the weekly competition this week. No comp #7. We'll be back next week with the next one. Here's the real reason. Jake and I are both on family vacations right now, and we're buried in enterprise work on top of it. We've been running 15+ hour days since this community started, and we've hit a point where we need a few days to actually breathe. This community has grown faster than we ever imagined. None of that happens without you all. The posts, the help in the comments, the bad ass builds people are shipping every week, the way you all show up for each other. It's real and we don't take it for granted. But if we're going to keep this thing high-quality long-term, we can't run on empty. A week off the comp grind so we can rest, catch up on enterprise work, and come back sharp is the right call. The 7-day leaderboard still runs as normal this week. Keep posting, keep engaging, keep helping each other. The leaderboard winner still gets the prize on Monday. Weekly comp #7 picks back up next week. We'll come back with something good. Thank you for understanding. And thank you for being here. ❤️
Pinned
🚨 You've been asking when the Lyceum opens. The waitlist is live. 🚨
The waitlist is up and seats are limited, so this is your nudge to go lock yours in. 👇 New here? Quick context. 👀 The Lyceum is Jake's live cohort program built on ICM, the methodology 35,000 people in this community are already using to get real results with AI. The short version: folders over agents. You learn the layer underneath the tools, the one that keeps working when the next model drops. Full breakdown is on the site. Here's what's inside: 🎯 Three cohorts, Technical, Business, and Creator. Same methodology, built around what you actually do. 🎥 Live sessions with Jake and a full team of instructors. ♾️ Lifetime recordings, written curriculum, and a private cohort Discord. 📜 An Eduba ICM certification you can put on your resume. And a guarantee no course makes: ✅ You leave with a working product, or the team finishes it with you. ⏳ Seats are limited and this community moves fast, so the math is not in your favor if you wait. 💡 Pricing and start dates aren't public yet. The waitlist sees them first, gives feedback on timing, and gets in before the program opens. Everything you want to know is on the page. If you already know this is for you, get on it. 🔥 👉 https://lyceum.eduba.io
Orchestration in the wild: what one line of input actually triggered
It's easy to have 1 agent that works great solo. The wall comes when you try to make them work as a team. You run one agent, copy the output, open another window, paste it in, run the next one. You're the integration layer. You're the thing holding the handoffs together, by hand, every time. I want to walk through one session where the system did the stitching instead of me, and show you the mechanics — what each step actually loaded and did — because that's the part you can build, not the part you feel. The setup was ordinary. We're scoping a project for a nonprofit prospect. Just got off a call, I had the transcript, and they were owed a follow-up with a ballpark on cost. I typed one line into the chat: "ingest this transcript and update the folder on this prospect." Then I watched what the orchestrator did with it. First, what "Duke routed it" actually means. Duke is my orchestrator. He doesn't do the work. He reads the request, decides which specialist owns it, and loads that specialist's instruction set before handing off — the role file, the voice doc, the guardrails, and whatever skills the task calls for. The routing IS the framing. When Duke "passes it to Pike," that's really Duke loading Pike's instructions into the context so the next thing that runs is a framed researcher, not a blank model with a prompt taped to it. So the transcript went to Pike, my research specialist. Pike ran the ingest skill against the raw transcript — pulled what changed since the last call, which open questions got answered, the next step, a couple of risk flags — then loaded the existing prospect folder so it added to what was already there instead of rebuilding from zero. Output: an updated folder and a clean read on where the deal stands. That updated read made the actual next step obvious — the prospect was owed a pricing email. Duke loaded Cash, my copywriter: my voice doc, the guardrails, the prospect context Pike had just refreshed. Cash drafted the email. Notice the handoff structure — Pike's output became the framed input for Cash. The folder Pike updated is what Cash read to write.
Interesting take on AI
Stumbled upon this which leads me to ponder why is AI free? What are your thoughts?
Interesting take on AI
1-30 of 1,528
Clief Notes
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by