published
Complete Version 1.0 master document.
Integration
Connect AI participation to real work, systems and decisions with clear controls and feedback.
Dimension version v1.0
Definition
Connect AI participation to real work, systems and decisions with clear controls and feedback.
Contents
The complete document structure, including its introduction, chapters and closing sections.
—AIDIVE AI Maturıty Framework –—INTEGRATION—I - IntegrationThe Integration Dimension evaluates whether AI reaches the work. It asks whether AI participates in real decisions and real actions, with defined authority, preserved meaning and observable consequence, and whether the enterprise can continue to operate when AI participation fails.—From Workflow Integration to Agentic Operational IntegrationTraditional integration commonly connects systems so that data and tasks move along routes designed in advance. Agentic operational integration must also support systems that pursue a goal, select actions, invoke tools, delegate work and change business state while operating. This expands the definition of integration readiness from connected syste—Guidance for AssessorsThe sections that follow examine the organisation. This section examines how the assessment itself should be conducted. Anti-patterns are errors of judgement and scope on the part of the assessor: they narrow the evidence base, distort findings, or lead to recommendations that are disproportionate to the decisions at stake. Red flags are conditionsI.1I.1 Enterprise Work, Decisions and AI ParticipationIntegration begins with how work, value and decisions move, and with where AI already participates in that movement. The purpose is to make the path visible enough to locate value, friction, decision rights, AI participation and operational risk through representative end-to-end flows.I.2I.2 AI Participation, Autonomy and ControlsWhere I.1 establishes how AI participates in the operating flow, this section focuses on the authority and controls that govern that participation. At each material touchpoint, the operating conditions should make clear what is exchanged, what AI is permitted to decide or change, which conditions constrain that authority, and what operational respoI.3I.3 Context Continuity Across the FlowContext continuity is the preservation of the operational meaning required to continue work safely. It covers the identity of the case itself, its current state, the history that produced it, the rationale behind prior decisions, the constraints that still apply and the issues that remain open.I.4I.4 Operational Continuity, Resilience and FragilityContinuity means preserving a safe and acceptable level of business service when AI, or something AI depends on, is unavailable, degraded or behaving unpredictably. Requirements start from the critical business service and its tolerance for interruption, delay and reduced quality, not from component uptime.I.5I.5 Integration Estate: Systems, Tools, Identity and ObservabilityThis section examines the technical estate that AI-enabled work runs on: the systems it reads from and writes to, the tools and capabilities exposed to it, the identities under which it acts, the instrumentation that makes its behaviour visible, and the debt accumulating underneath.I.6I.6 Decision-to-Execution and Closed-Loop LearningThis section follows a material AI output through the decision it informs, the action that follows, the record that changes and the outcome that results, then asks whether that outcome comes back and changes anything.I.7I.7 Integration Governance and Accountability [INT-07]Governance establishes who may approve, change, pause, expand or retire AI participation in operational work, and whether what happened can be reconstructed afterwards.—Dimension Synthesis and Transformation RoadmapThe Integration Dimension should conclude with a transformation narrative rather than a list of isolated findings. The synthesis has five steps: judge the evidence, place the current state, decide the target, sequence the work and package the result. Section-level prompts and takeaways are inputs to this narrative rather than substitutes for it.—Source headers, footers and notes—Practices & playbooksThe practical companion documents linked to this section.—Version historyChanges to this document, separate from the overall framework release history.
Related practices
PlaybookGuidance
Introduction and source information
AIDIVE AI Maturıty Framework™ - Architecture & Rhythm - INTEGRATION PRACTICES & PLAYBOOK
Integration
AR-I01
AR-I01 · Enterprise Real-Flow Discovery
Reveal how work actually moves across people, teams and systems, including where the lived flow diverges from the documented process and where hidden work, waits, handoffs and friction shape the outcome.
Integration
AR-I02
AR-I02 · Bounded Goal and Trajectory Review
Review goal-directed AI-enabled work where the execution path is composed at run time, establishing whether the operating boundary is explicit and the resulting trajectory can be reconstructed.
Integration
AR-I03
AR-I03 · AI Presence and Participation Depth Review
Identify where AI participates in the flow, classify its operational role and establish how deeply subsequent work, decisions or actions depend on that participation.
Integration
AR-I04
AR-I04 · Decision Point and Decision-to-Action Mapping
Make critical decisions, ownership, AI influence and downstream action paths visible.
Integration
AR-I05
AR-I05 · Human-Agent-System Interaction Mapping
Define what information, intent, authority, action and feedback move across each material human-agent-system interaction, and how the interaction is expected to complete.
Integration
AR-I06
AR-I06 · Autonomy Seam and Control Point Design
Calibrate permitted AI authority and human control at each material decision or action seam, and define the action envelope, controls, escalation and safe-stop behavior required for operation.
Integration
AR-I07
AR-I07 · Untrusted Input and Action Boundary Test
Test whether content entering an AI-enabled flow can influence action beyond its instruction authority, and whether independently enforced controls keep resulting actions within the permitted boundary.
Integration
AR-I08
AR-I08 · Multi-Agent Delegation Review
Review material multi-agent delegation chains to determine whether identity, authority, task continuity and supporting evidence remain explicit and reconstructable across handoffs.
Integration
AR-I09
AR-I09 · Context Flow and Minimum Context Package
Preserve operational meaning as work moves across humans, agents, teams and systems.
Integration
AR-I10
AR-I10 · Continuity, Degraded Mode and Recovery Test
Prove that a critical AI-enabled flow can continue within defined tolerances, enter degraded operation safely and recover trusted work and state after disruption.
Integration
AR-I11
AR-I11 · System Landscape and Shadow Integration Scan
Create visibility of the AI-enabled system and tool landscape, including unmanaged connections, duplication, ownership and material shadow integration.
Integration
AR-I12
AR-I12 · Tool Contract and Machine Identity Review
Review whether material agent-accessible tools expose bounded and interpretable business capabilities, and whether actions through them remain attributable to a scoped software identity and independently enforced authority.
Integration
AR-I13
AR-I13 · Observability and Evaluation Readiness
Establish whether material AI-enabled work can be reconstructed from the business unit of work through its trajectory, actions, controls and outcome, and whether maintained evaluation evidence can detect material behavioral change.
Integration
AR-I14
AR-I14 · Integration Debt and Dependency Register
Make material integration debt and dependencies visible as owned lifecycle decisions, including their operating consequence, carrying cost and future exit or concentration exposure.
Integration
AR-I15
AR-I15 · Closed-Loop Decision-to-Execution Review
Trace a material AI contribution through an owned decision, executed action, recorded state, observed outcome, feedback and governed learning.
Integration
AR-I16
AR-I16 · Integration Governance and Accountability Setup
Establish accountability, change authority, traceability, oversight and readiness gates for material AI-enabled operations.
Integration
AR-I17
AR-I17 · Integration Maturity Calibration
Calibrate current and target Integration capability patterns using operational evidence, explicit evidence confidence and the operating conditions each capability must sustain.
Integration
AR-I18
AR-I18 · 90-Day Integration Improvement Roadmap
Convert Integration findings and current-to-target capability gaps into a sequenced, owned 90-day roadmap of usable operating improvements and evidence-producing decisions.
Integration
PlaybookGuidance
Operating Rhythms
Practices create capability; operating rhythms keep it visible and actionable over time. AR-R12–AR-R16 are Integration conversations, triage and formal decision-gate patterns designed to run within the organization’s existing delivery, release, governance and operational-review cadences. They are a reference architecture rather than a mandatory cal
Integration
AR-R12Rhythm
AR-R12 · Weekly Integration Flow Triage
Resolve blockers, handoff failures, orphan outputs, context gaps and unresolved execution issues affecting priority AI-enabled flows.
Integration
AR-R13Rhythm
AR-R13 · Biweekly Autonomy and Control Conversation
Review AI authority mode, human-control mode, control activations, overrides, permission or action-envelope changes, escalations and unresolved control conditions.
Integration
AR-R14Rhythm
AR-R14 · Release and Exposure Expansion Gate
Decide whether the proposed release or exposure transition has sufficient Integration evidence to proceed, proceed with conditions, be held, narrowed or reversed.
Integration
AR-R15Rhythm
AR-R15 · Monthly Operational Integration Health Conversation
Review conversion, latency, evaluation performance, control and exception activity, support load, incident signals and continuity tolerance across material AI-enabled flows.
Integration
AR-R16Rhythm
AR-R16 · Quarterly Scale, Debt and Resilience Conversation
Review shared dependencies, concentration, resilience evidence, estate exposure, portability, debt carrying cost and unresolved lifecycle risk before further scale or replication.
Integration
PlaybookTemplate
Minimum Consulting Templates
The following templates define the minimum reusable artifacts for applying the Integration practices consistently. They may be implemented as documents, workbook views, workflow records or delivery-platform objects as long as the required fields, evidence intent and decision logic are preserved. Related views should be combined where this makes con
Integration
PlaybookGuidance
Consultant Application Guidance
AIDIVE Integration conclusions should be grounded in evidence from real flows, representative cases, exceptions, operating records and observed outcomes. A polished design or isolated pilot is useful evidence, but it does not demonstrate enterprise capability until the relevant behavior is implemented consistently across the reviewed scope.
Integration
PlaybookGuidance
Source headers, footers and notes
Integration
Dimension version history
This history belongs to Integration. Overall framework releases are recorded separately in Framework release history.