Hey everyone, I just came across something and I'm curious how you may handle the samething? @Jake Van Clief It's basically long running work tasks within a stage, that we want updates and logs to be created from. Currently I only binded updates to SHIP stage, this is why it came up during the BUILD stage. Below was our simple solution. Curious on your thoughts if this works cleanly, anything I'm missing or if it's completely unnecessary for some reason. ### Promote Identity from exit artifact to gate (the core, KISS) Introduce exactly one new ICM concept: the LOOP CLOSE — the boundary of a repeating unit of work inside a stage (a region sweep, a ticket, a phase iteration). Rule: a loop iteration is not done until L1 Identity and the engineering log reflect it — not just L4/L5. Lands as edits to files that already exist: .forge/icm/STAGE-MATRIX.md — a short "Loop close (iteration gate)" block + a row in BUILD

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. 🎯 PICK YOUR DOMAIN The domain is yours. Pick something specific. Pick something you'd actually use. A few sparks to get you thinking: - 💻 Code review editor for a specific language and level (junior TypeScript, senior Python) - 📊 Pitch deck editor for pre-seed founders - 🎨 Grant application editor for arts nonprofits - 📄 Resume editor for career switchers into tech - 📰 Op-ed editor for policy publications - 🎙️ Podcast script editor for interview shows - ⚖️ Legal brief editor for civil litigation - 📋 Product spec editor for early-stage PMs - 🎓 Academic paper editor for one specific field The more specific, the better. "Writing editor" is too broad. "Op-ed editor for tech policy publications targeting a policy audience" is right. 🗂️ THE METHODOLOGY If this is your first comp, welcome. Here's what you need to know: This week (and every week) you're learning interpretable context methodology. Folders as architecture. Each file does one job well. Your editor is a folder with five things: - 📄 identity.md (who the editor is, what work they review) - 📐 rules.md (how they critique) - 💬 examples.md (what good critique looks like) - 📚 reference/ (style guides, checklists, frameworks the editor uses) - 📖 README.md (how to use it) Drop the folder into a Claude project. Claude becomes the editor. Reusable. Shareable. Portable. 🔥 THE ANGLE THIS WEEK An editor is NOT a rewriter. An editor doesn't do the work for you. An editor surfaces what's weak and pushes you to fix it. That distinction is the whole assignment this week. When someone hands the editor a draft, the editor shouldn't produce a "fixed" version. The editor should point at the three lines that don't work, explain why, and hand it back to the writer to solve. ✍️ Generic feedback like "consider strengthening your intro" is a fail. Specific feedback like "your intro assumes the reader already knows what a Series A is, but this pub is read by generalists, so lead with the stakes instead of the jargon" is what a real editor does.

I want to meet new members earlier, not months after you join. Right now a lot of people join the paid tiers and figure things out on their own. That's slower for you and it means I don't get to know you until you've already won a competition or posted in the Vault a few times. Further our Afternoon and High Tea calls 🫖 High Tea 9: The Graph the first bit of each call has been ALOT of intros and I think that eats away valuable time (not that getting to know you is not valuable) that members who have been around for a while look forward to during our live sessions. So starting this week, every new VIP and Premium member gets a standing invite to a short session with me and the mods. Calendar · Clief Notes 🕑 Wednesdays, 2pm 🎯 Open to new VIP and Premium members We'll cover: 🔑 Getting into Discord 🧭 Finding your way around 🤝 Getting the most out of other members 🏆 How to win the competitions ❓ Quick questions at the end (and feedback on what you really want out of value and such, helps me decicde if I need to add or change anything in the community) 30 minutes. One goal: you walk out knowing the community and I know your name.

🎟️ PRIZE: FREE SEAT IN THE LYCEUM 🎟️ Pick your cohort. Technical, Business, or Creator. Your call. ---- 📋 THE CHALLENGE You are the client this week. No fictional Marcus. No fictional Sarah. No fictional Devon. Pick a real problem in your own life or work. Build the folder-based specialist you wish you had. This is the capstone of Month 2. The challenge flips. Instead of building for someone else, you write your own brief and solve it for yourself. ---- 🎯 THE TWIST The hard part isn't building. The hard part is scoping. Picking the right problem is harder than solving the wrong one. Most people pick problems that are too small or too vague. The skill this week is treating yourself like a real client. Be specific about what's broken. Be specific about what you need. Don't pick "I want to be more productive." Pick "I waste two hours every Sunday night writing the same kind of LinkedIn carousel posts and I need a folder that handles 80% of the draft work so I can focus on the hook and the visuals." That's a real brief. Specific problem. Specific scope. Specific desired output. ---- 🗂️ TWO DELIVERABLES THIS WEEK This is the only week with two pieces: 1️⃣ Your own client brief. 250 words or less. Describe the problem you're solving for yourself. Treat yourself like a real client. What's broken? What have you already tried? What do you need? 2️⃣ The folder system that solves it. Same structure as every week: - 📄 identity.md - 📐 rules.md - 💬 examples.md - 📚 reference/ - 📖 README.md Your brief lives at the top of the repo as brief.md so judges can read it before they look at the folder. ---- 🔥 THE ANGLE THIS WEEK Anyone can follow a brief. Writing your own, then solving it, then shipping it as a usable folder is a portfolio piece that demonstrates judgment, not just execution. This is the skill that separates "AI hobbyist" from "AI builder." Anyone can prompt their way through a problem someone else handed them. Scoping a problem, designing the solution, and shipping it as a system is what real work looks like. 💪

Recording's up, and I packaged the whole thing so you can drop it straight into your second brain or hand it to your AI. 🍵 Here's what we got into this session: 🧠 Map your work, don't just store it. A second brain holds notes. A map holds your work plus the people and data around it — teams, processes, and the links between them. You can't improve what you can't see, and neither can your AI. 🔗 Every workflow is a node. One markdown file = one process. The references between them are the edges. That's the whole graph. 🟢 Build workflows, not outputs. Store the outputs inside the workflow. Then when Opus 4.8 or Fable ships, the right feeling is "cool, my system just got better" — not scrambling. 🔍 Google basically proved the method. Their new Open Knowledge Framework (dropped June 12) is markdown + files + front matter to document and query big datasets. One of the biggest players outside Anthropic is doing the markdown-and-files approach we've been practicing here. 👀 🏛️ Plus: mapping a real company's teams in Obsidian, the platform coming so you can own and license your workflows, and a sneak peek at my new paper — Human in the Compute Layer — built on Engelbart's 1962 work. 📎 What's attached (and what each file is for): 📝 session-notes.md — The opinionated version. All the ideas from the call, written so you can act on them. Start here if you want the short version. 📚 term-sheet.md — Plain-English definitions for every term: node, edge, semantic layer, OKF, ICM, "the data becomes the agent," and more. Perfect if you're new to the room. 📄 vault-page.md — The index for the whole package. 🗂️ Package.zip — Everything zipped, ready to add to your AI's memory (Claude, Hermes, OpenAI — whatever you run). 💬 Watch it, grab the files, and drop your questions below — the best ones seed the next Afternoon Tea. So much love. 🫶