Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Enterprise Context Layer

andychen32.substack.com

Post reply on HN
Print view View original

21–28 of 28 posts

Re: The Enterprise Context Layer

#21

Post by andychen32 »

simonjgreen wrote: post #16
condwanaland wrote: post #13

I enjoyed reading this but felt like it missed a few of the points on why a lot of companies are indexing heavily on the context layer. 1. While AI is capable of driving massive value, chatbots are very rarely the solution 2. You need much more than this sort of text data to represent an enterprise. Timeseries, SAP (and other ERPs), and general relational data is part of building a knowledge graph, ontology, etc 3. S…

Yes. This feels more like a way to produce an SMB context layer than enterprise.

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

Re: The Enterprise Context Layer

#22

Post by yumiatlead »

Love the honesty, especially around process docs describing the ideal not reality. The thing I'd push on: your agents learned data retention questions are dangerous because the history existed in the data. But what about the stuff that never gets written down at all, like whose informal veto actually kills a project? Curious if you hit that wall. Someone else wrestling with the same problem:https://behaviorgraph.com/blog/posts/the-layer-every-enterpr...

Re: The Enterprise Context Layer

#23

Post by yumiatlead »

andychen32 wrote: post #20
eddy162 wrote: post #3

Felt like this read my mind, I was shocked recently at how good Cursor (with Claude) is at answering questions given its Slack/GSuite MCP connections; and a lot faster than Glean. Also amazing to see how this can literally give better answers than some humans would.

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 pro…

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.

Re: The Enterprise Context Layer

#24

Post by andychen32 »

yumiatlead wrote: post #22

Love the honesty, especially around process docs describing the ideal not reality. The thing I'd push on: your agents learned data retention questions are dangerous because the history existed in the data. But what about the stuff that never gets written down at all, like whose informal veto actually kills a project? Curious if you hit that wall. Someone else wrestling with the same problem: https://behaviorgraph.com…

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

Re: The Enterprise Context Layer

#25

Post by andychen32 »

consumer451 wrote: post #15

This was great info, but as someone who is concerned about passing great info on to others about my own products, I am suddenly less worried about my posts reading like LLM-speak. This post did very well. I should probably stop overthinking it, and learn from this post about balance.

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

Re: The Enterprise Context Layer

#26

Post by andychen32 »

chrisweekly wrote: post #5

Fantastic article. I've always felt that institutional knowledge flow is one of the most essential factors in a given company's ability to survive. In the nascent age of AI, this "Enterprise Context Layer" approach seems more likely to catch on (and become table stakes, in order to keep up) than something like https://dotwork.com which looks amazing but seems to imply vendor lock-in.

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

Re: The Enterprise Context Layer

#28

Post by yumiatlead »

andychen32 wrote: post #24
yumiatlead wrote: post #22

Love the honesty, especially around process docs describing the ideal not reality. The thing I'd push on: your agents learned data retention questions are dangerous because the history existed in the data. But what about the stuff that never gets written down at all, like whose informal veto actually kills a project? Curious if you hit that wall. Someone else wrestling with the same problem: https://behaviorgraph.com…

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 proje…

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.

Post reply on HN