Been quiet for a reason. I got flown out to New York to work on a project with a major artist. Grammy-level work. Can't say who yet (NDA), but if you know your way around Wu-Tang or Def Jam circles, you might be able to guess. I've been in the studio every day working on the album with them, building out the tech side of something that hasn't been done before in the music industry. Tomorrow's VIP High Tea session I'm breaking down how this deal came together, what the tech stack looks like, and how AI is opening doors in entertainment that didn't exist a year ago. I'll also be answering questions from the Google form submissions. If you've been on the fence about VIP, this is the session to show up for. See you tomorrow ✌️

You built your first folder. Vote below, then drop a screenshot in the comments so we can see what you came up with.

With the AMAZING support of you all in the last 24 hours upgrading to premium and VIP I decided to double down and drop some SERIOUS value for all of you for free as a giant thankyou and Proof I will work hard for you all. Yesterday Anthropic accidentally shipped the full source code for Claude Code inside an npm package. 512,000 lines of TypeScript. The entire CLI tool: every tool, every command, every system prompt, every unreleased feature flag. It was mirrored across GitHub within hours and Anthropic is now filing DMCA takedowns to pull it back. I spent the day going through it. Attached is a resource guide with every major repo, the best independent analysis posts, a table of the specific files worth reading, and a security warning you need to read before you touch any of it. Here is what matters for this community. ✨What it is: The source code for the Claude Code command line tool. The orchestration layer. How it manages conversations, picks tools, handles permissions, compresses context when the window fills up, and coordinates multiple agents working in parallel. This is production AI tooling at scale. ☄️What it is not: The Claude model. No weights, no training code, no API backend, no safety infrastructure. This is the client that talks to Claude, not Claude itself. If Claude Code is a car, we got the dashboard and transmission. Not the engine. 💯Why it matters for builders: 90% of this codebase is traditional software engineering. TypeScript, React, Zod validation, file I/O, error handling. The AI is maybe 10% by volume but most of the user-facing value. That ratio should sound familiar. It is the 60/30/10 in practice. The hard problems are not prompt engineering. They are context management, permission architecture, tool orchestration, and figuring out when to compress, when to truncate, and when to let the human decide. 🤫 Why I think it might be a marketing stunt: Every major feature that leaked (an always-on background agent called KAIROS, a tamagotchi pet system, 30-minute autonomous planning sessions, multi-agent coordinator mode) is now getting free press coverage across every tech outlet. These features are fully built and sitting behind compile flags. The "accident" required a specific change to the build config. And Anthropic was actively sending legal threats to protect this codebase ten days before it shipped to npm. Could be incompetence. Could be convenient. I will let you decide.

For those of you who enjoy the academic side of things, here is the current draft of the research paper I am writing that supports my "Folder" methodology in much greater detail. And for those of you who don't just copy and paste the paper into AI and have it explain it to you ha-ha. The core idea is simple. Instead of building complicated software to coordinate AI agents, you use folders and plain text files. Each folder is a step in your workflow. Inside each folder, a markdown file tells the AI what to do at that step. The AI reads the right folder at the right moment, does its work, and drops the result where the next step can pick it up. You review the output at each step and edit anything that needs fixing before moving on. The whole thing runs on your computer with no special infrastructure. For the technical readers: the paper traces this back through Unix pipeline design, Parnas's information hiding, multi-pass compilation, and literate programming. It formalizes a five-layer context hierarchy (identity, routing, stage contracts, reference material, working artifacts) and reports on practitioner findings from this community, including the U-shaped intervention pattern several of you have seen in your own workspaces. It also lays out future directions around semantic debugging and output provenance that I think will interest anyone building complex pipelines. Feedback welcome, especially from those of you running your own workspaces. [2603.16021] Interpretable Context Methodology: Folder Structure as Agentic Architecture

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?