Business Capabilities
The functions, products, operating capabilities, and outcomes technology must enable.
Capability domain
Architecture
Connect enterprise capabilities, platforms, applications, information, integration, security, and AI as a coherent system.
01 — Domain thesis
Architecture turns strategic intent into a coherent system of capabilities, platforms, information, and technology.
Enterprise architecture connects business capabilities to coherent experiences, applications, platforms, data, integration, security, and AI services. It is not an inventory of technology; it is the structural connection between enterprise intent and an evolvable technology system.
02 — Transformation questions
Questions the enterprise should be able to answer.
These questions define the capability—not an intake process.
- 01Which business capabilities must the target architecture enable?
- 02What belongs in systems of record versus systems of engagement?
- 03Where should integration use APIs, events, or orchestration?
- 04How should enterprise data and knowledge become accessible to AI systems?
- 05Which capabilities should be built, bought, partnered, or consumed as platforms?
- 06Where should security, identity, policy, and observability be enforced?
- 07How can the architecture evolve without accumulating uncontrolled complexity?
- 08Which architectural decisions require formal governance?
03 — Capability model
Architecture as an enterprise capability
A reusable lens for understanding the disciplines that must operate together.
Experiences & Channels
How customers, employees, partners, and stakeholders interact with enterprise capabilities.
Applications & Products
Systems of engagement, systems of record, business applications, digital products, and specialized platforms.
Integration & Interoperability
APIs, events, middleware, orchestration, and connectivity patterns.
Data, Intelligence & AI
Operational data, analytical platforms, enterprise knowledge, AI services, models, agents, retrieval, memory, and evaluation.
Platforms & Infrastructure
Cloud, compute, networks, runtimes, developer platforms, and foundational technology services.
Security, Identity & Observability
Identity, authorization, controls, telemetry, resilience, policy enforcement, and operational visibility.
04 — Evolution & maturity
From fragmented practice to intentional enterprise capability
Maturity is visible in how decisions, evidence, controls, and operating behavior become connected.
- 01
Inventory-led
Architecture documents technology after decisions have already been made.
- 02
Standards-led
Shared principles, patterns, and governance begin reducing avoidable variation.
- 03
Capability-led
Architecture decisions trace from enterprise outcomes through capabilities, information, applications, and platforms.
- 04
Evolvable
Modular boundaries, observable systems, governed AI access, and explicit transition states support continuous change.
05 — Connections
A connected enterprise transformation capability
Governance asks who decides and controls. Architecture defines how the enterprise system fits together. AI & Automation examines how work changes when intelligence enters that system.
Strategy
Turns priorities into capability and technology choices.
Explore domainGovernance
Requires standards, decision rights, exceptions, and accountability.
Explore domainData
Defines how information is managed, accessed, integrated, and used.
Explore domainAI & Automation
Provides the platforms, knowledge, model access, orchestration, tools, and integration patterns AI systems require.
Explore domainSecurity
Embeds security architecture, identity, policy, and observability into the target state.
Explore domainExecution
Must be implementable through engineering and delivery systems.
Explore domain06 — Frameworks & artifacts
Architecture operating model
Architecture turns priorities into durable boundaries, patterns, and transition states that enable safe execution.
Inputs
- Strategic outcomes
- Current-state constraints
- Security and data requirements
Decisions
- Target-state patterns
- Build, buy, or partner
- Transition sequencing
Outputs
- Reference architectures
- Architecture decisions
- Technical roadmaps
Applied in Practice
Mapspring
Multi-tenant SaaS boundaries, public and private experiences, hosted services, and an evolvable delivery architecture.
See Mapspring in practiceFramework and Lab boundary
Frameworks define the model. Labs test implementations.
The Architecture domain defines reusable enterprise patterns. Labs test implementations such as MCP, retrieval, memory, model routing, AI gateways, orchestration, evaluation architecture, and emerging interoperability patterns.
07 — Labs & experiments
Applied exploration
Current exploration
AI Architecture Lab
Current exploration of retrieval, model access, orchestration, memory, evaluation, and emerging interoperability patterns.
Explore08 — Insights & related work
Published learning
Published
The Engineering Value Stack
A framework connecting AI-assisted engineering, architecture, delivery disciplines, and enterprise value.
ExploreExplore related work
Continue through connected domains and frameworks.
Architecture is not an inventory of technology. It is the structural connection between enterprise intent and an evolvable technology system.
Framework
Enterprise Transformation Process
A six-phase process for discovering, assessing, designing, building, operating, and evolving transformation.
ExploreLab
AI Architecture Lab
Current exploration of retrieval, model access, orchestration, memory, evaluation, and emerging interoperability patterns.
ExploreInsight
The Engineering Value Stack
A framework connecting AI-assisted engineering, architecture, delivery disciplines, and enterprise value.
Explore