Phil Wainewright's latest piece on diginomica does the useful work of naming something most enterprise AI conversations skip: the decision threads buried in Slack, email, comments, and team apps are where the why of enterprise activity actually lives. Systems of record capture the what. Agents that only see the what will keep producing confident nonsense. That gap is real, and Phil has been consistent on it for over a year.
The piece quotes Garg and Gupta's argument that startups sitting "in the orchestration path" are best placed to capture this layer and displace incumbents. That's the claim worth pressure-testing. Decision threads happen inside tools the incumbents already own — Teams, Slack, Jira, Salesforce, ServiceNow. Data gravity, identity, and permissions all favor the platforms where the conversations are already happening. SAP, ServiceNow, Atlassian, Celonis, and Glean are each building some version of this graph from positions that are hard to dislodge.
For an Architect or CIO, the practical risk isn't missing a platform shift. It's funding a startup's "context graph" and discovering it's a thin layer over data you already pay to store — with new lock-in, fresh governance questions, and an entity-resolution problem nobody scoped. The decision-thread thesis is sound. The displacement thesis deserves more scrutiny than the term's momentum currently allows.
Read it for the framing. Then ask who owns the graph, where entity resolution happens, and what your context looks like the day the vendor gets acquired.