Thank you for commenting and reading my post about synthetic voice. It sure is a topic that will only keep growing (as we already know that actor voices are used, which is a synthetic voice that just sounds as good as them). Here is a video I made in 2015, I recorded the audio and had hired a VA to help make the video. It took a week and $200, and considering I made 4 videos in that series, you can make the math. Compared with the video that my ICM made, which is claude at $109 and Elevenlabs at $11. I probably have a huge bias because I am blown away by what technology does, even with a synthetic voice. Would love your opinion.

Welcome to Clief Notes. Here’s where to start. 👋 You don’t need to watch the entire classroom before trying something. Pick a starting point, make something small, and bring your questions back here. 🧭 Find your way around Navigating the Course shows you what’s here and how to get around. If you’re new to working with AI, start with The Foundation. We work through prompting, context, and organizing your files so you can give an AI a job you can actually check. 🛠️ Never ran a coding agent or folder strcutre? Jump into Module 4 This is a good starting point if you want to work through a practical example. The short videos mix animation with actual app screenshots, and there’s a fictional practice folder you can follow along with. - 4.1: Install and First Use — Get oriented and try your first task. Grab the Foundation Practice download from Resources here. - 4.2: Working With Files — Turn meeting notes into a decision list, then check where each decision came from. - 4.3: Think, Then Build — Compare your options, choose an approach, and approve a short brief before asking for the finished work. - 4.4: Project Instructions — Leave useful instructions with your project so you have less to explain next time. - You’ll find guidance for Claude Code and Codex, plus a regular chat route where you save the files yourself. 💬 Use the check-ins At the bottom of the lessons, you’ll find polls and discussion posts. Share what you tried, what worked, and what needed correcting.

Thank you Jake Van Clief and David McDermott for having me, and David Vogel for the Hermes assist. This one is ICM in practice. I open my own Hermes and walk every layer of its memory, live: the built-in memory files, session history, skills and the curator, the memory provider I host myself, and the ICM workspace that holds the job itself. The part I think this room will care about: in my workspace, every folder carries a small AGENTS.md router that points to a CONTEXT.md contract. Hermes loads AGENTS.md on its own. It doesn't load CONTEXT.md, so the router is what makes sure the contract gets read. Small router, real instructions 1 step away. Watch it here: https://www.youtube.com/watch?v=GtROa4PfvY8 ICM is why this system holds together, and Hermes is what walks it. Jordan The read through https://agentsasfolders.ai/blog/ai-agent-memory-hermes/

I watch Clief’s JEV video and it was brilliant. I was hooked the whole way through. Thank you for that post. I’m now left wondering where and if it fits into ICM since a primary responsibility handled by ICM is effectively routing the AI model/harness through the file/folder structure…and JEV is a general categorizer …so in the example in the video…JEV is dumb but brilliant at sorting things into categories like data to its associated department but incapable of much else so it’s placed as a preprocessor to the LLMs for efficient and cost savings advantages. My thinking now is how do I use JEV to supercharge the ICM routing we already do? Am I thinking about this correctly? Am I missing something?

made a short on a rule i now write into the CLAUDE.md before any automation build. if u just ask Claude Code to build an automation, it will often reach for a model call at every step, bc it can. reading an email, checking a total, saving a row, sending a receipt, all thru the LLM. the split from the video. judgement goes to the agent, rules go to code. in an invoice flow only one step needs judgement, reading the messy email and pulling out the amount. checking the total, saving it, sending the receipt never change, so those are plain functions. what worked for me is listing the steps in the CLAUDE.md with a tag on each, agent or code, before it writes anything. then Claude builds the code steps as normal deterministic functions and only calls the model where i said so. the build gets cheaper and way easier to test. do u put rules like this in ur CLAUDE.md or decide it as u go.