🎁 $1,000 IN PLATFORM CREDITS 🎁 One winner takes it. 📋 THE CHALLENGE Build a folder that plays one specific person, so someone can practice a hard conversation before the real one. Drop the folder into a Claude project and Claude becomes that person. The user pitches, negotiates, interviews, or delivers the bad news. The persona reacts the way the real person would. This week's deliverable is one simulator folder someone could use tonight to rehearse tomorrow's meeting. 🎯 PICK YOUR PERSONA Pick someone people dread talking to. Pick someone you have sat across from. A few sparks: - 💼 A skeptical Series A investor at a healthcare-focused fund - 👔 A hostile hiring manager for a senior engineering role - 💰 A client trying to talk your rate down - 😐 A defensive employee getting hard performance feedback - 🤝 A possible cofounder testing whether you'll last - 📞 A cold prospect who picked up the phone and wants off it - 🎤 A journalist working on a critical story about your company - 🏠 A landlord who doesn't want to fix the thing - 📋 A grant reviewer with a strong view of what counts as impact The more specific, the better. "A tough boss" could be anyone. "A CFO at a Series B SaaS company who has been burned by two failed marketing hires and now questions every dollar" is one person. 🔥 THE ANGLE THIS WEEK The last five comps were heavy. Cite every line. Check against a rule. Hold a shape. Prove the folder helps. Rebuild against your feedback. This one is lighter to build and just as hard to get right. The Rebuild asked you to take hard feedback and act on it. The Simulator gives people a place to practice that before it counts. A simulator earns its keep by staying in character when it would be easier to break. Three things make a persona hold: 1. It wants something. The investor wants a 10x return and a founder who knows their numbers. The hiring manager wants to fill the seat without a mistake. Write the goal in identity.md. Every reaction comes from it.

Most of us run AI like a vending machine. Prompt goes in, product is supposed to come out. Instead the output drifts, the context window fills, and everything collapses. So we blame the model and try again. The article's punch: the model was never the answer. The structure around it is. Systems engineering kept a nuclear plant stable on a submarine, and it is the same loop that finishes pool jobs on budget, survives nonprofit handoffs, and carried me 42 days on a bicycle from California to Michigan. The loop, everywhere: 🔹 Research. Know the outcome before you touch the tool. 🔹 Declare. One page, in terms you can measure. 🔹 Cycle. Run small. Check. Track. Adjust. Add nothing yet. 🔹 Layer. Only after the core holds. Karpathy framed it for agents: fill the context window with exactly the right information for the next step. Your move: pick one system this week, write its one page, run the first cycle, and drop the page below. The comments are the course. The text is fuel. https://www.skool.com/cliefnotes/classroom/c7f102c7?md=2b72dd8a1c464a238cf995646d8b40bc #systemsengineering #contextengineering #auditable #ownYourStack #CliefNotes

I've been poking at Grok Bot before trusting it with anything real. What got my attention is that it's already built a lot like an ICM workspace. Every account gets its own computer with a /workspace folder, and the bots read and write files there. So I set one up the way I'd set up mine: an AGENTS.md at the top, a log, and some tests. Then I tried to break it. This was the web version, one bot (Scout) plus a throwaway second agent to mess with it. Here's what I found. 1. The router isn't guaranteed to get read. Scout had a note in memory to read AGENTS.md before every task. The second agent rewrote the file to v3 behind its back, and Scout's next log line still ended in v2. 2. The description box is where the instructions actually live. Think project instructions. The docs say personal bots don't have one anymore. The web app still does, and it gets read every turn. I put "start every reply with Scout here" in it and that's what it did. When I had Scout research this, it pointed out the docs line and then said, more or less, I'm a personal bot and I clearly have one that I follow every turn. 3. The chat is the memory. Each bot runs one long conversation that gets summarized as it goes. Here we close out and start fresh to control context. Over there you spin up a new bot or duplicate one, and the docs are pretty vague about it. I tried a thread to get a clean start and it still knew a code word from the main chat. 4. Any bot can change the rules. Every bot on the account shares the same workspace. I put a fingerprint lock in the description (stop if the file's hash changes) and it worked for a changed file. Then the second agent edited Scout's description box itself, and Scout can edit its own with one tool call. xAI's own FAQ says don't use separate bots as a security boundary. They mean it. 5. The log caught what the chat didn't. The reply looked fine every time. The one line per task log is where the v2 showed up.

Hey everyone!! Jake and I are rebuilding Clief Notes around Edubaware, Eduba's own platform. We're aiming to launch it between 10 December and 1 January, and if that date moves, you'll hear it here first. Clief Notes stays free to join, and always will. Here's everything else that changes, starting with the part that has a deadline. ⏰ Lock in today's prices by Sunday 15 November ⏰ Right now Premium is $11 a month and VIP is $97. Join by 11:59 pm EST on Sunday 15 November and you keep that rate for as long as you stay subscribed. After that, new members pay $14.95 for Premium and $499 for VIP . If you already pay $11 or $97, your rate doesn't change. 💰 $1,000 of Edubaware credit 💰 Every Premium member on Clief Notes through 9 December gets $1,000 of Edubaware credit at launch. Every VIP gets $5,000. It's paid in full on day one, and members on the $11 rate and lifetime VIPs get it too. Join Premium by Sunday and that's $1,000 of credit for an $11 month. Anyone who joins after 9 December doesn't get it. Premium and VIP also get founders pricing on Edubaware: 50% off your first year and 25% off your second, for as long as you stay subscribed. VIPs get 50% off for both years. 🚀 Early access, over the next few weeks 🚀 Premium and VIP members get into Edubaware before launch. We'll be onboarding people over the next few weeks, not all at once, so David and Kay can set each of you up and check in once you're in. If your invite arrives later than a friend's, that's why. Every Premium and VIP member gets one. Every Tuesday, David or Kay posts an Edubaware update here. ⭐ What Premium gets ⭐ Everything new lands in Premium first: - A build tutorial from Jake every month, one full build from start to finish - Ask Jake: post your question in the monthly thread and Jake answers the most-liked ones on video. The first thread opens Monday 16 November. - Master sessions, run live here by the Masters of ICM - The Masters' drop: a new template, workflow or walkthrough from every Master, every

Yes. I’m being forced to the dark side. I’m looking to push all of our learnings we have here into the framework of what’s possible inside Enterprise security. My first step is to add this post to the community and see if you will drop wisdom, repos, and guidance in the comments. Thank you kindly.