Folders, not frameworks: how Taurus makes Claude repeatable for a whole team Giving an AI agent the right context at the right moment is still the hardest part of using coding agents like Claude Code in real, daily work. We've all felt it: the agent is brilliant when it knows where it is, and frustrating when it doesn't. So how do you give it that context — reliably, for more than one person? A small team will work but what happens when you try to on-board 100+ people? The popular answers don't scale. Elaborate memory systems help a single power user, but in an enterprise they become a liability: they're hard to curate, easy to pollute, and brittle the moment you add more people and more projects. And anything built around one person's bespoke setup — their servers, their wiring, their mental model — is expensive to onboard a whole team onto. Honestly, the wheel hasn't been invented yet. Nobody has a clean, proven answer for how context should work at enterprise scale. This is where the Interpreted Context Methodology (ICM) changes the conversation. Its core idea is deceptively simple: folder structure as agent architecture. Instead of orchestration code or a sprawling memory store, the context lives in the folders themselves. A workspace is just numbered folders for each stage, with markdown files (CLAUDE.md, conventions, reference material, working artifacts) that load in layers when an agent starts there. The agent reads downward and stops when it has enough — typically 2–8k tokens instead of 30–50k. You "configure the factory, not the product": set the workspace up once, then every run reuses it with new inputs. Outputs are plain text, editable, reviewable at every step. ICM is elegant because it's filesystem-native and human-readable — a non-developer can reshape a workflow by moving files. But it has one practical dependency that's easy to overlook: When you add more and more folders agents begin to skip information. Guidelines are missed, rules are overlooked. What worked for one person doesn't work for another because the model scans economically and thinks it knows enough. The solution is again simple, the agent has to actually start in the right folder. Start in a central place and the layered context never loads; start in the right place and the agent is instantly grounded. In a team, "just cd to the correct directory" is exactly the kind of invisible, error-prone step that breaks repeatability.

Hey everyone, Paul here. I wanted to share where I'm at and lean on the collective brain in this room. By day I'm a clinical data science lead in pharma - the kind of role where my "job description" is basically a small anthology. I'm across clinical data management, EDC builds, protocol and CRF work, SDTM datasets, sponsor interactions, and a lot of cross-functional fire-fighting. It's a mission-driven organization and I care a lot about the work. On top of that, I'm trying to really learn the sponsor management side of the industry while leveling up on AI/ML and agentic workflows so I can bring more structure and leverage into our development programs. Here's the honest part: I'm genuinely excited about all of it. The possibilities feel huge. I'm also struggling to focus, and I've gotten a bit gun-shy about shipping my first real ICM build. I've been playing with a bunch of ideas, drafting files, sketching workflows, and spinning up partial architectures... but I keep stalling right before I commit to, "this is the first build I'm going to ship and actually use." It's not lack of interest. It's that my world is wide, and every time I pick one use case, ten others raise their hand. Then I start second-guessing whether I chose the "right" one. I see how people here go from foundations to real systems, and it's both inspiring and a little intimidating. So instead of staying in my own head, I'd love to ask directly: Q: What actually keeps you focused when your work covers a lot of ground? (Vote below, and share more in the comments!)

So yeah, it took me a little while, but I now fully see how ICM truly works. This has ruined me for everything lol. My God this is awesome. I will never code the traditional way ever again.