Knowledge plane / Phase 2
Data Integration & Provenance
Where does enterprise truth come from?
Governed access to source systems with lineage and entitlements attached — the data plane behind retrieval, deliberately separate from the tool plane that takes actions.
Use this harness in my journey →- Connectors and data servers exposing systems of record to agents
- Data contracts: schema, freshness and quality guarantees per source
- Lineage from source through transformation to the answer
- Entitlements: row and column security carried through to the agent
- Federated query across warehouses, lakes and operational stores
- Classification of sensitive fields before anything is indexed
Accountable owner
Data Engineering, with Data Governance and Privacy
- Head of Data Engineering — accountable owner
- Data engineer — connectors, contracts, pipelines
- Data steward — source ownership and quality
- Privacy officer — classification, minimisation, retention
- Security engineer — entitlement propagation
Ownership and phase are architectural recommendations, not assessed results.
binds physical data to agreed definitions
supplies the corpus retrieval draws on
published as MCP data servers
entitlement enforcement and PII classification
lineage feeds audit and incident replay
training and feature data
Connect three sources properly — contract, lineage, entitlements — before connecting thirty carelessly. MCP data servers shorten integration work substantially, but the governance is the slow part, not the plumbing.
Signals to watch
- Freshness against contract per source
- Contract test pass rate
- Entitlement violations detected (target zero)
- Lineage coverage as a share of answers
- Time to honour a deletion request across indexes
Connectors and quality rules can evolve. Data access, freshness, lineage and consent remain enforced at the boundary.
How governed change crosses the architecture ↗Failure modes
- The agent inherits broader entitlements than the human it acts for
- PII copied into vector indexes where deletion obligations cannot be met
- Stale or silently broken sources answering confidently
- No lineage, so an incorrect answer cannot be traced to its source
Existing tool and standards snapshot · approximately mid-2026. Examples, not required dependencies; verify current versions before adoption.
Open source
- Airbyte
- dbt
- Trino or Starburst
- Apache Iceberg
- OpenLineage and Marquez
- DataHub or OpenMetadata
- Great Expectations
- Debezium
- Apache Polaris
- Apache Ranger or OPA for row and column policy
Managed
- Managed ELT and warehouse platforms
- Catalog and lineage suites
- Enterprise MCP data servers from vendors
Standards
- OpenLineage for lineage events
- Open table formats (Iceberg)
- MCP for exposing data to agents
- Data contract specifications
Data access and tool execution are different trust boundaries. Reading a governed table and calling an API that moves money should never share one permission model — that separation is why this harness exists apart from Tool, Skill & Sandbox.
