Every company feeding context to AI agents faces the same question: if everyone runs on the same models, where does advantage come from? Two moats decide it. Whether rivals can copy your context, and whether the model already knows it. Plot a context asset on both, and its real worth becomes obvious.
Rare among your competitors, but a frontier model can synthesize a competent version on request. Useful today. Don't build the strategy on it.
Rare, costly to copy, and beyond what the model can synthesize. Born from a proprietary loop. This is the moat worth defending.
Everyone in the industry holds it and the model knows it cold. Necessary plumbing. Build it cheaply and spend zero strategy attention here.
The model can't reproduce it, but every serious competitor already runs it. Required to operate, not a differentiator. Build it well, move on.
Score a context asset on both axes separately, then read where it lands. Effort to create is not cost to copy. A brand brief that took three weeks to write still takes three minutes to clone the moment the file leaves the building, which is why so much "proprietary" context quietly sits in the bottom-left.
The pattern repeats by layer. Instructional and public-semantic context tends to fall toward commodity. Episodic, relational, and environmental context, the kind generated by your own operations and the physical world, is where durable advantage concentrates. If your context investment is flowing mostly into the first group, that itself is the finding.
The aim is not to fill the top-right. Most assets belong elsewhere, and that's fine. The aim is to know which one or two assets are the real moat, so you protect those and stop overspending on the rest.
The most defensible context is often tacit, the judgment living in experienced people's heads, defensible precisely because it was never written down. The moment you codify it into a clean, agent-readable brain, you convert your stickiest asset into a portable one. What couldn't walk out the door now fits in a file.
So codify with eyes open. Treat the loop that produces and refreshes context as the asset, not the document it emits. Keep that loop proprietary even when you share its output, and pair any company brain with real access governance from day one, not as an afterthought.