So, yesterday I delivered a presentation to a family that requested a Wealth Development Analysis. I took 18 years of their Tax Returns to understand their past, and projected their next 25 years based on diferent economic scenarios. I've used Cowork, Code and Design. It went great, but this is not the main topic here. I've recorded the whole 100min meeting, transcribed it, uploaded to Claude, and asked it to analyze the whole meeting. I asked questions like: What is my style of presentation? Where did the storytelling worked and didn't work? What was the impact of my presentation on each participant? What didn't I see during the meeting? What a system's thinker would tell me about the meeting? The output was amazing. I got deep, lengthy feedback that will help me improve in my next preparation and presentation. It felt like closing the loop. So, don't stop at delivery, add another step of self-reflection in order to keep evolving!

I am working on 4 different projects using mainly Claude Code and CoWork. Two projects are personal and two are for clients. I understood that I need to be in the loop to make important decisions (strategic, operational, aesthetical). So, I tell my agents to show me their work stept by step, present pros, cons, unkowns, and ask for my decision. So, I spent my day answering questions from my agents as the present me their work, just like a CEO would spend their day answering questions from its direct reports. Sometimes they are high level questions, sometimes they are detailed quesitons. I might be able to automate some of those decisions in the future, but now I understand where do I need to spend my time and how important is our capacity to make decisions about complex issues.

For those who missed the first post or just joined: The Lyceum is a 12-week program we're building. Live instruction from Jake and the Eduba team. Small cohorts. Real projects. You build something from week one, not watch tutorials. At the end, a competition with real prizes. Eduba's first certification, backed by the same methodology we've used to train Fortune 500 teams. Now here's what we've locked in since then. The Structure Three 4-week sprints with a 1-week break between each. Not 12 straight weeks of grind. You build, you breathe, you come back sharper. - Sprint 1: Foundation — Core methodology. Everyone starts here. - Sprint 2: Application — You're building. Real project, real progress. - Sprint 3: Capstone — Finish what you started. Demo day prep. The breaks aren't fluff. They're built in so you can catch up, refine, or just live your life without falling behind. The Cohorts Same curriculum across all three. The difference is where your hours go. Technical — Developers, engineers, technical founders. You're building a tool or production system. 30% of your time goes to Claude Code and integrations. Another 30% to production systems and capstone. This is the builder track. Business — Ops, managers, founders, consultants. You're automating a process or designing a system spec. Heavy emphasis on workflow design (30%) and decision frameworks (25%). You direct the work without writing the code. Creator — Marketers, educators, solo operators. You're building a content production system. One person replaces the team. 25% on content pipelines, 20% on workflow design. This is how you scale yourself. Pick the track that matches how you work. The methodology transfers no matter which one you choose. A 4th Cohort? We're considering adding a team cohort if there's enough interest. This would be for companies that want to enroll multiple employees, or for people in the community who want to form their own team and build together. If that sounds like you, let us know in the comments.

Brought Vera back on Sonnet and first thing she does is survey the damage.

A friend of mine sent me his girlfriend's process manual, a Word doc describing how her franchise implementation company operates. I fed it to Claude along with Jake's paper on Interpretable Context Methodology (ICM). In one Cowork session, Claude built the complete folder-and-file system: 5 pipeline stages, templates, checklists, escalation rules. I had Claude generate two HTML manuals: an operations guide explaining the system to her (the business owner), and a separate onboarding guide for her human assistants. From a single process document to a fully structured, AI-ready operational system with documentation for people who've never used AI before. I sent it all to my friend. I will let you know if his girlfriend decides to implement. If so, I will be managing the implementation and the improvement process. (check out a page of the manual below. sorry but it is in portuguese)