honestly i don't think the "real infra" is there yet. someone has to make it

for now github + markdown might be the best way to do it

I agree! my instincts tell me most enterprises will hop onto this in the coming months (late stave startups first, then bigger companies) until we get to 100m token context window LLMs, this is probably the final pattern

haha yea claude helped me write some of it and the other parts i just wrote by hand because i wanted to phrase things in a specific way

I think this would be solved via the team/personal context layer.

imagine the hierachy: enterprise context, team context and then personal context. each of the layer above can read/write to the layer below. while the layers below cannot access layers above

the personal context layer, for example, would have access to all your meetings and slack dms.

if a group of executives decide in a private meeting to kill a project. that should be saved in their personal context layer. And an agent proactively detects the difference from the enterprise context and asks: "would you like to change enterprise context" something like that

I agree for something like quietly killing a project. That can live in a personal or team context layer at first.

But starting a new project is a different class of problem. That is not just about storing a decision. It is about adoption across the organization.

You can record that a few executives want something to happen. But that does not tell you who will drive it, who will resist it, which teams need to buy in, or how the change actually propagates. At that point, you are no longer dealing with just team or personal context. You are dealing with organizational behavior.

That is where I think the real gap still is.

Yea I agree. for most big enterprises, you probably need robust RBAC and multitenancy. But I do think this pattern of letting agents figure out your company autonomously in some text-like format will be the core pattern going forward

Yea me too! I had a sense that something better than pure document retrieval was possible. But wasn't sure what. I spent months just playing around with various RAG techniques until coming up with this. I do think something like Glean is still needed (the agents here used Glean search API for building this context layer). but for the purposes of answering questions and building enterprise-ready agents, the ECL is probably it

Agreed on Glean still being needed for retrieval. One gap worth noting though: Glean's enterprise graph on the people side is mostly org chart and document co-occurrence data. It doesn't capture who people actually trust, who informal decisions route through, or who the real subject matter experts are regardless of title. Organizational network analysis on top of that could be a meaningful additional layer for the ECL.

Hey, OP here! I agree the idea here is pretty simple. The main insight is just allowing the agents to figure out the unfiltered truth about a company (the good, bad, and ugly). I tried many variations of this before but they all failed because it simply captured "intended process" instead of the ground truth. Still have a lot of hard problems to figure out like how to maintain RBAC and scale this solution!