Agent Control-Plane System-of-Record

Type: framework / assurance decision frame First seen: 2026-09-18 Last updated: 2026-09-18

Definition

An agent control plane is a cross-vendor layer that discovers, registers, identifies, policies, monitors and can suspend the AI agents running across an enterprise’s platforms. The system-of-record question is the assurance question that follows once more than one such layer is present in an estate: which control plane’s inventory and logs are the authoritative, retained, exportable record for regulatory purposes — and, at the boundary where governed context flows to an agent (typically via MCP), what policy, certification status and logging actually travel with the call [S-2026-09-18-weekly-briefing].

Origin

The frame emerged from the AI-governance vendor scan across mid-2026 and crystallised in the week to 18 September 2026, when at least six vendors (Salesforce, IBM, WSO2, Dataiku, Broadcom, Archer) shipped or previewed a cross-vendor agent register in a single week, alongside Alation’s cross-platform agent lineage — the “fifth-plus vendor class” observation from the 11 September synthesis becoming a market-wide pattern [S-2026-09-18-weekly-briefing][S-2026-09-11-weekly-ai-governance-vendor-synthesis]. Each vendor positions its layer as the single inventory the EU AI Act Art. 12 record-keeping, ISO/IEC 42001 asset inventory and SS1/23 model-inventory expectations point at, which is precisely what makes “which one is the system of record” a decision a firm must take rather than inherit [S-2026-09-18-weekly-briefing].

Corroborated 2026-09-18 by the AI-governance-scoped weekly synthesis: six of that week’s 15 AI-governance vendor captures (Salesforce, IBM, Dataiku, WSO2, Broadcom, Archer/Evolv Foundation) were this control-plane pattern, confirming it as the dominant theme of the window rather than a one-off cluster [S-2026-09-18-weekly-ai-governance-vendor-synthesis].

How it connects to other concepts

• relates-to → AI Governance Platforms — the market category from which control-plane products are drawn; this concept is the assurance question that category now forces [S-2026-09-18-weekly-briefing].
• relates-to → Agentic Data Access Governance — the MCP call boundary, where governed metadata reaches agents, is the seam the system-of-record question turns on [S-2026-09-18-weekly-briefing].
• relates-to → Model Risk Management and Agentic AI — a control plane that is itself an AI system (e.g. GRC agents doing control testing) is in-scope of the same inventory/validation/oversight expectations [S-2026-09-18-weekly-briefing].
• relevant-to → Service Line — Independent Governance Assurance — the frame is the basis of a reusable assurance-review artefact [S-2026-09-18-weekly-briefing].

Practical applications

A one-page “enforcement-locus map” for an agentic-AI assurance review, asking three testable questions of an estate that has one or more control planes [S-2026-09-18-weekly-briefing]:

1. Which layer holds the retained, exportable record that satisfies EU AI Act Art. 12 logging and SS1/23-grade traceability — identity/IAM, gateway-middleware, infrastructure, the GRC “harness”, or the network layer — and is that record authoritative when layers disagree?
2. Who approves versioned changes to guardrail policy, agent scope and residency, and is that change control evidenced?
3. What travels with the MCP call — does policy, certification status and logging accompany the metadata reaching the agent, or does it stay inside the source platform?

Tensions / variants

• The competing loci (identity, gateway, infrastructure, GRC, network) are each marketed as the control plane, so an estate can end up with several overlapping “systems of record” and no authoritative one — the unresolved core of the frame [S-2026-09-18-weekly-briefing].
• All current vendor “first”/“trusted”/“compliance-grade” and regulatory-alignment claims are vendor-asserted, with no verified EU/UK regulated-FS reference customer named as of 18 September 2026; the frame is a set of questions to ask, not an endorsement of any layer [S-2026-09-18-weekly-briefing].

Sources

• S-2026-09-18-weekly-briefing — Weekly Briefing, 18 September 2026 (own synthesis; the week’s six-plus control-plane releases and the system-of-record framing).
• S-2026-09-18-weekly-ai-governance-vendor-synthesis — AI-Governance Vendor Synthesis, 18 September 2026 (own synthesis; corroborates the six-vendor control-plane cluster from the AI-governance-scoped capture set specifically).
• S-2026-09-11-weekly-ai-governance-vendor-synthesis — the earlier “fifth-plus vendor class” and enforcement-locus-map observation.