---
id: "concept-unified-context-infrastructure"
type: "concept"
source_timestamps: ["00:11:02", "00:12:13"]
tags: ["ai-infrastructure", "governance", "architecture"]
related: ["concept-shadow-agents", "concept-context-engineering", "concept-intent-engineering", "framework-intent-gap-layers", "entity-mcp", "entity-anthropic", "action-build-mcp-infrastructure", "prereq-mcp", "question-versioning-knowledge", "question-resolving-silo-conflicts"]
definition: "A composable, vendor-agnostic, centrally-governed data and context layer that connects AI agents to organizational knowledge through standardized protocols."
sources: ["s24-prompt-engineering-dead"]
sourceVaultSlug: "s24-prompt-engineering-dead"
originDay: 24
---
# Unified Context Infrastructure

## Definition

**Unified Context Infrastructure** is the composable, vendor-agnostic, centrally-governed layer that replaces the patchwork of [[concept-shadow-agents]]. It is **Layer 1** of the [[framework-intent-gap-layers]].

## Defining Properties

- **Composable**: agents can mix and match data sources without bespoke integration code.
- **Vendor-agnostic**: not locked to any one model provider or data platform.
- **Centrally governed**: access controls, audit trails, and lifecycle rules are unified.
- **Secure**: PII and regulated data flow only through sanctioned channels.

## Canonical Implementation

The leading proposed standard is **[[entity-mcp]]** — Model Context Protocol — introduced by [[entity-anthropic-d24]] and (per the speaker) donated to the Linux Foundation in December 2025. Familiarity with MCP is treated as a [[prereq-mcp-d24]] for the talk.

## Why This Layer Comes First

Intent Engineering ([[concept-intent-engineering]]) is impossible without a coherent substrate. You cannot encode an org-wide tradeoff hierarchy if every department's agents see different data through different pipes with different freshness guarantees.

## Open Questions

This layer raises non-trivial unsolved problems:

- [[question-versioning-knowledge]] — how do agents know what's stale?
- [[question-resolving-silo-conflicts]] — what wins when departmental contexts disagree?

## Enrichment Note

Gartner-style research (cited in the enrichment overlay) treats **data foundation readiness** as the #1 enterprise AI barrier (63% of firms unprepared). This concept aligns directly with that framing — though counter-perspectives argue infrastructure unification, *not* intent encoding, is the actual primary lever.



## Related across days
- [[concept-world-model]]
- [[concept-openbrain-architecture]]
- [[concept-vertical-context]]
- [[concept-shadow-agents]]
- [[arc-context-architecture-evolution]]