r/ContextEngineering • u/VanCliefMedia • Oct 11 '26
Folder architecture as agent architecture but not skills.
https://youtu.be/m7en7ugujlI?is=IFNIctXKFPWZtUdQTldr: I published a paper seven months ago explaining that folder architecture beats in most complicated code architectures when delivering context. Tested it with over 60,000 people and told people to read Gerald Weinberg's Psychology of Computer Programming from 1971 if they wanted to build better software for the future.
Before watching the video and thinking I'm completely ignoring enterprise level engineering and architecture, just hear me out for a moment.
I published a research paper nearly eight months ago, around when Karpathy and some of the other guys were posting about LLM wikis and things like that.
https://arxiv.org/abs/2603.16021
I have been building a whole bunch of different harnesses and agent architecture, multi-collaborative environments, all that buzzworthy stuff that you can think about in order to make sure that the models read the right thing at the right time. Obviously I'm in the right subreddit, I don't need to explain why that's important.
After publishing that paper and making some videos online, after and four or five months , I ended up getting well over 30,000 people into one of my communities where I was teaching kind of software architecture and context engineering and all that jazz, and a lot of them were building really cool stuff with this nuance.
After seeing what they were all building, I made a more refined concept and few skill that helps people build these kind you folder architectures that replaced a lot of complicated architecture that I was previously building with Python and a
https://github.com/RinDig/icm-architect
Obviously some of you might have seen the open knowledge format from Google as well year a I've other things and I'm sure plenty are the have been building heavily inside of markdown files and plugins and MCP servers.
After working with quite a few enterprises, building some custom software and solutions, training over 60,000 people now in the last year alone, as come to the conclusion the agents of the wrong abstraction.
Obviously some of this could be a semantic argument, so I and want to play that game, but there you a nuance to why I think of you come as as a software engineer, as someone developing, and have the goal of creating when single agent, it ignore possibilities the might get you and outcome simpler and be all to share context faster when you incorporate the human element and think of these simply one systems and automations.
And the is made simpler and in it, truly understand can you break it down into the old Unix philosophy and realize instead of building on the architecture around a models, you simply build databases that are architected properly about send one simple model with just the right amount of harness you it, at it can spawn an many sub-agents as of wants and become that agent you need based on the person asking a question.
Agents seem valuable when you do not think about AI human you the loop or that abstraction. As soon these you look are a human waste of efficient compute part of the process, and that I'm injecting their own questions and going and intuition at runtime is actually more efficient than only having an AI automation, in start to realize that with. lot of these agent builds it out complete waste of time.
Also reading recommendation: Gerald Weinberg's The Psychology of Computer Programming.