This is a big win for me. In the past, when Claude was down, it’d be frustraing because it usually happened in the middle of a project, and I’d feel stuck. This time, it happened to be the project that I am testing the ICM folders on. The ICM structure let me hop into Codex and it immediated picked up where things were cut off with a simple one sentence “tell me where we’re at” prompt. Codex was 95% on point with where we were in the task and next steps. The hiccups were due to confusing or missing pointers in the routing. Easy fixes. Still amazed that a “simple” folder restructure can do this. Feels so liberating. Thank you @Jake Van Clief

So, in order to move forward in AI's assistant roadmap, here is my insight about the video. A MUST for newbies. I really loved how simple the demo shows how the system works. Moving claude.md to agents.md is a smart move, and great for my case: I use Cline and Antigravity combined with Claude Code on same folders. Great work @iscalelabs!

Hi everyone! Finally, I feel like I can share what I’ve been building behind the scenes. AND I AM FUCKING PROUD OF THIS ONE! 🔥 What do you think something like this is worth? I’ve built an end-to-end contract automation pipeline that runs 100% inside the Microsoft ecosystem. The best part? There is ZERO AI in this flow. Just pure, deterministic, enterprise-grade automation that works flawlessly every single time—and costs next to nothing to run! ⚙️ How the Flow Works: Drop & Trigger: You drop a .pdf file into a specific SharePoint folder. This instantly triggers a Power Automate flow that extracts the data and generates a draft contract. Interactive Teams Approval: The person who uploaded the file receives an automated notification in Microsoft Teams. Right inside Teams, they can: - View the uploaded source file. - Review the generated draft contract. - Approve or deny the contract. - Edit key values directly (edits apply to the final executed contract). E-Signing (No Third-Party Fees): Once approved, the contract is automatically emailed to the customer with a unique link to review and e-sign. - Customers can sign using a mouse, touch screen, stylus, or by uploading a signature image. - Note: You can plug in Adobe Sign or DocuSign, but why pay per signature during testing when you can build it yourself? 😉 Legally Sound Audit Trail: The system captures and logs full verification parameters: [Signed By], [Signed At], [Signer Email], [Signer IP], [Signer Device], [Signature Method], [Document Hash], [Reference], [Approved By], [Approved At]. Final Delivery & Auto-Cleanup: Once signed, the finalized contract is emailed to both parties. The flow then automatically deletes all temporary input and output files, leaving a clean footprint where only the two emailed contracts exist. 🛡️ Built for Enterprise & Clients Bulletproof Reliability: Built-in safety features prevent duplicate entries, invalid file formats, or missing data fields.

I converted one client space to a standalone ICM workspace because I wanted to test the folder structure in just an isolated format, and it's been working so well! I am super happy with the first iteration of this. This is a client I'm developing a social media pipeline for her, so it involves: - Ideation - Lots of reference files - Creatives that are outdated - Creating new creatives - Setting up a tracker as a system that allows her to give feedback on drafts and allows us to iterate graphics - Posting to her social media platforms The confusing thing about this client is that she has a 20-year history of accounts, emails, and information, and has had multiple people managing her accounts, with no centralized source of truth. She literally does not know where information is or who owns what piece, because there's been so much turnover in the last 20 years. We've got emails, text, Slack, Google Drive, and Asana that information was coming in through, so we just needed a way to be able to track all of that. Previously, I did have a folder structure, but she was sending me information in different places, and it still felt like things were incredibly scattered. I wanted to see if we could simplify finding things with ICM and also be able to do a better job tracking without having to rely on opening up a complete third-party notion or Airtable or something like that. For the setup in Claude Code, I fed Jake’s research paper and the two videos (one of Jake's videos and the video from the Foundations course) and asked it to setup the folder structure. We then went back and forth, iterated for a couple of hours, and did some tests on the plumbing up and down the folder chain. I had it track tasks, drafts, and the production pipeline, and then did adversary reviews with dumber models (Sol, Haiku, and GLM). I figure if the dumber models can do it, then that means the routing is clear. I wanted to make sure that the routing was built for models to follow and that it wasn't relying on the underlying intelligence of the frontier models.

Hey everyone! Just go a message from my client saying that he closed a deal (he organizes events) for a major client of his, using a proposal that was 100% AI generated, using an ICM system I've created. How the system works (TL;DR) - see the images with the input and the ouptut. It's not a prompt, it's a workspace the client's team operates every day. Messages and a voice note go in; an on-brand HTML proposal comes out, and a PDF when it closes. Two human gates: one on the content, one on the rendered PDF. The AI assists, the human decides. Three rules do most of the work: 1. The AI never invents. Every sentence traces back to a message or to the operator's dictation. Missing something → it asks. Data that arrived with nowhere to go → it also asks, never decides silently. 2. The AI never sets a price. Values come from the operator, always. 3. Nothing reaches the end client without explicit human approval. And the part I like most: when a proposal closes, the system asks about every correction the operator made: "was that just this one, or is it a rule from now on?" If it's a rule, it proposes the edit to the rules file. The next proposal is born better. --- The longer version, for whoever wants the mechanics The shape is a pipeline that empties into a record library. Each proposal is one run; each finished run becomes a record the next run can learn from. Inputs. The operator drops in everything that actually arrived: forwarded client messages, supplier quotes, a voice note with their own instructions. No inputs, no assembly. First question before building anything: is there an existing proposal to use as a base, or should I search the archive for similar events? Assembly. The AI loads only what this step needs — proposal anatomy, brand voice, design rules, hard constraints and builds the HTML in the company's identity. Photos come from a catalog with provenance, never from a search; real photos of the company's own events come first, and a reference image is always labeled as one. If a photo's commercial attribute doesn't match the item being sold, it doesn't go in. What it hands back isn't just a draft, it's a draft plus a list of what's missing, so the operator knows which supplier to chase.