The intelligence layer you actually own

Models are substitutable. What the institution knows is not.

This part describes the components of an owned intelligence layer, and the reasoning behind one firm's decision to build rather than rent it.

5. The intelligence layer: what you actually own

If the model is rented and the compute is rented, what precisely is the owned asset? Four components, and the first two are widely underestimated.

5.1 The context substrate

Every AI system is a function of what you put in front of it. The industry assumed larger context windows would solve this. They did not. Anthropic's engineering work documents “context rot,” the measurable degradation of recall as token count grows. Microsoft Research found graph-grounded retrieval outperforming vector retrieval even when the vector system was given million-token context windows. More context is not better context. Curated context is better context.

One caution, because the counter-evidence is the design principle. The llms.txt convention grew nearly ninefold to roughly 36,000 files by May 2026, and server log analysis across 137,000 domains found 97 percent received zero requests. Markdown-first knowledge creates value when it sits inside the agent's retrieval path, not when it is published and hoped for. A substrate is something your systems read by default. A document is something someone might find.

5.2 The knowledge graph, the agent layer, and telemetry

Retrieval over documents answers questions a document already answers. Most valuable enterprise questions span sources and require relationships — which is what a knowledge graph holds. Above it sits the agent layer: portable definitions, enterprise-held identity, capability limits and lifecycle management. Beneath all of it runs telemetry, so every interaction is observable, attributable and joinable to a financial outcome. Those four components are the owned asset.

6. Case in point: why Michael Baker built Titan

Michael Baker International is an 86-year-old engineering and consulting firm of roughly 6,000 people. We are not a technology vendor, and this decision was not taken because building was appealing. It was taken because the alternative did not answer the question we were being asked.

So we built Titan, an internal enterprise AI platform we own end to end. It routes across multiple frontier models so model selection is a governed decision. It keeps interaction data inside our own tenant, so accumulation accrues to the firm. It provides an enterprise-owned agent registry, so agents built by our people are our assets. And it instruments everything, so usage can be joined to financial and project outcomes. We deliberately did not build models, did not build infrastructure, and did not attempt to replace the productivity suite.

What it returned

• Adoption moved from single digits toward the mid-twenties as a share of the workforce — a leading indicator, not a result. The mechanism was the platform combined with a peer champion network of domain experts.
• Unit economics changed shape. Cost moved from a fixed function of headcount to a variable function of use.
• Agent creation became organic and substantial. Hundreds of purpose-built agents now exist, created predominantly by non-developers.
• Institutional knowledge began to accumulate as structure, by default rather than by effort. We consider this the strategic return.
• We can answer the client question. When a state agency asks where its information goes, the answer is architectural and demonstrable rather than contractual.

We do not yet have a defensible P&L attribution, and we are not going to pretend otherwise. Owning the layer is what makes the measurement possible. It does not make it instant.

What we would sequence differently

A limit we will state plainly: Titan routes across multiple frontier providers, which lowers switching cost but does not by itself reduce concentration risk, since those providers are the concentrated ones. Extending routing to open-weight models is on our roadmap and is not yet done.