Architecture intent
Define the business purpose, accountable owner, data and system boundaries, risk, dependencies, and expected outcome.
Agentic Enterprise Architecture
Scaled Agents connects enterprise architecture intent to customer-owned identity, bounded authority, Human Review, runtime decisions, evidence, and lifecycle control.
The Architecture Decision
Enterprise architecture already connects strategy, capabilities, applications, data, security, and technology. Agentic EA adds the control path for AI workers that can retrieve data, call tools, trigger workflows, or delegate work.
Define the business purpose, accountable owner, data and system boundaries, risk, dependencies, and expected outcome.
Decide the exact action an AI worker may take, under which policy and review conditions, for how long, and with what evidence.
Three Control Questions
Orchestration, models, data platforms, API gateways, service meshes, and observability remain execution inputs. They do not replace the customer-owned governance chain.
The Agent Registry and Passport connect the AI worker to a human owner, purpose, risk tier, lifecycle state, and approved scope.
Purpose Binding and the Tool/API/Connector Registry define eligible actions, resources, data classes, destinations, and prohibited uses.
A Toll Gate and Human Review can inform a short-lived Runtime Permit. The Action Broker is the controlled mediation path for the exact action when implemented and operated in the customer’s configured environment; evidence records preserve the result.
An active Passport establishes a current governance record. It does not authorize every action. Runtime authority remains action-specific, time-bounded, policy-bound, and revocable.
Reference Architecture
The architecture keeps customer strategy and enterprise standards connected to the authority, mediation, evidence, and lifecycle controls applied to AI-worker actions.
Shared Responsibility
The licensed platform provides structures for identity, authority, review, runtime decisions, evidence, and lifecycle management. Customer owners configure and operate those controls for their environment.
Provides the customer-managed platform, license, documentation, updates, and optional consultative services within the agreed scope.
Owns hosting, configuration, integrations, data, identities, policies, approvals, monitoring, custom changes, operations, and all decisions about deployment and use.
Accountable customer owners retain deployment, activation, legal, privacy, security, compliance, audit, risk acceptance, and production-operating decisions. Public architecture content does not make those decisions or grant AI-worker authority.
Next Step
Start with purpose, ownership, intended outcome, data, systems, autonomy, and risk—then connect the blueprint to the customer-owned control path.