Enterprise Strategy
The semantic divide separating future-ready enterprises from the rest, and the hidden cost of building your own data access layer instead of buying.
3 posts
Enterprise AI is not gated by model capability. It is gated by the absence of a runtime layer below the copilot - the place where business meaning, governance, and execution converge into something deterministic enough for production. Without that layer, every agent is a guessing machine, every dashboard is a parallel definition, and every compliance review is a forensic exercise.
This collection takes the strategic view. Posts cover the semantic divide - why future-ready enterprises will outpace the rest by treating meaning as infrastructure, not as documentation; the case for moving from data products to semantic products; and how data leaders should think about platform investment when retrieval-only architectures no longer scale to multi-agent workflows.
You'll also find pieces on how data products are dead in their current form, what "long live semantic products" actually means in budget terms, and what a CDO's first-90-days plan looks like for standing up a semantic execution layer. The argument across them: the enterprises that compile their AI through governed meaning will move faster, audit cheaper, and keep regulators on side. The ones still wiring meaning per-agent will spend the next five years rebuilding context they should have modelled once.
The Company Brain: Why Enterprise AI Agents Need a Shared Semantic Memory
YC calls it the missing primitive. Why your wiki, your data catalog, and your RAG pipeline are not it.
Read moreThe Semantic Divide
Why future-ready enterprises will outpace the rest - and what's at stake for laggards.
Read moreThe Hidden Cost of Building Your Own Data Access Layer
Roll your own semantic + governance + dialect handling - here's the bill.
Read moreStop building context twice.
One graph. Every agent compiles through it. Joins proven, policies enforced, SQL emitted.