IBM is the enterprise-estate vendor. It owns silicon and systems for running AI next to the data (z17, Power11, Spyre), storage plus a catalog that answers what the data is (watsonx.data intelligence with integrated lineage), streaming and integration (Confluent, DataStage), GPU scheduling (Spectrum LSF, Turbonomic), a model platform (watsonx.ai, Granite), a complete agent-governance plane (watsonx Orchestrate's control plane joined to IBM Agent Identity), and a first-party application estate (Orchestrate domain agents, Maximo, Cognos, Planning Analytics). It is strong at 0C, 1A, 1C, 2A, 2C and Layer 3, moderate at 0A, 1B and 2B, and a gap at 0B. Red Hat is its own row: OpenShift is the substrate IBM's on-premises software runs on (on-premises watsonx requires it), so the two rows compose in the common IBM deployment. IBM Cloud is outside this row.
The capture is coupled and visible where the value accumulates. The catalog structure, lineage and governance rules, Confluent's platform surfaces, DataStage flows, Orchestrate agent definitions and the agent inventory behind Agent Identity, and the Maximo and Cognos models are IBM's, and Ceded; Granite's open weights, Milvus, and Ceph are the open seams. It is the inverse of the Red Hat row: portability sits on the Red Hat side, and captured value accumulates on the IBM side. A buyer of both gets a portable substrate under a captive estate, and should price the estate, not the substrate.
The buyer's trade: governed data, AI beside the systems of record, an agent plane with cross-platform reach, and applications that run the business, in exchange for capture in IBM's data, agent, and application layers, and an identity join between Orchestrate and Agent Identity that the architect wires.
Layer-by-layer status: Layer 0A (Owned AI Silicon Beside the Data: z17, LinuxONE 5, Power11 and Spyre), Layer 0B (No Fabric on IBM's Paper), Layer 0C (Storage Scale and FlashSystem, With Ceph and Fusion Beside Them), Layer 1A (watsonx.data intelligence, a Catalog With Classification and Lineage), Layer 1B (Milvus Inside watsonx.data + Unstructured Data Pipelines for RAG), Layer 1C (Confluent + DataStage + Lakehouse Federation), Layer 2A (IBM-Owned GPU Scheduling: Spectrum LSF + Turbonomic), Layer 2B (watsonx.ai Model Platform + Granite, on the Red Hat Engine), Layer 2C (Complete Intelligence-2C Plane Across Two Products; Identity Join Architect-Wired), Layer 3 (+1) (IBM Portfolio: watsonx Agents, Maximo, Cognos and Planning Analytics; Red Hat the Infrastructure Focus).
Assessment framework: 4+1 Layer AI Infrastructure Model. Scoring model: Decision Authority Placement Model (DAPM) — Retained, Delegated, or Ceded. Published by The CTO Advisor LLC (DBA The Advisor Bench). Author: Keith Townsend. Date assessed: October 27, 2026. Version: v2.25 - 4+1 v3: Layer 0 Sub-Layers.
IBM is the enterprise-estate vendor. It owns silicon and systems for running AI next to the data (z17, Power11, Spyre), storage plus a catalog that answers what the data is (watsonx.data intelligence with integrated lineage), streaming and integration (Confluent, DataStage), GPU scheduling (Spectrum LSF, Turbonomic), a model platform (watsonx.ai, Granite), a complete agent-governance plane (watsonx Orchestrate's control plane joined to IBM Agent Identity), and a first-party application estate (Orchestrate domain agents, Maximo, Cognos, Planning Analytics). It is strong at 0C, 1A, 1C, 2A, 2C and Layer 3, moderate at 0A, 1B and 2B, and a gap at 0B. Red Hat is its own row: OpenShift is the substrate IBM's on-premises software runs on (on-premises watsonx requires it), so the two rows compose in the common IBM deployment. IBM Cloud is outside this row.
The capture is coupled and visible where the value accumulates. The catalog structure, lineage and governance rules, Confluent's platform surfaces, DataStage flows, Orchestrate agent definitions and the agent inventory behind Agent Identity, and the Maximo and Cognos models are IBM's, and Ceded; Granite's open weights, Milvus, and Ceph are the open seams. It is the inverse of the Red Hat row: portability sits on the Red Hat side, and captured value accumulates on the IBM side. A buyer of both gets a portable substrate under a captive estate, and should price the estate, not the substrate.
The buyer's trade: governed data, AI beside the systems of record, an agent plane with cross-platform reach, and applications that run the business, in exchange for capture in IBM's data, agent, and application layers, and an identity join between Orchestrate and Agent Identity that the architect wires.
CPUs, accelerators, servers, integrated systems, OS and hypervisor, physical plant
Mainframe-class systems with on-chip AI inference and Spyre accelerator clusters, running AI beside transactional records. Proprietary integrated system: Ceded.
Enterprise servers with on-chip inference acceleration and Spyre attach for generative and agentic inference. Proprietary integrated system: Ceded.
Storage Fusion HCI, the integrated system that hosts watsonx on premises. Integrated systems are primary at 0A; the row names it only inside the Fusion chip.
Assessment pending
IBM sells owned silicon and systems for running AI next to the data. The z17 mainframe and LinuxONE 5 carry Telum II on-chip AI acceleration and take up to 48 Spyre cards (generally available October 28, 2025). Power11 carries on-chip matrix-math acceleration and takes up to 16 Spyre cards (generally available December 2025). Spyre is IBM's own 5nm, 32-core inference accelerator, and Storage Fusion HCI is the integrated system that hosts watsonx on premises. The silicon carries IBM's judgment, not NVIDIA's. The buyer gets inference inside the systems that already hold core banking, insurance and enterprise resource planning (ERP) records. The architect's concern is that these are proprietary integrated systems with no exit to another vendor's hardware. The accelerators are inference-class, not training-class. Calibration: Intel reads moderate on CPUs with a thin accelerator line; NVIDIA and AMD strong on frontier accelerators. IBM Cloud's rented GPUs are read on the IBM Cloud row.
Delegated where the grade rests. PR/SM on z17 and LinuxONE 5, and PowerVM on Power11, make the dispatch calls, and the enterprise can pin: PR/SM dedicates central processors to one logical partition, and PowerVM runs dedicated-processor partitions outside the shared pool, so vendor decides, visible, overridable, Delegated, the VMware and Nutanix reading. Portability: z17, Power11 and Fusion HCI are proprietary integrated systems whose firmware and partitioning opinions don't lift, Ceded.
Confidence flag: Fusion HCI is a facet of Storage Fusion here; if Fusion HCI is the thing sold, the integrated-system rule makes it primary at 0A. Public evidence that moves the cell: training-class accelerators on IBM's on-premises paper. Not a chip (the hardware-management placement rule, October 16, 2026): PR/SM, PowerVM partitioning and z/OS Workload Manager read with z17 and Power11 as the authority carrier. Source conflict (October 23, 2026): IBM's z17 product page footnote still says "The IBM Spyre Accelerator is current in technology preview." The cell scores Spyre on its user's guide (GC28-7071-00), which documents it for z17 and LinuxONE 5, as ruled October 22, 2026. Named, not scored (public preview, October 27, 2026, no GA date): IBM Z Atlas, which discovers relationships across z/OS infrastructure, software, middleware, and applications and uses that topology to drive patching and change. It's operations tooling over the Z estate, not compute.
Interconnects, switching and routing, network virtualization
Assessment pending
IBM sells no network fabric on premises, so no routing or congestion decision is made on its paper. Calibration: AMD and Intel read moderate on NICs without switching; NVIDIA strong on the whole fabric.
Absent: nothing offered and nothing inherited at 0B.
Public evidence that moves the cell: a GPU fabric on IBM's on-premises paper.
Arrays, storage servers and software, front-end protocols: where the data sits
Owned all-flash block arrays with agentic operations: the 9600 lists "64 GB/s FC or NVMe/FC" and "100/40 GB iSCSI or NVMe/TCP" host ports, and the configuration limits cover iSCSI, Fibre Channel, NVMe over Fibre Channel and NVMe over TCP hosts across the 5600, 7600 and 9600. Proprietary arrays: Ceded.
Ceph: distributed S3-compatible object storage for watsonx.data lakehouse. Open-source substrate the enterprise can self-operate; the litmus's own Retained example. Competent but not AI-optimized at competitor level.
Proprietary storage services for OpenShift applications with data caching and acceleration; Storage Fusion HCI hosts watsonx on-premises. Fusion's data-services opinions are IBM-captive, split from the open-source Ceph substrate it sits beside, per the one-chip-one-substrate convention.
IBM's parallel file system sold as software only, installed with the Storage Scale installation toolkit on x86_64 Linux servers (RHEL, SLES, Ubuntu). Policy-driven placement and migration across internal and external storage pools, with per-file replication.
Optional host connectivity on the FlashSystem arrays: 32 and 64 Gb Fibre Channel with NVMe/FC, and 10 to 100 GbE with iSCSI and NVMe/TCP. Policy-based high availability covers NVMe-oF hosts from release 9.1.1.
The native client cluster nodes mount the Storage Scale file system through. IBM's client over IBM's data path; opinions built on it don't lift to another file system. Ceded.
Protocol nodes that serve NFS, SMB and S3 (only NFS and SMB on a Storage Scale System appliance). Multi-vendor standard protocols, so the hosts and applications consuming them swap to another provider behind the same protocols: Delegated, the WEKA, Everpure and NetApp front-end reading.
IBM's parallel-file appliance, which "utilizes a high-speed, proprietary protocol to provide access to data," and is "configured with optional protocol nodes to support NFS, SMB, HDFS, and low-latency S3 object access." The appliance and its management are IBM's: Ceded; the Storage Scale software reads on its own chip.
Assessment pending
IBM's storage substrate covers parallel file, block and object. Storage Scale is IBM's parallel file system, sold as software on x86 Linux servers or as the Storage Scale System 6000 appliance. It does policy-driven placement and migration across pools, with per-file replication. FlashSystem 5600, 7600 and 9600 are all-flash arrays with FlashSystem.ai operations agents (generally available March 6, 2026). Storage Ceph serves S3 object for the watsonx.data lakehouse, and Storage Fusion gives OpenShift applications storage services with caching and acceleration. The buyer gets AI-throughput file storage under its own catalog. The architect's concern is the storage OS. Storage Scale has no second implementation, so its pool, policy and replication opinions don't lift, and the native client AI nodes mount through is IBM's alone. Ceph is the open seam, competent but not AI-optimized. Calibration: VAST, WEKA and DDN read strong on storage alone; Red Hat moderate on Ceph through ODF.
Delegated where the grade rests. Storage Scale places and protects the bytes, and the enterprise can move a single file to a named pool with mmchattr -P and set its replica counts with -r and -m, a per-file handle the engine must honor: vendor decides, visible, overridable, Delegated. Portability: Storage Scale, FlashSystem, Fusion and the native client read Ceded; the FlashSystem block protocols are standards, Delegated; Ceph is open source the enterprise operates, Retained.
Confidence flag: the FlashSystem and Storage Scale System 6000 chip holds two products whose placement engines and portability may differ.
The data itself, organized and governed: the Governance Catalog that Layer 2C queries
Open data lakehouse with Presto and Spark engines, Iceberg table format. Shared metadata layer across clouds and on-premises. GPU-accelerated Presto (private preview). Context layer for AI-queryable metadata (private preview). watsonx.data intelligence provides data lineage, classification, quality, and Master Data Management. Proprietary IBM platform: opinions captive, no open exit. The Apache Iceberg surface in front of it is its own chip.
IBM's data catalog (formerly IBM Knowledge Catalog) with automated classification, sensitive-data discovery and anonymization, data quality, and Data Lineage (formerly IBM Manta, acquired October 2023) integrated for end-to-end mapping of data flows. The catalog a reasoning plane queries for what the data is. IBM's catalog structure and governance rules don't lift: Ceded.
GA May 2026. Software platform enforcing data sovereignty across four pillars: operational, data, technology, AI sovereignty. Embeds policy at infrastructure runtime. Built on Red Hat OpenShift. Mistral AI as first certified model partner. Ensures data residency, model execution, and inference all operate within sovereign boundary. Proprietary IBM platform: opinions captive, no open exit.
Apache Iceberg has independent implementations: code and definitions written to it move to another compatible implementation within the features both support, the data moves by export, replication or rewrite, and the provider's control-plane configuration and operational state don't lift. Delegated. The service behind it is its own chip, Ceded.
Private preview. Proof-of-concept with Nestlé showed 83% cost savings. GPU acceleration for analytical queries on the lakehouse.
Strong, on the catalog criterion: IBM's catalog answers what the data is. watsonx.data intelligence carries classification, sensitive-data discovery and anonymization, data quality, and Data Lineage (formerly Manta) for end-to-end mapping of data flows. Above it, watsonx.governance maps AI assets through policies, risks and regulations. It's the only assessed governance surface built to reach past its vendor, monitoring models on OpenAI, AWS and Meta. Sovereign Core enforces data residency, and the watsonx.data lakehouse (Presto and Spark on Iceberg) shares metadata across clouds and on premises. The architect's concern is that the value accumulates in IBM's catalog structure, lineage graph and governance rules, which don't lift. The Iceberg tables are the open seam. Storage Ceph and Storage Fusion hold the bytes, 0C functions. The grade rested on the catalog, so it doesn't move. Calibration: AWS reads strong on Glue and Lake Formation; Dell and WEKA moderate on metadata-only indexes.
Profiling assigns data classes by matching values, and business terms are suggested or auto-assigned above a threshold, so watsonx.data intelligence decides. A data steward can change or remove a column’s class and reject a term, and those choices persist: vendor decides, visible, overridable, Delegated. Portability: the catalog, lineage graph, watsonx.governance and Sovereign Core are IBM IP, Ceded; the Iceberg tables are open, Delegated.
Named, not scored (private preview): the watsonx.data Context layer, which adds contextual metadata into the lakehouse, and GPU-accelerated Presto on NVIDIA. Confluent's streaming is scored at 1C. Open question: whether IBM's Governance Graph can serve as the queryable governance surface a Layer 2C plane needs. watsonx.governance governs AI assets (models, policies, risks and regulations), not the data, so it isn't scored at 1A.
Low-latency retrieval for RAG — vector/hybrid search, context windows
Managed Milvus inside watsonx.data, combining vector similarity with relational-style filtering. Open-source Milvus the enterprise runs on premises: Retained on the possess-and-operate line.
Pipelines that turn documents into RAG-ready chunks and embeddings and populate vector stores; included in the watsonx.data integration, intelligence, and Premium licenses. IBM's flows and operators: Ceded.
Assessment pending
RAG preparation and retrieval inside the governed lakehouse. watsonx.data's Unstructured Data Integration ingests documents, PDFs, and slides, extracts text, removes PII, deduplicates, and runs chunking and embedding operators that populate vector stores; watsonx.data's managed Milvus service (Milvus 2.5) serves hybrid search that combines vector similarity with scalar filters beside the structured data in the lakehouse. The architect's concern: the ingestion pipelines are IBM's flows, the end-to-end retrieval product (OpenRAG on watsonx.data) isn't confirmed generally available, and there is no documented reranking or relevance-tuning stage. Moderate. Calibration: above the Red Hat row's assembled kit, because IBM's pieces are integrated from ingestion to index; below Elastic, Azure AI Search, and Vertex, which ship a generally available relevance stage and a managed retrieval service, the best shipping implementations on the instrument; alongside Cloudera and Redis on a real engine and pipeline short of the frontier deliverable.
Split. Milvus is open source the enterprise runs inside on-premises watsonx.data, and its collections and indexes lift to any Milvus deployment: Retained. The Unstructured Data Integration flows and operators are IBM's and rebuild on exit: Ceded. Milvus ranks inside queries the enterprise composes, with per-request filters: vendor decides, visible, overridable, Delegated, the Elastic reading.
Watch-list, notes only: OpenRAG on watsonx.data (announced; general availability not confirmed), which would deepen the cell. watsonx.data intelligence governs unstructured data and is read at 1A. Red Hat's vector-store integration and Llama Stack RAG are scored on the Red Hat row.
Move/transform data — ETL/ELT, lineage, cost-aware movement, KV cache tiering
IBM sells Confluent Platform to "Run and manage our complete data streaming platform on premises." The Kafka core the enterprise runs lifts to any Kafka: Retained, the self-run Kafka reading on the Confluent row; Confluent Server's commercial features read Ceded there.
IBM-defensible IP. Enterprise data integration engine with decades of maturity. Graphical and code-first pipeline building. Automated data cleansing, tokenization, formatting for LLM consumption. Comprehensive lineage tracking: trace which raw document fed into a specific fine-tuning or RAG dataset. Data sanitization (PII, hate speech, copyrighted content) reduces Layer 2C compliance burden. Proprietary IBM platform: opinions captive, no open exit.
IBM-defensible IP. Zero-copy query federation to external data platforms: Confluent Tableflow, Databricks Unity Catalog, Snowflake Open Catalog, Salesforce Data Cloud. Presto and Spark engines query data where it resides without copying. The federation logic is IBM-specific integration. Proprietary IBM platform: opinions captive, no open exit.
Confluent Cloud sold by IBM: managed Kafka-protocol streaming the enterprise can move to another Kafka. The Kafka protocol surface is its own chip. The service behind it, its operations, management and configuration, is Confluent's and doesn't lift: Ceded.
"Turn data streams into open tables for your data lake": Tableflow materializes Kafka topics as Iceberg or Delta tables, integrated with watsonx.data. The schematization and table maintenance are Confluent's: Ceded, the Tableflow reading on the Confluent row.
"fully-managed Apache Flink®, enabling low-latency analytics," the Confluent Cloud for Apache Flink service sold by IBM. The Flink SQL surface is its own chip. The service behind it, its operations, management and configuration, is Confluent's and doesn't lift: Ceded.
The Kafka protocol has independent implementations: code and definitions written to it move to another compatible implementation within the features both support, the data moves by export, replication or rewrite, and the provider's control-plane configuration and operational state don't lift. Delegated. The service behind it is its own chip, Ceded.
Flink SQL has independent implementations: code and definitions written to it move to another compatible implementation within the features both support, the data moves by export, replication or rewrite, and the provider's control-plane configuration and operational state don't lift. Delegated. The service behind it is its own chip, Ceded.
GPU-accelerated Spark on watsonx.data for pipeline processing. Same RAPIDS integration available across vendor platforms.
Strong, on three IBM-owned surfaces. Confluent (acquired for $11 billion) makes real-time streaming infrastructure, with Tableflow exposing live Kafka streams as Iceberg tables in watsonx.data without ETL. DataStage (watsonx Edition) is the enterprise integration engine: graphical and code-first pipelines, automated cleansing and tokenization for LLM consumption, PII and harmful-content sanitization before training, and lineage that traces which raw document fed which fine-tuning or RAG dataset. watsonx.data federation queries Confluent Tableflow, Databricks Unity Catalog, Snowflake Open Catalog, and Salesforce Data Cloud where the data resides. The architect's concern: the defensible value is captive (Confluent's platform surfaces, DataStage flows, the federation logic), and the stack is enterprise-weight; teams used to Python scripts and lightweight RAG tooling can find it heavy. Calibration: the strong 1C cohort (Snowflake Openflow, Databricks Lakeflow, Qlik CDC plus Talend, VAST DataEngine, Confluent) covers batch, streaming, CDC, transformation, and lineage generally, and IBM covers all of it on owned surfaces. Composition: in the common IBM deployment these pipelines run on OpenShift as containerized workloads, so data moves to compute, unlike VAST's DataEngine; the open ML pipeline stack (Kubeflow, Ray, MLflow) and Red Hat's Kafka, Debezium, and Camel are scored on the Red Hat row. Decision authority: both engines that carry the grade execute what the enterprise wrote or configured. Confluent reads code / Retained on its own row, and DataStage runs the flows the enterprise designs (runtime column propagation is opt-in, a setting the enterprise chooses). Code decides, visible, overridable, Retained, the judgment test (October 4, 2026).
Low upstream, and the capture is IBM's. Confluent's platform surfaces, DataStage, and the watsonx.data federation logic are IBM IP: Ceded. The open Kafka core reads Retained, as on the Confluent row. NVIDIA's role is limited to RAPIDS acceleration for Spark. The pipelines run on IBM's engines, which execute the flows the enterprise designs: code decides, visible, overridable, Retained, the judgment test (October 4, 2026). Compare VAST, which owns everything at this layer with one authority, and Dell, with four authority boundaries.
The Confluent acquisition creates a unique data velocity advantage. Dell, HPE, and VAST focus on data at rest (storage) and data in batch motion (pipelines). IBM now owns data in continuous motion (streaming). For agentic AI where agents need to reason over current events, current transactions, current sensor data, not yesterday's batch export. This is an architectural differentiator that no other infrastructure vendor possesses. Whether IBM can integrate Confluent deeply enough with watsonx.data to deliver on the 'zero-copy' promise is the execution question. The technology exists; the integration maturity is early. DataStage's data sanitization capabilities (removing PII, hate speech, copyrighted content prior to model training) are a crucial data-plane capability that directly reduces the compliance burden on Layer 2C downstream. This is the pipeline-to-governance connection that the 4+1 model identifies as critical: clean data in the pipeline means fewer governance exceptions at the reasoning plane.
GPU scheduling, quotas, RBAC, fair-share scheduling, utilization optimization
Workload scheduling for HPC and AI training with GPU-aware placement, fair share weighted by GPU run time, and resource accounting. Proprietary scheduler: Ceded.
Automated GPU resource actions for generative AI inference workloads. Proprietary decision engine and policies: Ceded.
Generally available as SaaS or on premises (October 27, 2026). Connects signals across applications, infrastructure, networks, and security into one operational context, and uses AI to help teams weigh tradeoffs and coordinate action, with policies setting which actions run automatically and which need approval. A day-two operations tool read at 2A with OpsRamp's reading on the HPE row; the grade rests on Spectrum LSF and Turbonomic. IBM's platform and policies: Ceded.
Spectrum LSF and Turbonomic schedule and right-size NVIDIA GPUs (with DCGM integration); the scheduling judgment is IBM's, the silicon NVIDIA's.
IBM sells the 2A purpose line almost word for word. Spectrum LSF (10.1.0.16, July 2026) schedules GPUs on some of the world's largest AI supercomputers, with GPU-runtime fair share and GPU resource accounting; Turbonomic's GPU optimization discovers LLM inference workloads on Kubernetes and OpenShift and scales them to use the available GPUs, as automated actions. The architect's concern: both are proprietary control planes whose queue, fair-share, and optimization policies don't port. In the common deployment the Kubernetes layer underneath is the Red Hat row's (OpenShift, OpenShift AI Kueue, Advanced Cluster Management); IBM's schedulers sit beside it (LSF, for batch training) or above it (Turbonomic), not in place of it. Strong. Calibration: CoreWeave (Kubernetes, Slurm on Kubernetes, Mission Control) and Nebius (Kubernetes plus Slurm) read strong; LSF is a proprietary Slurm-class GPU scheduler at frontier scale, and Turbonomic adds cross-platform automation. HPE reads strong on GreenLake and OpsRamp. IBM Cloud's managed Kubernetes and OpenShift are outside this row.
Low upstream, Ceded to IBM. LSF and Turbonomic are IBM IP whose policies don't lift: Ceded, the proprietary-scheduler reading (open-source Slurm or Run:ai, run by the enterprise, reads Retained). LSF honors per-job pins (host selection and resource requirements the engine must satisfy), and Turbonomic's actions can run in recommend or manual mode, a documented gate before the effect: vendor decides, visible, overridable, Delegated under the override rule.
IBM Concert is scored as a day-two operations chip under the hardware-management placement rule (incident management and agentic remediation read at 2A), the reading HPE's OpsRamp takes. The next-generation platform shown at Think 2026 became generally available as SaaS or on premises on October 27, 2026, which retired its watch-list entry. The grade rests on Spectrum LSF and Turbonomic and doesn't move. OpenShift, OpenShift AI, and Ansible are the Red Hat row's 2A.
Model serving, agent execution, inference APIs, distributed inference
IBM's model platform for on-premises inference, model deployment, tuning, and prompt tooling. Deployment spaces, prompt templates, and tuned assets are IBM-specific and rebuild on exit: Ceded.
IBM-defensible legal wrapper on open-source models. Granite 4.1 (3B, 8B, 30B dense models, Apache 2.0). ISO 42001 certified. Cryptographic model signing. Uncapped IP indemnity on watsonx.ai. Optimized for agentic workflows: tool calling, instruction following, function calling. Granite Guardian for safety guardrails. Models run anywhere (Hugging Face, Ollama, Dell Enterprise Hub, NVIDIA NIM, Red Hat AI). Open weights the enterprise runs anywhere: Retained; the IP indemnity is IBM's, the model isn't captive.
Deploying custom foundation models in watsonx.ai software requires A100 or H100 80GB GPUs; Granite on Spyre (Z and Power) is the non-NVIDIA path.
A governed model platform on the enterprise's own hardware. watsonx.ai software (Cloud Pak for Data 5.x) serves IBM-curated and third-party models, deploys the enterprise's own custom foundation models (supported since Cloud Pak for Data 4.8.4), supports tuning and prompt tooling, and carries Granite with IBM's uncapped IP indemnity. The architect's concern: the serving engine underneath belongs to the Red Hat row. watsonx.ai runs on OpenShift and Red Hat AI in the common deployment, so IBM contributes the model platform rather than the inference engine. Custom model deployment is tied to NVIDIA A100 and H100 GPUs, and deployments, prompt templates, and tuned assets live in watsonx.ai's own surface. Moderate. Calibration: the Red Hat row reads strong on the engine itself (vLLM, llm-d, Models-as-a-Service); VMware and Nutanix read moderate on platform-native serving over someone else's engine, and IBM is that shape. The agent runtime in watsonx Orchestrate is read at 2C.
Split. watsonx.ai's deployment spaces, prompt templates, and tuned assets are IBM-specific: Ceded. Granite is open weights the enterprise runs anywhere: Retained. The enterprise's own tool code is Retained. The model decides which tool to call, and the enterprise's own tool code gates the effect: model decides, visible, overridable, Delegated, the NVIDIA reading.
Inference flag: tool calling through watsonx.ai's on-premises chat API (documented on watsonx.ai SaaS); if it isn't available on premises, the customer-tools component moves here. Watch-list, notes only: the watsonx.ai model gateway on premises (SaaS-confirmed). Red Hat AI Inference, llm-d, MLflow, and InstructLab are the Red Hat row's 2B. IBM Cloud is outside this row. To notes under the GA evidence table (October 24, 2026): Customer-Created and Managed Tools (Function Calling / Client-Side) (tool calling is documented for watsonx.ai SaaS, but no owner page shows it in the on-premises Software Hub chat API). Named without a stated status (IBM post, October 27, 2026): the watsonx Orchestrate Premium Runtime, a dedicated hosting, isolation, and metering layer for agents that run dynamic tool code or call external MCP servers. The October 27 release doesn't list it under any availability heading; it's a 2B agent-execution candidate once IBM documents it.
Policy-driven placement and resource coordination — the Autonomy Layer
Generally available on AWS and IBM Cloud (June 2026). A centralized layer to observe, govern, and orchestrate AI agents regardless of where they were built or run: the AI Gateway (generally available August 31, 2026) applies policies at the gateway level to every connected agent; agent discovery and registration from Amazon Bedrock (generally available August 31, 2026) feeds a shared agent catalog; multi-agent orchestration spans frameworks; the AgentOps Agent and agent evaluation (generally available August 31, 2026), extended to models and MCP servers on October 27, 2026, cover observability. Discovery from Microsoft Foundry and Google Gemini, and sandbox containment, are tech preview, in the notes. Governance policies and catalog opinions authored in the control plane are IBM-captive: Ceded.
Generally available. A developer assistant whose multi-model routing sends each task to Claude, Mistral, or Granite on accuracy, latency, and cost; 80,000 internal IBM users. Its routing acts at runtime and contributes a routing leg to the plane; under routing-is-not-reasoning it doesn't carry the cell alone. IBM IP: Ceded.
GA May 2026. Four sovereignty pillars: operational, data, technology, AI. AI sovereignty enforced at runtime, governing where inference happens, who controls models, how decisions are logged/traced/reviewed. Built on OpenShift + Red Hat AI. Mistral AI first certified model partner. Proprietary IBM platform: opinions captive, no open exit.
Governance Graph mapping AI assets through policies, risks, and regulatory requirements. Agentic monitoring and security capabilities. Cross-platform: governs IBM, OpenAI, AWS, Meta. Continuous compliance monitoring, not periodic audits. The governance query surface that a 2C control plane needs. Proprietary IBM platform: opinions captive, no open exit.
Generally available October 26, 2026. Registers each agent with its owner, risk classification, approved tool connections, and lifecycle state; issues short-lived, task-scoped OAuth tokens with on-behalf-of delegation and consent-aware authorization for sensitive actions; links human, agent, credential, policy decision, and action in a structured audit trail. Agents created or managed in watsonx Orchestrate have a documented onboarding path; HashiCorp Vault brokers credentials for systems that can't take a delegated token. IBM's inventory and authorization model: Ceded.
IBM says Agent Identity and HashiCorp Vault integrate with NVIDIA OpenShell's secure runtime (October 27, 2026). OpenShell itself is alpha and descored on every row, so the integration earns nothing here. No NVIDIA dependency in the plane.
IBM ships a complete Intelligence-2C plane, generally available, assembled from two products. Read against the five legs, with the join between them: Identity (generally available October 26, 2026): IBM Agent Identity, built around IBM Verify, registers each agent in a central inventory with its owner, risk classification, approved tool connections, and lifecycle state. It issues short-lived, task-scoped OAuth tokens, preserves on-behalf-of delegation across identity providers so an action traces back to the person it was taken for, and writes audit trails that link the human, the agent, the credential, the policy decision, and the downstream action. HashiCorp Vault brokers short-lived credentials for systems that can't take a delegated token. Gateway (generally available August 31, 2026): the watsonx Orchestrate AI Gateway applies policy at the gateway level to every agent connected through it. Registry (generally available): Orchestrate's shared agent catalog, fed by discovery and registration from Amazon Bedrock (generally available August 31, 2026). Orchestration (generally available June 2026): multi-agent orchestration across IBM, LangGraph, LangFlow, and A2A agents, where a model routes each task by the agents' and tools' descriptions. Observability (generally available August 31, 2026): the AgentOps Agent and agent evaluation, extended to models and MCP servers before deployment and in production on October 27, 2026. The seam is the identity join. Agent Identity and the Orchestrate control plane are separate products; IBM documents agents created or managed in Orchestrate as an onboarding path into Agent Identity, and wiring their tool connections into Verify policy is the architect's work. The cell counts the leg and names the seam as the enterprise's, the Azure reading for its architect-wired gateway. Around the plane: watsonx.governance maps AI assets through policies, risks, and regulations and monitors models IBM doesn't run; Sovereign Core enforces where inference runs; Bob's multi-model routing is a routing leg, and routing isn't reasoning. Strong. Calibration: beside Google Cloud and Databricks, whose planes are complete and generally available, and Azure, which assembles its plane from five products with the gateway join left to the architect. Salesforce, VMware, Snowflake, and Nutanix hold moderate with a leg missing. Cross-platform reach (Bedrock agents today, Agent Identity designed to sit beside Entra ID, Okta, and Ping) is real and isn't a leg. Infrastructure-2C, per-request placement across cost, residency, and capacity, isn't productized here or anywhere on the instrument, and the deterministic outcome-validator is likewise universal. Both are noted, not charged.
Delegated where the grade rests, at the model boundary. Orchestration is the leg the plane can't stand without, and inside it a model decides: Orchestrate routes each task to an agent or tool by reading their descriptions. The enterprise can see that call in traces and the audit trail, and its gates sit before the effect: gateway policies on every connected agent, each agent's approved tool connections and task-scoped tokens in Agent Identity, consent for sensitive actions, and real-time revocation of an agent or a credential. Model decides, visible, overridable: Delegated, the Azure reading. Portability: every chip is IBM's proprietary control plane, Ceded. The agent inventory, authority grants, gateway policies, and governance graph are opinions that rebuild on exit, and identity sitting beside Entra ID or Okta is reach, not an exit.
Not scored, tech preview (October 27, 2026; no GA date): watsonx Orchestrate Discover, which finds agents, models, and MCP servers on Microsoft Foundry and Google Gemini (preview since September 15, 2026), and Contain, which runs agents in isolated sandboxes with a kill switch. Named without a stated status: chat with third-party agents through Orchestrate channels (October 27, 2026). HashiCorp Vault 2.2 (generally available October 27, 2026) gives agents their own secured accounts and renews their credentials; it's named in the identity leg as the credential broker and isn't a separate chip. Deployment: IBM's GA announcement and product page don't say whether Agent Identity runs as IBM Verify SaaS, self-managed, or both; the product page names IBM Verify as the integration that carries agent identity. Source hierarchy: the October 27 Orchestrate post introduces the AI Gateway without a status; the September 3 post dates it generally available August 31, 2026, and governs. Infrastructure-2C (per-request placement across cost, residency, and capacity) is absent here as everywhere on the instrument; the deterministic outcome-validator is likewise universal and noted, not charged.
AI-powered business capabilities — business logic, workflow automation
Generally available prebuilt agents in the watsonx Orchestrate agent catalog, documented by IBM Developer, connecting to SAP SuccessFactors, Workday, Salesforce, Microsoft 365, and other systems of record. IBM's agent definitions, customized in IBM's builders: Ceded.
Enterprise asset management with predictive maintenance; version 9.1, generally available June 24, 2025, adds Maximo Assistant, a native generative-AI chat over asset data. Asset models, maintenance strategies, and predictive configurations are captive to Maximo: Ceded.
Business intelligence with an AI assistant, and financial planning with AI-assisted forecasting, natural-language analysis, and anomaly and driver insight (Planning Analytics Workspace 3.1.10). Reports, models, and cubes are IBM-specific: Ceded.
~160,000 consultants with an AI practice. Vertical industry solutions across banking, healthcare, government, and manufacturing. Delegated, not Retained: the Delegated definition covers a genuinely substitutable delivery partner, and a different systems integrator could deliver the same outcome. The enterprise keeps the right to change providers without rebuilding the layer, which is Delegated by definition; Retained is reserved for a commodity substrate the enterprise operates or a layer no vendor has claimed. The enterprise can select Deloitte, Accenture, Wipro, or a boutique for platform implementation without architectural impact. The SAP BASIS pattern: platform IP is the moat, implementation services are not.
NVIDIA NIM microservices and Agent Blueprints deployable on Red Hat AI Factory with NVIDIA. Same blueprints available across NVIDIA partners.
The boundary first. Layers 0 through 2C read IBM's AI infrastructure (its silicon and systems, storage and catalog, data movement, schedulers, model platform, and agent plane); Red Hat is its own row, and IBM Cloud sits outside this one. Layer 3 reads IBM's paper: the first-party business applications IBM sells under the same commercial relationship count, whichever product line hosts them (the methodology's company-paper rule, the OCI and Fusion precedent). Strong. IBM's application estate is broad, first-party, and generally available with AI inside it. The watsonx Orchestrate prebuilt domain agents cover HR, procurement, sales, customer care, finance, and supply chain, connecting to SAP SuccessFactors, Workday, Salesforce, and Microsoft 365. Maximo Application Suite runs enterprise asset management with predictive maintenance and, since 9.1 (generally available June 24, 2025), a native generative-AI assistant over asset data. Cognos Analytics carries an AI assistant, and Planning Analytics ships AI forecasting, natural-language analysis, and anomaly and driver insight. Envizi's ESG planning rides Planning Analytics; Sterling and Guardium are named here without scored AI evidence. That breadth across asset management, financial planning, analytics, and agentic business processes stands with the Salesforce, ServiceNow, SAP, and Oracle value planes, the best shipping implementations on the instrument. What separates IBM from them is the system of record: IBM's agents and applications often work over other vendors' records (SAP, Workday) rather than its own, which is a capture fact the DAPM column carries, not a grade gap. IBM Consulting (~160,000 consultants) is a competitive advantage in a substitutable services market, not a structural platform dependency. Enterprises switch AI platform implementation partners the same way they switch SAP BASIS support: IBM to Accenture, Accenture to Deloitte, Deloitte to Wipro. The platform doesn't notice. The open-source components (OpenShift, vLLM, KServe, Kubeflow) run identically regardless of which SI assembled them. IBM Consulting's advantage is scale and experience, not lock-in. This is structurally different from every other vendor's services model: • Dell's Accelerator Services are additive: the NVIDIA runtime works without Dell's humans. • HPE's Kamiwaza partnership is structural: remove Kamiwaza and HPE loses Layer 2C orchestration. • VAST requires minimal consulting because the platform makes architectural decisions for you. • IBM's consulting is the primary go-to-market motion for a platform built from open-source components. The components are free. The assembly expertise is what IBM sells. But any competent SI can provide the assembly expertise. IBM Consulting competes for the engagement; it doesn't own the engagement by virtue of platform architecture. Granite is read at 2B, where the model family is scored; a model isn't a business application. IBM Z/Power transactional AI (Telum on-chip inference beside the ledger for banking, insurance, and government) and watsonx Code Assistant for Z (Bob Premium for Z) are real and IBM-only, but neither is a business application: Telum is IBM silicon running inference, a Layer 0 and 2B fact, and the code assistant is a developer tool, which earns no Layer 3 grade. Neither carries the Layer 3 grade. The ISV ecosystem comparison: • Dell's ecosystem is broad and horizontal: 5,000+ customers, OpenAI, Palantir, Google, ServiceNow, SpaceXAI. • HPE's ecosystem is curated and vertical: 26+ ISVs through Unleash AI. • IBM's ecosystem is consulting-driven: IBM Consulting partnerships with SAP, Salesforce, Adobe, and ServiceNow. The OpenShift ISV ecosystem is scored on the Red Hat row.
IBM's applications carry IBM's judgment: the domain agents, Maximo, Cognos, and Planning Analytics decide inside IBM's application logic, and customization is configuration. Vendor decides, visible, not overridable, Ceded, the Salesforce, ServiceNow, and OCI reading for first-party applications. The ecosystem and services around them are substitutable. The consulting question is critical for DAPM: IBM Consulting is NOT a borrowed-judgment dependency. The enterprise retains full authority to select any SI for platform implementation, customization, and ongoing support. Switching SIs does not change the platform architecture, does not require re-engineering, and does not break running workloads. This is the SAP BASIS pattern: the platform IP (watsonx.governance, Orchestrate) is the structural dependency; the implementation services are a competitive market. The structural comparison: • Dell's ecosystem is load-bearing: ISV partners provide infrastructure-level functions. Remove Cohere North and Dell loses agent orchestration. • HPE's ecosystem is curated: partners provide domain applications. Remove Deloitte Zora AI and HPE loses a finance use case, not a platform function. • IBM's consulting is competitive: remove IBM Consulting and the enterprise hires Accenture. The platform remains intact. The adoption motion may slow but the architecture doesn't change. • VAST's ecosystem is additive: platform is self-sufficient. Partners add vertical use cases.
IBM's Layer 3 strategy is tightly focused on high-value, unglamorous enterprise utility: code modernization, automated compliance, legacy IT orchestration, mainframe fraud detection, rather than broad consumer-facing generative applications. Dell's Layer 3 partners are flashy (OpenAI, Palantir, SpaceXAI). HPE's Unleash AI partners target emerging AI use cases (video AI, geospatial, vision). IBM's Layer 3 targets the work enterprises actually need done: converting COBOL to Java, generating Ansible playbooks, detecting fraud in real-time transaction streams, modernizing mainframe applications. Nobody puts COBOL modernization on a keynote slide, but it's where regulated enterprise budgets concentrate. The watsonx application surfaces reinforce this enterprise utility focus: watsonx Assistant (conversational AI for customer service, HR, operations), watsonx Code Assistant / IBM Bob (AI-assisted development across the software lifecycle), watsonx Orchestrate applications (workflow automation binding agents to enterprise processes). These are not general-purpose AI platforms. They are purpose-built for specific enterprise operational domains. The 80,000 internal IBM Bob users represent the largest internal AI deployment from any vendor in this assessment. IBM is eating its own cooking at scale, and the 45% productivity gain claim, if sustained across production workloads, validates the agentic AI thesis more concretely than any vendor keynote. The EY tax technology partnership (Bob in private beta, described as 'closer to a collaborative agent than a simple coding tool') signals enterprise validation from a major professional services firm. Granite's Apache 2.0 licensing + uncapped IP indemnity is a distinctive governance posture. No other model family provides both open-source freedom AND vendor-backed legal protection. This addresses a specific enterprise concern: 'I want to run this model anywhere, and I don't want to worry about IP claims.' Neither OpenAI (closed-source, no indemnity) nor Meta (open-source, no indemnity) nor Google (Gemma open-weight but limited indemnity) matches this combination. The Kubernetes-baseline test at Layer 3: applications are inherently above the platform baseline, but IBM's distribution model matters. Granite models are Apache 2.0: run on any platform. IBM Consulting is substitutable. The OpenShift ISV ecosystem targets any Kubernetes. IBM's defensible Layer 3 assets are narrow: Z/Power transactional AI (hardware adjacency), Granite IP indemnity (legal wrapper), watsonx Code Assistant for Z (mainframe-specific), and the watsonx application surfaces that integrate with Layer 2C governance (watsonx.governance integration creates application-level governance that doesn't port to Tanzu). The governance integration is the subtle lock-in: applications built to leverage watsonx.governance's Governance Graph inherit a dependency on IBM's governance architecture.
IBM Think 2026, Red Hat Summit 2026, Red Hat AI 3.4 GA, watsonx Orchestrate next-gen preview, IBM Sovereign Core GA, IBM Concert public preview, IBM Confluent acquisition, Granite 4.1 release, analyst coverage (SiliconANGLE, NAND Research, Futurum Group, ECI Research) v1.5 (July 12, 2026, /reconcile): OpenShell descored from 2B to a dated watch-list line: alpha on four peer rows; GA-gate applies uniformly. 1A Ceph+Fusion chip split: open-source Ceph Retained, proprietary Fusion Ceded (one chip, one substrate). v1.6 (July 12, 2026, /ga-check): watsonx Orchestrate Agentic Control Plane promoted from the watch-list on doc-confirmed GA ('available today on AWS and IBM Cloud,' IBM announcement + release notes), scored as a Ceded 2C component; status holds moderate (Intelligence-2C governance, not placement). /reconcile (September 1, 2026): human-delivered services moved Retained to Delegated; a substitutable delivery partner is the Delegated definition. /reconcile (September 1, 2026): retired status vocabulary replaced with gap. /reconcile (September 1, 2026): shared 2C findings stated explicitly (live-placement universality, outcome-validation finding). /reconcile (September 1, 2026): the hard-coded cross-vendor 2C roster replaced with a shape-based reading. The roster had drifted out of agreement with the rows it described (HPE 2C scored three Ceded, not Retained plus Delegated) and went stale on every peer promotion. /reconcile (September 4, 2026, Elastic row): Layer 0 authority Ceded to Absent. The Ceded-invisible reading is for a vendor that absorbs the layer beneath its own service; OpenShift on OEM hardware absorbs nothing, so the layer reads Absent, matching Kamiwaza, Articul8, and Elastic. No status changed. /reconcile (October 5, 2026): Layer 3 partner to strong under the company-paper rule (ratified on this row): watsonx Orchestrate prebuilt domain agents, Maximo Application Suite, and Cognos plus Planning Analytics added as Ceded components, with the Red Hat focus and portfolio boundary stated in the cell. Granite removed from Layer 3 (already scored at 2B), multi-model support removed (platform enablement, which earns no Layer 3 grade), and the Z/Power chip removed (Telum is silicon, the code assistant a developer tool); the Layer 0 reading of Telum is logged for reconcile. Authority re-read to vendor / visible / not overridable / Ceded. v2.0 (/reconcile, October 5, 2026): the IBM / Red Hat OpenShift AI row split along the vendor support boundary; Red Hat now has its own row (redhat). This row rescoped to IBM's AI infrastructure and re-graded: Layer 0 gap to moderate (z17, Power11, Spyre, FlashSystem, Storage Scale System; IBM Cloud excluded as a separate cloud shape); 1A moderate to strong on a catalog that classifies the data (owned storage plus watsonx.data intelligence with integrated lineage); 1B held moderate on watsonx.data Milvus and Unstructured Data Integration; 1C held strong, the open ML pipeline stack moved to the Red Hat row and the Confluent chip aligned with the Confluent row; 2A held strong, re-grounded from OpenShift onto Spectrum LSF and Turbonomic, with the stale Concert entry corrected; 2B held moderate on watsonx.ai and Granite, the serving engine on the Red Hat row; 2C held moderate with the stale preview prose replaced by the generally available control plane and Agent Identity noted as private preview; Layer 3 boundary text updated and the Red Hat partner ecosystem chip moved to the Red Hat row. /reconcile (October 5, 2026): 1C authority column (rulings of September 15 and October 4, 2026). 1C authority vendor / Ceded to code / Retained: Confluent reads code / Retained on its own row, and DataStage runs the flows the enterprise designs. Grade unchanged. /reconcile (October 5, 2026): authority visible set from the cell's own text where it settles it: layer1a true. Direction, grades, and components unchanged. /reconcile (October 5, 2026): calibration text citing NetApp's AI Data Engine updated after its documentation was withdrawn and NetApp's 1A moved to moderate. Text only; grades and readings unchanged. v2.4 (Layer 0 sub-layers, October 16, 2026): Layer 0 split into 0A Compute, 0B Network Fabric and 0C Storage Substrate by runtime decision (Keith, October 16, 2026); storage left 1A for 0C, and 1A, now Data Foundation & Governance, is graded on the catalog that classifies the data. 0A moderate, 0B gap, 0C strong; summary edits (summary worksheet, Keith, October 16, 2026); 1C post-write fix (Item 4). v2.5 (October 19, 2026, /reconcile): 0C split the Storage Scale client and protocol chip into the native client (Ceded) and Cluster Export Services NFS, SMB and S3 (Delegated), the front-end reading on WEKA, Everpure and NetApp. Grade and authority unchanged. (Same pass) Plain-language pass: methodology rule numbers in the prose and audit notes replaced with the reasoning they stood for; no grade, chip or authority reading changed. v2.6 (October 19, 2026, /reconcile voice pass): em-dashes in the prose replaced with periods, colons, commas or parentheses; wording, grades, chips and authority readings unchanged. v2.7 (October 23, 2026, /reconcile): 0A notes record that IBM's z17 product page still footnotes Spyre as technology preview, and that the cell scores Spyre on its user's guide. Found by the 0A compute research. Grade and authority unchanged. v2.8 (October 23, 2026, /reconcile): 0C: Block arrays and a parallel-file appliance were one chip. Found by the Layer 0 data pass after the sniff read. Grade and cell authority unchanged. v2.9 (October 23, 2026, /reconcile): Layer 1 research pass. 1C: split (Platform, Cloud, Tableflow and Flink are separate products; "enterprise features" isn't a product). 1A: "watsonx.governance" removed (watsonx.governance governs AI assets (models, risks, regulations), not the data). Found by the Layer 1 slot cut. Grade and cell authority unchanged. v2.10 (October 23, 2026, Layer 1 calibration): IBM Confluent Platform reads Retained, as its own text and the Confluent row's self-run Kafka reading say. Grade unchanged. v2.11 (October 23, 2026, Layer 1 managed-services pass): watsonx.data gets a door; IBM Confluent Cloud splits; Managed Flink on IBM Confluent Cloud splits. Grade unchanged. v2.12 (October 24, 2026, /reconcile): GA evidence recorded on 2 of 2 Layer 1B chips under the GA evidence table. Grade unchanged. v2.13 (October 24, 2026, /reconcile): Layer 1B GA evidence migrated to the GA evidence table version 2. Grade unchanged. v2.14 (October 24, 2026, /reconcile): GA evidence recorded on 4 of 4 Layer 1A chips under the GA evidence table version 2. Grade unchanged. v2.15 (October 24, 2026, /reconcile): GA evidence recorded on 8 of 8 Layer 1C chips under the GA evidence table version 2. Grade unchanged. v2.16 (October 24, 2026, /reconcile): GA evidence recorded on 3 of 3 Layer 0A chips under the GA evidence table version 2. Grade unchanged. v2.17 (October 24, 2026, /reconcile): GA evidence recorded on 8 of 8 Layer 0C chips under the GA evidence table version 2. Grade unchanged. v2.18 (October 24, 2026, /reconcile): GA evidence recorded on 2 of 2 Layer 2A chips under the GA evidence table version 2. Grade unchanged. v2.19 (October 24, 2026, /reconcile): GA evidence recorded on 2 of 3 Layer 2B chips under the GA evidence table version 2. Grade unchanged. v2.20 (October 24, 2026, /reconcile): GA evidence recorded on 4 of 4 Layer 3 chips under the GA evidence table version 2. Grade unchanged. v2.21 (October 24, 2026, /reconcile): GA evidence recorded on 4 of 4 Layer 2C chips under the GA evidence table version 2. Grade unchanged. v2.22 (October 24, 2026, /reconcile): GA evidence table version 2.1 applied: 0 chips recorded or narrowed, 1 to notes. Grade unchanged. v2.23 (October 24, 2026, /reconcile): 2A prose updated: Run:ai is open source and reads Retained, so it no longer stands for the proprietary-scheduler reading. Grade unchanged. v2.24 (October 24, 2026, /reconcile): GA evidence quotes re-pointed to the live owner pages (3 chips) after the quote spot-check. Grade unchanged. v2.25 (October 27, 2026, IBM TechXchange): 2C moderate to strong. IBM Agent Identity became generally available October 26, 2026, filling the identity leg; with the AI Gateway (generally available August 31, 2026), the agent catalog, multi-agent orchestration, and AgentOps, the plane carries all five legs across two products, and the identity join is named as the architect's seam. Agent Identity added as a Ceded chip. 2C authority vendor to model (outside review, ruled by Keith): Orchestrate routes by description, so the model decides inside the orchestration leg; visible and overridable, Delegated, the Azure reading. Borrowed-judgment text rewritten to match the chips' Ceded readings. Discover and Contain (tech preview) and Vault 2.2 in the notes. 2A: IBM Concert, generally available October 27, 2026, scored as a Ceded day-two operations chip under the hardware-management placement rule (Keith); grade unchanged; watch-list entry retired. Z Atlas (public preview) named in 0A notes; the Orchestrate Premium Runtime (no stated status) in 2B notes.