# Layer2C — AI Infrastructure Decision Intelligence
> The CTO Advisor LLC · thectoadvisor.com · Updated July 17, 2026

Layer2C helps enterprise technology leaders evaluate where AI infrastructure vendors actually operate — across compute, data, orchestration, runtime, reasoning, and applications — and where your organization still owns governance, cost, evidence, and accountability.

Each assessment maps vendor capabilities against the 4+1 Layer AI Infrastructure Model and scores every component using the Decision Authority Placement Model (DAPM): Retained, Delegated, Ceded, or Absent.

Full article: https://thectoadvisor.com/blog/2025/11/05/the-cto-advisor-41-layer-ai-infrastructure-model/

## Framework

**8 Layers:**
- Layer 0: Compute & Network Fabric
- Layer 1A: Data Storage & Governance
- Layer 1B: Context Management & Retrieval
- Layer 1C: Data Movement & Pipelines
- Layer 2A: Infrastructure Orchestration
- Layer 2B: Application Runtime & Execution
- Layer 2C: Agentic Infrastructure — The Reasoning Plane
- Layer 3 (+1): AI Application Layer

**DAPM Classifications:**
- Retained — enterprise owns and controls this capability
- Delegated — provided by a substitutable partner; enterprise retains authority to swap
- Ceded — vendor controls this; enterprise consumes without governance authority
- Absent — no capability exists; enterprise must build or operate without it

**Layer Status Indicators:** ● Strength  ◑ Delegated/Partial  ○ Gap  ✕ Absent  ◇ Partner Ecosystem

## Vendors Assessed (23 complete)

### Articul8 AI Platform
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.1 - Reconcile: 2C Determinism Rule · July 17, 2026  
Source: Articul8 product pages, Series B announcement (Jan 2026), The CTO Advisor Enterprise Reasoning Plane whitepaper (Jan 2026), AWS Startups case study, SiliconANGLE coverage, VentureBeat coverage, Adara Ventures investment thesis, G2 profile, ZenML LLMOps database, Tracxn profile

**Layer Status:**  
○ Layer 0 · Compute: Compute & Network Fabric — Enterprise Responsibility  
◑ Layer 1A · Storage: Data Storage & Governance — Derived Semantic Layer  
● Layer 1B · Retrieval: Context Management & Retrieval — Articul8 Differentiator  
◑ Layer 1C · Pipelines: Data Movement & Pipelines — Autonomous Ingestion  
○ Layer 2A · Orchestration: Infrastructure Orchestration — Enterprise Responsibility  
● Layer 2B · Runtime: Application Runtime & Execution — ModelMesh Runtime  
◑ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Governed Mission Dispatch — Probabilistic Core  
● Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Domain Applications  

**DAPM Profile:** Retained 0 · Delegated 0 · Ceded 21 · Absent 0

**Summary:** Articul8 is a domain-specific GenAI platform that enters the buyer conversation at Layers 2B/2C/3 — the execution, reasoning, and application layers — and works downward into the data foundation (L1A/1B/1C). It is the heaviest top-of-stack vendor in the instrument: three strong layers (L1B, L2B, L3), three moderate (L1A, L1C, L2C), and two gaps (L0, L2A). Every layer it provides is Ceded.

---

### AWS AI Infrastructure
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.4 - Single-Vendor API Re-Lens & Label Reconciliation · July 12, 2026  
Source: re:Invent 2025, GTC 2026, Bedrock AgentCore GA, AgentCore Policy GA (Mar 2026), SageMaker Unified Studio, AWS/NVIDIA collaboration, OpenAI/AWS partnership, analyst coverage. v1.2 (instrument reconciliation): 1A S3 and 2A EKS Retained→Delegated — a managed service behind a multi-vendor standard interface is Delegated; Retained is reserved for an open substrate the enterprise operates. Corrects the prior over-application of Retained. Also aligned the VAST Layer 2C cross-reference to VAST's current gap status (PolicyEngine GA end 2026). v1.3 (lab-validated against the TFD corpus RAG build): added Amazon S3 Vectors (GA Dec 2025) to Layer 1B as a Ceded component (single-vendor vector API, no open exit), and added the self-orchestrate-versus-Bedrock-KB Retain/Delegate fork to the 1B and 1C narration, mirroring 2A/2B. v1.4 (July 12, 2026, /reconcile): the hyperscaler lens drift resolved — AWS's single-vendor managed services re-lensed under the litmus's own rule (single-vendor API = Ceded; Delegated requires a multi-vendor standard or open substrate), aligning the row with the Azure/GCP/OCI treatment of architecturally identical services. Chips moved D→C: Glue Catalog + Lake Formation, SageMaker Catalog (1A); Bedrock Knowledge Bases (1B); Bedrock, AgentCore Runtime (2B); Guardrails, AgentCore Policy, Evaluations + Memory (2C); Amazon Q, Kiro, Bedrock Agents (L3). Invalid dual-enum chips split into per-mode components (SageMaker managed Ceded / self-hosted Retained; Bedrock Agents Ceded / Strands apps Retained; Glue ETL Delegated / Unified Studio Ceded; MWAA Delegated / Step Functions Ceded). Agent Registry (Preview) descored to the watch-list per the GA-gate. statusLabels moved to capability vocabulary. No capability grades changed.

**Layer Status:**  
● Layer 0 · Compute: Compute & Network Fabric — Custom Silicon Full Stack  
● Layer 1A · Storage: Data Storage & Governance — Managed Data Foundation  
● Layer 1B · Retrieval: Context Management & Retrieval — Managed Retrieval Portfolio  
● Layer 1C · Pipelines: Data Movement & Pipelines — Managed Pipelines (Spark/Airflow Substrates)  
● Layer 2A · Orchestration: Infrastructure Orchestration — EKS + Capacity Management  
● Layer 2B · Runtime: Application Runtime & Execution — Bedrock + Open Paths  
◑ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Intelligence-2C Toolkit; Placement Implicit  
● Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Broadest Ecosystem  

**DAPM Profile:** Retained 3 · Delegated 7 · Ceded 20 · Absent 0

**Summary:** AWS is the first vendor in this assessment series that makes a credible claim across every layer of the 4+1 model — including Layer 2C. The structural difference between AWS and every on-prem vendor (Dell, HPE, VAST) is the direction of authority. On-prem vendors build upward from hardware, attempting to extend authority into orchestration and runtime layers. AWS builds downward from managed services, extending authority into custom silicon (Trainium, Inferentia, Graviton), custom networking (EFA/SRD, Nitro), and now on-prem infrastructure (AWS AI Factories).

---

### Microsoft Azure AI Infrastructure
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.3 - Label Vocabulary & Channel-Substitution Reconciliation · July 12, 2026  
Source: Build 2025, GTC 2026, KubeCon Europe 2026, FabCon/SQLCon 2026, Ignite 2024, Microsoft/OpenAI restructured agreement (April 2026), Entra Agent ID GA (April 2026), Agent Governance Toolkit (April 2026), Foundry Agent Service, analyst coverage. v1.2 (instrument reconciliation): 2A AKS Retained→Delegated — managed K8s behind a standard interface is Delegated, not Retained. Azure Blob remains Ceded (single-vendor API). v1.3 (July 12, 2026, /reconcile): statusLabels moved to capability vocabulary (authority lives in the DAPM chips); Azure Databricks Delegated→Ceded under the channel-substitution rule (proprietary platform Ceded-to-owner through any paper, matching the Databricks row).

**Layer Status:**  
● Layer 0 · Compute: Compute & Network Fabric — Hyperscale Compute Stack  
● Layer 1A · Storage: Data Storage & Governance — Unified Data Foundation (Fabric/OneLake)  
● Layer 1B · Retrieval: Context Management & Retrieval — Managed Retrieval (AI Search)  
● Layer 1C · Pipelines: Data Movement & Pipelines — Managed Pipelines (Fabric/ADF)  
● Layer 2A · Orchestration: Infrastructure Orchestration — AKS + Arc Hybrid Orchestration  
● Layer 2B · Runtime: Application Runtime & Execution — Foundry + OpenAI Runtime  
● Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Intelligence 2C: Productized | Infra 2C: Emerging  
● Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Broadest Enterprise Ecosystem  

**DAPM Profile:** Retained 1 · Delegated 6 · Ceded 16 · Absent 0

**Summary:** Microsoft Azure is the most structurally complex vendor in this assessment series because it operates three distinct authority systems simultaneously: a massive cloud infrastructure platform (Azure), a deeply integrated but newly non-exclusive frontier model partnership (OpenAI), and the largest enterprise software installed base on earth (Microsoft 365, Entra ID, Purview, Fabric). No other assessed vendor straddles all three domains. Google Cloud owns its frontier model outright. AWS partners with model providers at arm's length. Dell, HPE, and VAST operate below the model layer entirely. Microsoft is the only vendor that must coordinate authority across infrastructure, model intelligence, and enterprise application identity — and the April 2026 OpenAI restructuring has made that coordination both more flexible and more visible.

---

### Cisco Secure AI Factory with NVIDIA
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.5 - VAST GPL Re-read & DAPM Reconciliation · July 12, 2026  
Source: Cisco Live EMEA 2026, GTC 2026, RSA Conference 2026, Cisco Q3 FY2026 earnings, Galileo acquisition announcement (Apr 2026), AGNTCY/Linux Foundation donation (Jul 2025), DefenseClaw open source, Cisco/VAST partnership, analyst coverage, published 4+1 model. v1.5: two instrument rulings applied. (1) Whose-paper capability rule (the GPU parallel): the VAST AI Operating System is on Cisco's Global Price List with full Cisco support — the full platform deploys on Cisco paper, exposed and customer-administered, passing the exposure test; 1A/1B/1C promote moderate→strong at parity with the Supermicro row's identical delivery of the same engine. (2) Retraction of the OEM-channel DAPM rule: VAST components at 1A/1B/1C move Delegated→Ceded — a proprietary single-implementation platform's opinions are captive to its owner through any paper, matching VAST's own row. statusLabels moved to capability vocabulary. Capability grades and authority chips now read on their own axes.

**Layer Status:**  
● Layer 0 · Compute: Compute & Network Fabric — Networking Strength — Asymmetric  
● Layer 1A · Storage: Data Storage & Governance — Partner-Delivered Data Platform  
● Layer 1B · Retrieval: Context Management & Retrieval — Partner-Delivered Retrieval  
● Layer 1C · Pipelines: Data Movement & Pipelines — Partner-Delivered Pipeline Engines  
◑ Layer 2A · Orchestration: Infrastructure Orchestration — Networking-Centric Orchestration  
◑ Layer 2B · Runtime: Application Runtime & Execution — Security Layer — Not Runtime  
◑ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Security + Identity — Not Yet Governance  
◇ Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Partner Ecosystem  

**DAPM Profile:** Retained 6 · Delegated 2 · Ceded 24 · Absent 0

**Summary:** Cisco is the only vendor in this assessment series whose AI infrastructure authority is anchored by networking and security rather than compute, storage, or cloud services. Where Dell builds up from servers, HPE from sovereign compute, VAST from storage, and hyperscalers from managed services, Cisco builds outward from the network fabric and security posture that connects everything else. The Secure AI Factory with NVIDIA is a reference architecture, not a vertically integrated platform — and that distinction defines Cisco's entire 4+1 profile.

---

### CoreWeave AI Cloud
*The Open-Substrate Neocloud — Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.4 - Label Vocabulary & Managed-Service Chip Reconciliation · July 12, 2026  
Source: CoreWeave Platform and Storage docs, NVIDIA GTC 2026 (HGX B300 GA, Vera Rubin NVL72 H2 2026), SUNK / CKS / Mission Control product pages and docs, CoreWeave AI Object Storage (CAIOS) + LOTA, Distributed File Storage, Dedicated storage tiers (VAST/WEKA/DDN/IBM Spectrum Scale/Pure), CoreWeave Sandboxes, Weights & Biases acquisition (closed 2025) and unified agentic AI launch (May 2026 — Serverless RL, CoreWeave Inference, W&B Weave, W&B Skills), NVIDIA $2B investment (Jan 2026), SEC filings, analyst coverage. v1.1 added Dedicated storage tier + Sandboxes (CoreWeave AR, May 29 2026). v1.2 corrects the 1A authority reasoning: the architectural guarantee is CoreWeave's SLA on a CoreWeave service — the storage substrate (VAST/WEKA/etc.) is an implementation detail invisible to the customer and is removed from the DAPM call, consistent with not scoring a hyperscaler's object store on its drive supplier. v1.4 (July 12, 2026, /reconcile): statusLabels moved to capability vocabulary; CKS+SUNK (2A) and CKS open serving (2B) Retained→Delegated — CoreWeave-operated managed services behind standard interfaces take the EKS-class treatment; Retained is reserved for substrates the customer operates (SUNK Anywhere self-host noted as that form).

**Layer Status:**  
● Layer 0 · Compute: Compute & Network Fabric — NVIDIA-Reference Cloud Compute  
◑ Layer 1A · Storage: Data Storage & Governance — Open Default Storage + Dedicated Tier  
○ Layer 1B · Retrieval: Context Management & Retrieval — Enterprise-provided  
○ Layer 1C · Pipelines: Data Movement & Pipelines — Fast Transport, No Pipeline Layer  
● Layer 2A · Orchestration: Infrastructure Orchestration — Open-Substrate GPU Orchestration  
● Layer 2B · Runtime: Application Runtime & Execution — Strong — authority splits by what you use  
○ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Gap: Improvement Loop, Not a Reasoning Plane  
◑ Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — W&B developer plane — captive opinion layer  

**DAPM Profile:** Retained 0 · Delegated 4 · Ceded 8 · Absent 0

**Summary:** CoreWeave is a pure-play NVIDIA GPU cloud whose entire differentiation lives at three layers — the compute fabric (0), infrastructure orchestration (2A), and application runtime (2B) — and which is, unusually for a cloud in this assessment, built deliberately on open substrate. Its orchestration opinions rest on Kubernetes (CKS) and Slurm (SUNK), not a proprietary managed scheduler, and SUNK Anywhere runs those same workflows on non-CoreWeave and on-prem clusters with few configuration changes. That makes CoreWeave's orchestration layer the rare cloud cell that reads as Retained rather than Ceded.

---

### Databricks Data Intelligence Platform
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.0 - Initial Assessment · June 21, 2026  
Source: docs.databricks.com, Data + AI Summit 2025 & 2026 announcements, Databricks blog/newsroom (Lakeflow GA, Lakebase GA, Agent Bricks, Unity AI Gateway, Unity Catalog open-source), MLflow 3 release notes, analyst coverage, published 4+1 model

**Layer Status:**  
○ Layer 0 · Compute: Compute & Network Fabric — Not Databricks' Layer (By Design)  
● Layer 1A · Storage: Data Storage & Governance — Lakehouse Strength — Open Formats, Captive Governance  
● Layer 1B · Retrieval: Context Management & Retrieval — Lakehouse-Native Governed Retrieval  
● Layer 1C · Pipelines: Data Movement & Pipelines — Data Engineering Heartland  
◑ Layer 2A · Orchestration: Infrastructure Orchestration — Managed Workload Orchestration; GPU Scheduling Pre-GA  
● Layer 2B · Runtime: Application Runtime & Execution — Mosaic AI Runtime — Serving + Agents (GA)  
◑ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Agent Governance via Unity Catalog — Not Placement Reasoning  
● Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — First-Party Data Apps + Marketplace Ecosystem  

**DAPM Profile:** Retained 0 · Delegated 5 · Ceded 20 · Absent 0

**Summary:** Databricks is a data + AI lakehouse platform that floats above Layer 0 — it owns no silicon and runs on AWS, Azure, and GCP — and is strong across the entire data and application stack: storage and governance (1A), retrieval (1B), pipelines (1C), runtime (2B), and the value plane (3). It moderates only where it does not own the layer: infrastructure orchestration (2A), where it rents cloud compute and its GPU scheduling is still pre-GA, and the reasoning plane (2C), where it provides governance and multi-agent orchestration but not live placement. Its authority sits in the opinion layer, never the substrate.

---

### Dell AI Factory with NVIDIA
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v2.6 - Codified-Criteria Audit & Watch-List Roll · July 12, 2026  
Source: DTW 2026, GTC 2026, Dell press releases (March 16, May 18, June 22, 2026), Dell InfoHub documentation, Dell AI infrastructure product/marketing briefing (July 2026), published 4+1 model. v2.5 (briefing + DAPM axis reconciliation): DAPM re-reasoned from the customer's seat throughout — the rating measures the enterprise-to-vendor authority relationship; vendor-to-vendor framing (Dell-cedes-to-NVIDIA) retired to the nvidia[] dependency column and borrowedJudgment narrative. 2A Dell CSI Operator Ceded→Delegated (consumed interface is the multi-vendor CSI/K8s standard). GA-gate descores to dated watch-lists: 1A Exascale (targeted early 2H CY26, unconfirmed), 1C KV cache offload (NVIDIA CMX pre-GA), 2B Deskside Agentic AI (NemoClaw/OpenShell alpha). 1B GPU-accelerated DSE watch-listed: upstream Elasticsearch 9.4 took cuVS to GA April 2026, but upstream GA never moves an OEM cell — Dell-side GA unconfirmed in Dell docs. statusLabel convention ratified: capability vocabulary only; authority lives in the per-component DAPM chips. Summary rewritten: capture mechanism named (decoupled/invisible); 2C gap upgraded from instrument finding to vendor-confirmed deliberate ecosystem strategy. No layer status changed. v2.6 (July 12, 2026, codified-criteria audit): the canonical row re-read under the methodology's new capability grading criteria and channel-substitution rule. Trust3 Delegated→Ceded (proprietary governance platform; policies captive to the partner through any paper). 2B blueprint component re-reasoned to menu-altitude Delegated (deployed platforms capture per-choice, to the ISV). 1B held at moderate with the frontier check written in (rule 6: DSE is general but below the integrated-retrieval frontier, GPU path unconfirmed). Watch-lists rolled: Exascale still 2H 2026 (now expanding to 4-in-1 with PowerFlex, 1H 2027); GPU-accelerated DSE flagged as slipped — Dell's '1H 2026' passed without doc confirmation. No layer status changed.

**Layer Status:**  
● Layer 0 · Compute: Compute & Network Fabric — Dell Strength  
● Layer 1A · Storage: Data Storage & Governance — Dell Strength  
◑ Layer 1B · Retrieval: Context Management & Retrieval — Elastic-Powered Retrieval  
◑ Layer 1C · Pipelines: Data Movement & Pipelines — Dell + Dataloop  
◑ Layer 2A · Orchestration: Infrastructure Orchestration — Rack-Level Management  
◑ Layer 2B · Runtime: Application Runtime & Execution — Blueprints + Services  
○ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Enterprise Responsibility  
◇ Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Partner Ecosystem  

**DAPM Profile:** Retained 4 · Delegated 11 · Ceded 9 · Absent 0

**Summary:** Dell has one of the most credible on-prem AI Factory infrastructure stacks in the market. Its credibility comes from physical infrastructure (Layer 0), storage and data lifecycle integration (Layers 1A/1B/1C, where the Dataloop acquisition gives Dell its first proprietary software asset in the data lifecycle), and ecosystem packaging (Layer 3). From the buyer's seat, the authority profile is just as legible: the enterprise retains commodity compute, cedes its storage and pipeline opinions to Dell, and inherits NVIDIA's judgment for everything GPU-aware above the rack.

---

### Google Cloud AI Infrastructure
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.4 - Label Vocabulary & Chip Enum Reconciliation · July 12, 2026  
Source: Google Cloud Next 2026 (Apr 22–24), GTC 2026, NVIDIA partnership, Forrester, SiliconANGLE, The New Stack, analyst coverage. v1.2 (instrument reconciliation): 2A GKE Retained→Delegated — managed K8s behind a standard interface is Delegated, not Retained. Cloud Storage remains Ceded (GCS-native API). v1.3 (lab-validated against the TFD corpus / vCTOA RAG build): added the retrieval surface to Layer 1B - Vertex AI Search (Discovery Engine, the Bedrock Knowledge Bases analog), BigQuery Vector Search, and Firestore Vector Search, all Ceded (single-vendor APIs); demoted the preview LookML Agent from a scored component to a notes watch-line per the GA-gate; and added the self-orchestrate-versus-managed Retain/Delegate fork to 1B/1C, mirroring the AWS row.

**Layer Status:**  
● Layer 0 · Compute: Compute & Network Fabric — TPU + GPU Full Stack  
● Layer 1A · Storage: Data Storage & Governance — Model-Powered Governance  
● Layer 1B · Retrieval: Context Management & Retrieval — Model Prep & Managed Retrieval  
● Layer 1C · Pipelines: Data Movement & Pipelines — Managed Pipeline Portfolio  
● Layer 2A · Orchestration: Infrastructure Orchestration — GKE + Sovereign Extensions  
● Layer 2B · Runtime: Application Runtime & Execution — Model-Integrated Stack  
● Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Productized Placement  
● Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Open Model Layer, Captive Platform  

**DAPM Profile:** Retained 1 · Delegated 5 · Ceded 32 · Absent 0

**Summary:** Google Cloud is the only vendor in this assessment series that owns a frontier foundation model — and that single fact restructures the entire 4+1 analysis. Google built Gemini, trains Gemini on its own TPUs, optimizes its silicon for Gemini’s training requirements, and weaves Gemini’s intelligence into every layer of its cloud platform. This creates a model-integrated stack: an architecture where the frontier model is not a component plugged into infrastructure but the intelligence that pervades the infrastructure.

---

### HPE Private Cloud AI
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.8 - 1A Frontier Promotion & Label Reconciliation · July 12, 2026  
Source: GTC 2026, HPE GreenLake/storage May 2026 announcements, Discover 2025, Juniper acquisition, Town of Vail whitepaper, analyst coverage. v1.6: vendor name updated from 'HPE AI-Native Infrastructure' to 'HPE Private Cloud AI'. v1.7: Kamiwaza components at 1B/1C/2B/2C moved Delegated→Ceded under the instrument's retraction of the OEM-channel DAPM rule (a proprietary single-implementation platform is Ceded-to-partner through any paper; partnership substitutability claims fail the lift-to-leave litmus) — calibrated to Kamiwaza's own row, which scores the same surfaces Ceded. 2C statusLabel moved to capability vocabulary. Bracketing narrative corrected: the capability advantage over Dell survives; the authority reading is capability-with-capture versus no-capability-no-capture. No capability grades moved. v1.8 (July 12, 2026, /reconcile): 1A moderate→strong under the whose-paper and frontier rules (owned Alletra/Data Fabric/Polaris/Zerto depth; drift vs. Lenovo 1A strong resolved). 1B/2B statusLabels moved to capability vocabulary. 2C prose corrected: Google’s productized 2C is Ceded per the GCP row, not Retained.

**Layer Status:**  
● Layer 0 · Compute: Compute & Network Fabric — HPE Strength  
● Layer 1A · Storage: Data Storage & Governance — Owned Storage + Governance Strength  
◑ Layer 1B · Retrieval: Context Management & Retrieval — Reference Stack + Partner Orchestration  
◑ Layer 1C · Pipelines: Data Movement & Pipelines — HPE + Open Source  
● Layer 2A · Orchestration: Infrastructure Orchestration — HPE Strength  
◑ Layer 2B · Runtime: Application Runtime & Execution — NVIDIA Runtime + Framework Surface  
◑ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — IT-Ops Reasoning + Partner AI Orchestration  
◇ Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Unleash AI Ecosystem  

**DAPM Profile:** Retained 4 · Delegated 7 · Ceded 27 · Absent 0

**Summary:** HPE presents the most structurally interesting comparison to Dell in the 4+1 model because it makes genuine software authority claims that Dell does not. Three capabilities differentiate HPE's architectural position: GreenLake Intelligence (agentic AI mesh using domain-specific LLMs via MCP — HPE-owned Layer 2A/2C for IT operations), the $14B Juniper Networks acquisition (full networking IP stack from silicon to software — owned networking depth that Dell entirely delegates to NVIDIA Spectrum), and the Unleash AI program with Kamiwaza as the chosen Layer 2C orchestration partner (validated in production at Town of Vail).

---

### IBM / Red Hat OpenShift AI
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.6 - ACP GA Promotion · July 12, 2026  
Source: 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).

**Layer Status:**  
○ Layer 0 · Compute: Compute & Network Fabric — No IBM Silicon (OEM-Provided)  
◑ Layer 1A · Storage: Data Storage & Governance — Governance Strength, Storage Gap  
◑ Layer 1B · Retrieval: Context Management & Retrieval — Open-Source Assembled  
● Layer 1C · Pipelines: Data Movement & Pipelines — Confluent + Open-Source Pipeline  
● Layer 2A · Orchestration: Infrastructure Orchestration — OpenShift Strength  
◑ Layer 2B · Runtime: Application Runtime & Execution — Open-Source Runtime + NVIDIA  
◑ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Most Explicit 2C Claim  
◇ Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Consulting-Led Ecosystem  

**DAPM Profile:** Retained 9 · Delegated 6 · Ceded 13 · Absent 0

**Summary:** IBM / Red Hat is the only vendor in this assessment series attempting to build an enterprise AI operating model from middleware outward. Where Dell builds upward from hardware, VAST builds upward from storage, and Google builds downward from model intelligence, IBM builds from the platform layer — Red Hat OpenShift as the universal substrate — and extends authority in both directions: downward into infrastructure governance (Sovereign Core, Concert) and upward into agent orchestration (watsonx Orchestrate). The platform is the distribution vehicle, not the value. The value is the governance and orchestration intelligence that rides on top.

---

### Intel AI Infrastructure Portfolio
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.0 — Initial Assessment · June 26, 2026  
Source: Intel 2025/2026 earnings releases (SEC 8-K), Intel Newsroom (Gaudi 3 availability, Xeon 6 and Xeon 6+ 'Clearwater Forest' launch, agentic AI systems), IBM Cloud / Intel Gaudi 3 availability announcement, NVIDIA Investor Relations (Sep 2025 strategic agreement and $5B investment), OPEA (LF AI & Data) and oneAPI documentation, OpenVINO documentation, IT@Intel Agentic AI white paper (Oct 2025), DPDK and SPDK (Linux Foundation) project documentation, The Register / ServeTheHome Clearwater Forest launch coverage (Computex 2026), published 4+1 model.

**Layer Status:**  
◑ Layer 0 · Compute: Compute & Network Fabric — CPU Strong, Accelerator Present-but-Thin, No Fabric  
○ Layer 1A · Storage: Data Storage & Governance — Substrate Provider, Not a Storage Offering  
○ Layer 1B · Retrieval: Context Management & Retrieval — Open Reference Only, Not an Offering  
○ Layer 1C · Pipelines: Data Movement & Pipelines — Substrate Provider, Not a Pipeline Offering  
○ Layer 2A · Orchestration: Infrastructure Orchestration — Substrate Provider, No Orchestration Offering  
◑ Layer 2B · Runtime: Application Runtime & Execution — Open Runtime Tooling, No Managed Service  
○ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — No Control Plane  
○ Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Silicon Enabler, Not Application Vendor  

**DAPM Profile:** Retained 2 · Delegated 4 · Ceded 0 · Absent 0

**Summary:** Intel is the only ingredient vendor in this instrument. Every other row — Dell, HPE, AWS, Google Cloud, Azure, VAST, VMware, Cisco, IBM/Red Hat, Oracle — is an integrator or operator that assembles Layers 0 through 3 into a system the enterprise buys whole. Intel is the component and open-standards company all of them buy from. Its authority sits entirely at Layer 0, where it is strong on CPU, present but thin on accelerator, and absent on fabric. Above Layer 0 it ships no procurable platform. But it is the open substrate the rest of the stack runs on, and that distinction is the assessment, not a deficiency to apologize for.

---

### Kamiwaza AI Orchestration Platform
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.2 - Reconcile: 2C Determinism Rule (held strong) · July 17, 2026  
Source: Kamiwaza 1.0 launch (May 2026), Kamiwaza v0.9.3 docs, product pages, HPE Town of Vail whitepaper, Tracxn profile, SecurityBrief coverage, GitHub repos

**Layer Status:**  
○ Layer 0 · Compute: Compute & Network Fabric — Enterprise Responsibility  
◑ Layer 1A · Storage: Data Storage & Governance — Derived Artifact Layer  
● Layer 1B · Retrieval: Context Management & Retrieval — Kamiwaza Differentiator  
○ Layer 1C · Pipelines: Data Movement & Pipelines — Enterprise Responsibility  
○ Layer 2A · Orchestration: Infrastructure Orchestration — Enterprise Responsibility  
◑ Layer 2B · Runtime: Application Runtime & Execution — Kamiwaza Runtime  
● Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Kamiwaza Core  
◑ Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Platform + Kaizen  

**DAPM Profile:** Retained 0 · Delegated 3 · Ceded 15 · Absent 0

**Summary:** Kamiwaza is a software-only AI orchestration platform that enters the buyer conversation at Layer 2C and works downward. It is one of only two vendors in the instrument — alongside Articul8 — whose primary product includes the reasoning plane. Where Articul8's Intelligence-2C focuses on mission decomposition and domain-specific agent routing, Kamiwaza's Intelligence-2C focuses on governance: cross-agent authority, relationship-based access control, and policy enforcement at execution time. The enterprise gets production-validated cross-agent governance that no other on-prem vendor provides independently.

---

### Lenovo Hybrid AI Advantage with NVIDIA
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.1 - DAPM Retraction & Capability Re-read · July 11, 2026  
Source: v1.1 (same day): corrections from the Supermicro-session instrument rulings. The OEM-channel DAPM rule was retracted — a proprietary single-implementation platform is Ceded-to-partner through any paper; Delegated survives only via open/self-hostable substrates or multi-vendor standard interfaces. Chips moved: 1A DM/DG (ONTAP), DE (SANtricity), and WEKA Delegated→Ceded; 2B Nutanix Delegated→Ceded. Cloudian (S3), Red Hat, AI Library runtime, and TruScale survive on litmus grounds. 1A re-read under the whose-paper capability rule (the GPU parallel): moderate→strong on the productized menu plus owned InfiniBox. 1C re-examined under the exposure test and held at gap (no productized pipeline engine on Lenovo paper). Summary paragraph 2 rewritten accordingly. Original v1.0 source: CES 2026 (Lenovo Agentic AI + xIQ launch, AI Cloud Gigafactory, Jan 6), GTC 2026 (inference platforms, Vera Rubin support, March), Lenovo press releases (May 12 and June 24, 2026), Lenovo Press product documentation (Hybrid AI Software Platform lp2311, Hybrid AI 221/285/289 platform guides, Cloudian LVD lp2388, Centific LVD lp2180), Infinidat acquisition close (April 9, 2026), Cloudian/WEKA Lenovo SKU and reseller-agreement evidence, published 4+1 model. Assessment notes: InfiniBox components added in grading review (assessor initially missed the April 2026 Infinidat close; caught by human review). xIQ Agent Platform and xIQ Hybrid Cloud Platform descored to dated watch-lists under the GA-gate — announced January 6, 2026, no product documentation or part numbers as of July 11, 2026. Fabric DAPM reasoned from the customer's seat per the instrument's v2.5 Dell ruling: resale-vs-brand is vendor-to-vendor framing and does not move a customer-seat rating.

**Layer Status:**  
● Layer 0 · Compute: Compute & Network Fabric — Lenovo Strength  
● Layer 1A · Storage: Data Storage & Governance — Owned High-End + Partner-Delivered Strength  
◑ Layer 1B · Retrieval: Context Management & Retrieval — Validated Retrieval — Partner Stack  
○ Layer 1C · Pipelines: Data Movement & Pipelines — Enterprise Responsibility  
◑ Layer 2A · Orchestration: Infrastructure Orchestration — Fleet Management + Consumption Orchestration  
◑ Layer 2B · Runtime: Application Runtime & Execution — Validated Runtimes + Services  
○ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Enterprise Responsibility  
◑ Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — First-Party Agents + ISV Ecosystem  

**DAPM Profile:** Retained 4 · Delegated 8 · Ceded 10 · Absent 0

**Summary:** Lenovo has one of the most credible on-prem AI infrastructure foundations in the market. Among the on-prem anchors on this instrument, each builds from what it owns: Dell from servers and storage, HPE from sovereign compute and three owned fabrics, Cisco from network silicon and security. Lenovo's anchor is manufacturing scale and thermal engineering — server breadth, Neptune sixth-generation liquid cooling, eight of the top ten public clouds as customers — and it is the only one of the four that owns neither a network fabric nor, until the April 2026 Infinidat close, any opinion-bearing storage software. Above the rack, capability arrives predominantly as other vendors' IP validated and SKU'd on Lenovo paper: ONTAP, Cloudian, WEKA, Red Hat, Nutanix, NVIDIA.

---

### NetApp Intelligent Data Infrastructure
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.4 - AIPod Mini Whose-Paper Ruling · July 13, 2026  
Source: NetApp INSIGHT 2025 (Oct 14-16, 2025), NVIDIA GTC 2026 (Mar 16-19, 2026), netapp.com / docs.netapp.com (ONTAP, AFF/ASA/AFX, StorageGRID, AIPod, AI Data Engine, NetApp Console/BlueXP, Trident), AWS/Azure/GCP first-party service docs, analyst/press coverage (TechTarget, Blocks & Files, StorageMath), published 4+1 model. v1.1 (instrument reconciliation): clarified that Layer 1C credits a data-movement decision/orchestration capability (policy-driven replication/tiering/caching), not transparent transport throughput — distinguishing NetApp's movement decisions from CoreWeave-style byte-transport acceleration. v1.2: Trident at 2A corrected Ceded→Delegated — the consumed interface is CSI/Kubernetes, a multi-vendor standard (Dell v2.5 CSI Operator precedent), and Trident is Apache 2.0; the v1.1 Ceded call confused what the driver connects to (NetApp storage, captured at 1A) with where provisioning opinions accumulate (Kubernetes-standard objects). 1A note added recording the Lenovo DM/DG channel pairing (capture is NetApp's through any paper, per the July 2026 OEM-channel retraction). v1.3 (same day, /ga-check): AI Data Engine promoted on doc-confirmed GA (docs.netapp.com/us-en/ai-data-engine — AIDE 9.18.1 U0/U1 and 1.0.0 release notes). 1B gap→moderate with AIDE vectorization/RAG retrieval endpoints scored Ceded; Metadata Engine added as a 1A component (Ceded); the watch-list's native-vector-DB question resolved native. Guardrails remain wrong-function at 2C (gap holds). 1C re-read resolved same day under the newly codified general-versus-fixed-function criterion (capability rule 4): AIDE's ingest pipeline scored as a Ceded 1C component, cell holds at moderate — the slice ships, the general half of the layer remains the enterprise's. v1.4 (July 13, 2026): NetApp AIPod Mini with Intel assessed against 2B and ruled out under the whose-paper rule (validated reference design on Supermicro compute, open-source OPEA runtime, SI-delivered — not a NetApp-paper product). No cell moved; recorded in 2B gap/notes as a second meet-in-the-middle path that confirms the storage-half finding.

**Layer Status:**  
◑ Layer 0 · Compute: Compute & Network Fabric — Software-Defined Storage Fabric  
● Layer 1A · Storage: Data Storage & Governance — NetApp Strength — Data Foundation  
◑ Layer 1B · Retrieval: Context Management & Retrieval — AIDE Retrieval — Storage-Integrated  
◑ Layer 1C · Pipelines: Data Movement & Pipelines — Best-in-Class Movement + AI-Ingest Pipeline  
◑ Layer 2A · Orchestration: Infrastructure Orchestration — Data-Infrastructure Control Plane; No GPU Scheduling  
○ Layer 2B · Runtime: Application Runtime & Execution — Runtime is NVIDIA's (Meet-in-the-Middle)  
○ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — No Reasoning Plane (Data Guardrails ≠ Agent Governance)  
○ Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — No Value Plane — Data Foundation Beneath Others' Apps  

**DAPM Profile:** Retained 0 · Delegated 3 · Ceded 10 · Absent 0

**Summary:** NetApp is a storage and data-management vendor whose authority concentrates in one of the most mature governed data foundations in the market (Layer 1A) and the storage-adjacent infrastructure around it — a software-defined storage fabric (Layer 0), best-in-class data movement (Layer 1C), and a hybrid-multicloud data control plane (Layer 2A). For the AI execution, reasoning, and application layers, NetApp is the data half of a meet-in-the-middle AI factory (AIPod): the compute, model-serving runtime, retrieval, and applications are NVIDIA's, sold alongside through the channel — not NetApp's.

---

### Nutanix Cloud Platform with Enterprise AI
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.1 - Interface-Portability Reconciliation · June 20, 2026  
Source: .NEXT 2026 (Apr 2026), .NEXT 2025, NAI 2.7 (May 2026), AOS 7.5 / AHV 11 / Prism Central pc.7.5, NUS 5.3, NDB v2.10, NKP 2.17, Nutanix Bible, NVIDIA vGPU product-support matrix for AHV, published 4+1 model. v1.1 (instrument reconciliation): 1A NUS Objects Retained→Delegated, resolving the internal split with NKP (2A) — proprietary implementation behind a multi-vendor standard is Delegated, not Retained.

**Layer Status:**  
◑ Layer 0 · Compute: Compute & Network Fabric — Hardware-Agnostic Abstraction  
◑ Layer 1A · Storage: Data Storage & Governance — Platform Storage + Compliance Governance, Not AI-Native  
◑ Layer 1B · Retrieval: Context Management & Retrieval — Foundational RAG via Managed Postgres  
○ Layer 1C · Pipelines: Data Movement & Pipelines — Gap  
● Layer 2A · Orchestration: Infrastructure Orchestration — Nutanix Heritage Strength  
◑ Layer 2B · Runtime: Application Runtime & Execution — Platform-Native Serving, Agents Pre-GA  
○ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Emerging Signals — Governance Without Placement  
◑ Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Platform-Enabled, Not Platform-Provided  

**DAPM Profile:** Retained 1 · Delegated 9 · Ceded 8 · Absent 0

**Summary:** Nutanix occupies the same structural position as VMware — an HCI / private-cloud platform, an abstraction layer running on commodity x86 it does not manufacture — and against the 4+1 model it produces a strikingly similar profile: strongest at infrastructure orchestration (Layer 2A), competent across the data and runtime layers, and gapped at data pipelines (Layer 1C) and the reasoning plane (Layer 2C). Its deepest IP and authority sit in the orchestration control plane: Prism, AOS, and AHV.

---

### NVIDIA AI Platform
*A Components Company Becoming a Platform Vendor — Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.3 - Prose-Coherence (GA-Gate) · May 22, 2026  
Source: GTC 2025, GTC 2026, Dynamo 1.0 GA, NemoClaw/OpenShell announcement, Run:ai acquisition, DGX Cloud, NVIDIA AI Enterprise, NIM GA, analyst coverage, SEC FY2026 annual report

**Layer Status:**  
● Layer 0 · Compute: Compute & Network Fabric — NVIDIA Strength — Silicon Authority  
○ Layer 1A · Storage: Data Storage & Governance — Accelerator Only  
◑ Layer 1B · Retrieval: Context Management & Retrieval — Acceleration + Model Enablement  
○ Layer 1C · Pipelines: Data Movement & Pipelines — Gap — single pre-GA capability  
● Layer 2A · Orchestration: Infrastructure Orchestration — NVIDIA Authority via Run:ai  
● Layer 2B · Runtime: Application Runtime & Execution — NVIDIA Authority — Inference + Agent Runtime  
○ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Runtime Governance Only — Not a Reasoning Plane  
◑ Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Model + Blueprint Enablement  

**DAPM Profile:** Retained 2 · Delegated 3 · Ceded 8 · Absent 0

**Summary:** NVIDIA is the only vendor in this assessment series that appears inside every other vendor's assessment. Dell's Layer 2A GPU orchestration is NVIDIA Run:ai. HPE's Layer 2B runtime is NVIDIA AI Enterprise. VMware's GPU integration is NVIDIA vGPU Manager. AWS, Google Cloud, and Azure all run NVIDIA GPUs alongside their own silicon. VAST embeds NVIDIA GPUs, NICs, DPUs, and switches into its data platform. Mapping NVIDIA as a standalone vendor inverts the perspective: instead of asking 'where does Dell cede authority to NVIDIA,' the question becomes 'where does NVIDIA claim authority, and from whom?'

---

### Oracle Cloud Infrastructure (OCI) AI Infrastructure
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.5 - Compute Management GA Promotion · July 12, 2026  
Source: Oracle AI World 2025, GTC 2026, OCI Enterprise AI GA (Mar 2026), Fusion Agentic Applications (Mar 2026), Oracle AI Database 26ai, Stargate/OpenAI partnership, NVIDIA/AMD partnerships, analyst coverage, Oracle Q3 FY2026 earnings. v1.3 (instrument reconciliation): 1A OCI Object Storage and 2A OKE Retained→Delegated — a managed service behind a multi-vendor standard interface is Delegated, not Retained. Also aligned the VAST Layer 2C cross-reference to VAST's current gap status. v1.4 (July 12, 2026, /reconcile): statusLabels moved to capability vocabulary per the instrument convention; no grades or chips changed. v1.5 (July 12, 2026, /ga-check): OCI Compute Management promoted from the watch-list on OCI product documentation (instance pools, cluster networks, capacity reservations) — scored as a Ceded 2A component; status holds moderate.

**Layer Status:**  
● Layer 0 · Compute: Compute & Network Fabric — Full-Stack Cloud Compute  
● Layer 1A · Storage: Data Storage & Governance — Database-Anchored Data Foundation  
● Layer 1B · Retrieval: Context Management & Retrieval — Database-Native Retrieval  
◑ Layer 1C · Pipelines: Data Movement & Pipelines — Database-Centric Pipelines  
◑ Layer 2A · Orchestration: Infrastructure Orchestration — OKE + GPU Superclusters  
● Layer 2B · Runtime: Application Runtime & Execution — OCI Enterprise AI Platform  
◑ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Intelligence 2C: Emerging | Infra 2C: Implicit  
● Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Strongest Application-Layer Authority  

**DAPM Profile:** Retained 0 · Delegated 3 · Ceded 24 · Absent 0

**Summary:** OCI occupies a structurally unique position in this assessment series: it is the only hyperscaler whose AI infrastructure strategy is anchored by a database franchise. AWS builds down from managed services. Google builds out from a frontier model. OCI builds up from the enterprise data layer — Oracle AI Database 26ai, Autonomous AI Database, and the Fusion Applications estate that runs 97% of the Fortune 100. Every other hyperscaler treats the database as one service among many. Oracle treats the database as the gravitational center around which AI infrastructure orbits.

---

### Palantir AIP + Foundry + Apollo
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v3.2 - Label Vocabulary Reconciliation · July 12, 2026  
Source: Palantir Architecture Center (Platforms, Ontology System, Multimodal Data Plane, Interoperability, Rubix, AIP Architecture), Apollo docs (How Apollo Works, Plans & Constraints), 'Securing Agents in Production' (Palantir blog, Jan 2026), AIPCon 9, Q1 2026 earnings (May 4, 2026), published 4+1 model v3.2 (July 12, 2026, /reconcile): 2A/2C statusLabels moved to capability vocabulary; no grades or chips changed.

**Layer Status:**  
○ Layer 0 · Compute: Compute & Network Fabric — Not Palantir's Layer (By Design)  
● Layer 1A · Storage: Data Storage & Governance — Palantir Strength — Governance Authority, Open Storage  
● Layer 1B · Retrieval: Context Management & Retrieval — Palantir Strength — Governed Retrieval  
◑ Layer 1C · Pipelines: Data Movement & Pipelines — Foundry Pipelines + Open Compute (MMDP)  
◑ Layer 2A · Orchestration: Infrastructure Orchestration — Platform-Scoped Orchestration  
● Layer 2B · Runtime: Application Runtime & Execution — Palantir Strength — Governed Agent Runtime  
● Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Closest Productized Mechanism  
● Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Palantir Strength — Where It Starts, Not Where It Ends  

**DAPM Profile:** Retained 0 · Delegated 2 · Ceded 26 · Absent 0

**Summary:** Palantir is the first vendor in this series that is not an infrastructure vendor at all, and reading its own documentation makes the inversion precise. Dell, HPE, VAST, Cisco, and the clouds build upward from silicon, storage, or a data center; Palantir builds downward from the decision. Its Architecture Center is explicit that the Ontology is designed to represent 'the complex, interconnected decisions of an enterprise, not simply the data.' Where Dell is strongest at Layer 0 and absent at Layer 2C, Palantir is structurally absent at Layer 0 and strongest at Layers 1A (governance), 2B (governed agent runtime), 2C (reasoning/orchestration), and 3 (value). It is the mirror image of every infrastructure vendor assessed so far.

---

### Qlik (Cloud Analytics + Talend Cloud + Open Lakehouse)
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.0 - Initial Assessment · July 7, 2026  
Source: help.qlik.com (Open Lakehouse architecture, Qlik MCP server, Qlik Predict, client-managed Qlik Sense), Qlik press releases (Open Lakehouse GA Sept 2025; agentic analytics GA + MCP Server Feb 2026; Qlik Connect 2026; agentic data engineering GA June 2026), Qlik Community FAQ and support articles, published 4+1 model

**Layer Status:**  
○ Layer 0 · Compute: Compute & Network Fabric — Not Qlik's Layer (By Design)  
◑ Layer 1A · Storage: Data Storage & Governance — Open Lakehouse on Your Substrate; Captive Trust Layer  
◑ Layer 1B · Retrieval: Context Management & Retrieval — Turnkey RAG, Closed Box  
● Layer 1C · Pipelines: Data Movement & Pipelines — Qlik's Heartland — CDC + Talend + Lakehouse Ingestion  
◑ Layer 2A · Orchestration: Infrastructure Orchestration — Managed Task & Cluster Orchestration; No GPU Plane  
◑ Layer 2B · Runtime: Application Runtime & Execution — Turnkey Agents & Automation; No Model Serving  
○ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Bring Your Own Reasoning Plane (MCP-First)  
● Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Qlik's Native Layer — The Analytics Value Plane  

**DAPM Profile:** Retained 0 · Delegated 1 · Ceded 19 · Absent 0

**Summary:** Qlik is a data integration and analytics software vendor that floats above Layer 0 (SaaS on AWS, and AWS-only) and is strongest at the two ends it has always owned: data movement (1C — the Attunity/Talend/Upsolver heartland) and the analytics value plane (Layer 3 — the application estate plus a GA detect-predict-act loop). The middle of the stack is uniformly moderate — storage/governance, retrieval, orchestration, and runtime are all real but product-bounded — and the reasoning plane is a gap by explicit posture. Authority sits in Qlik's opinion layer wherever Qlik ships one; the substrate never.

---

### Salesforce (Agentforce 360 + Data 360 + Customer 360)
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.0 - Initial Assessment · July 17, 2026  
Source: Salesforce Developer docs (Agentforce Trust Layer, Supported Models, Data 360 architecture and security, search index and retriever guides), MuleSoft Agent Fabric documentation, Salesforce Architect fundamentals (Data 360, MuleSoft Agent Fabric deep dive), Salesforce and Informatica press releases (Informatica acquisition close Nov 18 2025; 'Informatica from Salesforce' data-foundation announcement May 20 2026), Agentforce 360 GA (Spring '26, Feb 23 2026), Agentforce Observability GA (Feb 2026), AWS Big Data blog (zero-copy access to Iceberg from Data 360 via Glue REST catalog), Salesforce FY26 metrics (Q3/Q4 Data Cloud and Agentforce), published 4+1 model. Informatica folded into this row on the whose-paper rule (wholly owned since Nov 2025). Determinism distinction ('you can't prompt your way to deterministic output' / 'legal is not right') written at 2C as a universal finding and adopted as a 2C scoring-discipline rule (ratified Salesforce v1.0, sibling of 'routing is not reasoning'), applied uniformly rather than as a Salesforce-only downgrade.

**Layer Status:**  
○ Layer 0 · Compute: Compute & Network Fabric — Not Salesforce's Layer (By Design)  
● Layer 1A · Storage: Data Storage & Governance — Authorization Authority, Dual Capture  
● Layer 1B · Retrieval: Context Management & Retrieval — Governed Retrieval — Native Infrastructure Surface  
● Layer 1C · Pipelines: Data Movement & Pipelines — MuleSoft + Informatica — Heterogeneous Movement  
◑ Layer 2A · Orchestration: Infrastructure Orchestration — Managed Orchestration; No GPU Plane  
● Layer 2B · Runtime: Application Runtime & Execution — Atlas Runtime — Governed, Constructible, Any-Model  
◑ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Governance Without a Reasoning Mechanism  
● Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Salesforce's Native Layer — First-Party Value Plane  

**DAPM Profile:** Retained 0 · Delegated 2 · Ceded 29 · Absent 0

**Summary:** Salesforce is an enterprise application, agent, and data platform that floats above Layer 0 and is strong everywhere it has always lived: the data plane of storage and governance, retrieval, and movement, plus the agent runtime and the value plane. It moderates at the two layers it does not truly own. Infrastructure orchestration, where it manages its own workloads on rented cloud. And the reasoning plane, where it governs and enforces but does not reason. Authority sits in Salesforce's opinion layer wherever Salesforce ships one, which is nearly everywhere above the silicon.

---

### Supermicro DCBBS & AI Data Platforms
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.0 - Initial Assessment · July 11, 2026  
Source: Supermicro DCBBS documentation and solutions pages (May 2026 brochure era), Seven AI Data Platform Solutions launch (March 16, 2026, with Cloudian, DDN, Everpure, IBM, Nutanix, VAST Data, WEKA), BlueField-4 STX storage server (March 18, 2026), Vera Rubin DCBBS blueprints announcements (2026), SuperCloud Software Suite documentation (SCC v3.x license brief March 2026, SCAC product page and datasheet, SDX and SCD product documentation), Broadcom Enterprise SONiC license SKUs on Supermicro paper, AI-RAN/sovereign AI announcements (March 2, 2026, Nokia/SK Telecom/Telenor), published 4+1 model. Assessment notes: this row forced two instrument-level rulings, both from the grading review. First, the whose-paper capability rule — channel delivery credits fully on the capability axis (the GPU parallel: every OEM scores strong at Layer 0 on NVIDIA silicon; the same logic credits partner data platforms productized on the vendor's paper). Second, the retraction of the OEM-channel DAPM rule — a proprietary single-implementation platform is Ceded-to-partner through any paper; two sellers of one proprietary stack is channel substitution, not authority. Delegated survives only via open/self-hostable substrates or multi-vendor standard interfaces. The 2A strong carries a standing deployment-evidence flag: it survives on documentation; named production operators are the open fact. The initial control-row hypothesis (hardware vendor, nothing above the rack) failed its documentation test — recorded as evidence the doc-first method works.

**Layer Status:**  
● Layer 0 · Compute: Compute & Network Fabric — Supermicro Strength  
● Layer 1A · Storage: Data Storage & Governance — Partner-Delivered Strength  
● Layer 1B · Retrieval: Context Management & Retrieval — Partner-Delivered Retrieval  
● Layer 1C · Pipelines: Data Movement & Pipelines — Partner-Delivered Pipeline Engines  
● Layer 2A · Orchestration: Infrastructure Orchestration — First-Party GPU Cloud Orchestration  
◑ Layer 2B · Runtime: Application Runtime & Execution — NVIDIA Passthrough + Open Substrate  
○ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Enterprise Responsibility  
◇ Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Uncurated Partner Ecosystem  

**DAPM Profile:** Retained 5 · Delegated 7 · Ceded 12 · Absent 0

**Summary:** Supermicro grades as the most capability-dense OEM row on this instrument — strong from Layer 0 through 2A — while owning less software IP than any peer. The mechanism is the row's defining feature, and the reason for every strong grade: Supermicro's paper productizes best-of-breed partner platforms (VAST, WEKA, DDN, Cloudian, IBM, Nutanix, Everpure) as named Supermicro products with documented single-vendor support, on top of the industry's fastest NVIDIA-generation cadence, DLC-2 liquid cooling at gigawatt scale, and a DCBBS motion that delivers whole data centers as building blocks. The capability axis credits what a customer can deploy on the vendor's paper today — the same rule that scores every OEM strong at Layer 0 on NVIDIA silicon — and by that rule Supermicro's deployable menu is the widest and strongest in the on-prem market.

---

### VAST AI Operating System
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.5 - 2B Maturity-Discount Reconciliation · June 21, 2026  
Source: VAST Forward 2026, VAST AI OS white paper, analyst coverage, published 4+1 model. v1.5 (instrument reconciliation): 2B moderate→strong — AgentEngine is GA (H2 2025) and a complete, owned agent runtime; the prior moderate rested on a maturity/less-proven discount, which is not a capability axis (GA + complete owned runtime = strong, the same bar Databricks 2B cleared). Maturity may become a scored attribute as the agentic market matures.

**Layer Status:**  
◑ Layer 0 · Compute: Compute & Network Fabric — Software-Defined  
● Layer 1A · Storage: Data Storage & Governance — VAST Strength  
● Layer 1B · Retrieval: Context Management & Retrieval — VAST Strength  
● Layer 1C · Pipelines: Data Movement & Pipelines — VAST Strength  
◑ Layer 2A · Orchestration: Infrastructure Orchestration — Partial  
● Layer 2B · Runtime: Application Runtime & Execution — VAST Strength — AgentEngine (GA)  
○ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Gap — placement abstraction, not a reasoning plane  
◑ Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Focused Ecosystem  

**DAPM Profile:** Retained 0 · Delegated 7 · Ceded 29 · Absent 0

**Summary:** VAST is the most architecturally distinct vendor in this assessment series because it deliberately collapses traditionally separate infrastructure layers into a single platform. The VAST AI Operating System unifies storage (DataStore), metadata and vector database (DataBase + Catalog), global namespace (DataSpace), serverless compute (DataEngine), retrieval (InsightEngine), agent runtime (AgentEngine), governance (PolicyEngine), and model lifecycle (TuningEngine) under one authority boundary. Where Dell assembles 5–7 partner technologies to span Layers 1A through 2B, VAST provides a vertically integrated alternative with no inter-layer seams.

---

### VMware Private AI Foundation with NVIDIA
*Mapped to the 4+1 Layer AI Infrastructure Model*  
Version: v1.4 - Interface-Portability Reconciliation · June 20, 2026  
Source: VMware Explore 2025, VCF 9.0/9.1 announcements, Broadcom press releases, VCF Private AI blog series, published 4+1 model. v1.4 (instrument reconciliation): 1B Vector Database (pgvector) Ceded→Delegated (OSS, opinions lift via pg_dump); 2A vSphere Supervisor + VKS Ceded→Delegated (conformant K8s, consistent with cloud managed-K8s treatment).

**Layer Status:**  
◑ Layer 0 · Compute: Compute & Network Fabric — Hardware-Agnostic Abstraction  
◑ Layer 1A · Storage: Data Storage & Governance — Platform Storage, Not AI-Native  
◑ Layer 1B · Retrieval: Context Management & Retrieval — Foundational RAG Services  
○ Layer 1C · Pipelines: Data Movement & Pipelines — Gap  
● Layer 2A · Orchestration: Infrastructure Orchestration — VMware Heritage Strength  
◑ Layer 2B · Runtime: Application Runtime & Execution — Platform-Native + NVIDIA-Dependent  
○ Layer 2C · Reasoning: Agentic Infrastructure — The Reasoning Plane — Emerging Signals Only  
◑ Layer 3 (+1) · Applications: AI Application Layer — The Value Plane — Platform-Enabled, Not Platform-Provided  

**DAPM Profile:** Retained 1 · Delegated 9 · Ceded 18 · Absent 0

**Summary:** VMware Private AI Foundation with NVIDIA occupies a structurally unique position in this assessment series: it is neither an infrastructure OEM (Dell, HPE), a hyperscaler (AWS, Google Cloud), nor a data platform vendor (VAST). It is a virtualization and private cloud platform — the abstraction layer that sits between physical infrastructure and workloads. Broadcom’s strategic thesis is that VCF is ‘the permanent abstraction layer between AI software and physical chips,’ and the Private AI Foundation extends that thesis into AI workloads specifically.

---

## Site Navigation

| Page | URL | Description |
|---|---|---|
| Home / Vendor Grid | https://layer2c.com/ | All assessed vendors with DAPM profiles and layer status |
| Cross-Vendor Compare | https://layer2c.com/compare | Layer status matrix and DAPM heat map across all vendors |
| What Is Layer 2C? | https://layer2c.com/what-is-layer-2c | Framework explainer, 4+1 model, DAPM definitions |
| Methodology | https://layer2c.com/methodology | How assessments are scored and what they evaluate |
| System Map | https://layer2c.com/system | How the four Layer2C properties fit as one research system |
| Articul8 AI Platform Assessment | https://layer2c.com/assessment/articul8 | Mapped to the 4+1 Layer AI Infrastructure Model |
| AWS AI Infrastructure Assessment | https://layer2c.com/assessment/aws | Mapped to the 4+1 Layer AI Infrastructure Model |
| Microsoft Azure AI Infrastructure Assessment | https://layer2c.com/assessment/azure | Mapped to the 4+1 Layer AI Infrastructure Model |
| Cisco Secure AI Factory with NVIDIA Assessment | https://layer2c.com/assessment/cisco | Mapped to the 4+1 Layer AI Infrastructure Model |
| CoreWeave AI Cloud Assessment | https://layer2c.com/assessment/coreweave | The Open-Substrate Neocloud — Mapped to the 4+1 Layer AI Infrastructure Model |
| Databricks Data Intelligence Platform Assessment | https://layer2c.com/assessment/databricks | Mapped to the 4+1 Layer AI Infrastructure Model |
| Dell AI Factory with NVIDIA Assessment | https://layer2c.com/assessment/dell | Mapped to the 4+1 Layer AI Infrastructure Model |
| Google Cloud AI Infrastructure Assessment | https://layer2c.com/assessment/gcp | Mapped to the 4+1 Layer AI Infrastructure Model |
| HPE Private Cloud AI Assessment | https://layer2c.com/assessment/hpe | Mapped to the 4+1 Layer AI Infrastructure Model |
| IBM / Red Hat OpenShift AI Assessment | https://layer2c.com/assessment/ibm | Mapped to the 4+1 Layer AI Infrastructure Model |
| Intel AI Infrastructure Portfolio Assessment | https://layer2c.com/assessment/intel | Mapped to the 4+1 Layer AI Infrastructure Model |
| Kamiwaza AI Orchestration Platform Assessment | https://layer2c.com/assessment/kamiwaza | Mapped to the 4+1 Layer AI Infrastructure Model |
| Lenovo Hybrid AI Advantage with NVIDIA Assessment | https://layer2c.com/assessment/lenovo | Mapped to the 4+1 Layer AI Infrastructure Model |
| NetApp Intelligent Data Infrastructure Assessment | https://layer2c.com/assessment/netapp | Mapped to the 4+1 Layer AI Infrastructure Model |
| Nutanix Cloud Platform with Enterprise AI Assessment | https://layer2c.com/assessment/nutanix | Mapped to the 4+1 Layer AI Infrastructure Model |
| NVIDIA AI Platform Assessment | https://layer2c.com/assessment/nvidia | A Components Company Becoming a Platform Vendor — Mapped to the 4+1 Layer AI Infrastructure Model |
| Oracle Cloud Infrastructure (OCI) AI Infrastructure Assessment | https://layer2c.com/assessment/oci | Mapped to the 4+1 Layer AI Infrastructure Model |
| Palantir AIP + Foundry + Apollo Assessment | https://layer2c.com/assessment/palantir | Mapped to the 4+1 Layer AI Infrastructure Model |
| Qlik (Cloud Analytics + Talend Cloud + Open Lakehouse) Assessment | https://layer2c.com/assessment/qlik | Mapped to the 4+1 Layer AI Infrastructure Model |
| Salesforce (Agentforce 360 + Data 360 + Customer 360) Assessment | https://layer2c.com/assessment/salesforce | Mapped to the 4+1 Layer AI Infrastructure Model |
| Supermicro DCBBS & AI Data Platforms Assessment | https://layer2c.com/assessment/supermicro | Mapped to the 4+1 Layer AI Infrastructure Model |
| VAST AI Operating System Assessment | https://layer2c.com/assessment/vast | Mapped to the 4+1 Layer AI Infrastructure Model |
| VMware Private AI Foundation with NVIDIA Assessment | https://layer2c.com/assessment/vmware | Mapped to the 4+1 Layer AI Infrastructure Model |

## Sister Sites

Part of the layer2c.com family — companion tools and assessments.

| Site | URL | Description |
|---|---|---|
| Fourth Cloud | https://cloud.layer2c.com/ | Assesses operating-model readiness: on-prem control planes scored FC-0 through FC-4 |
| Labs | https://labs.layer2c.com/ | Validates where authority actually holds, through scoped real-hardware builds. Machine corpus: https://labs.layer2c.com/labs/index.json (index) and https://labs.layer2c.com/llms.txt |
| StackBuilder | https://stackbuilder.layer2c.com/ | Composes reference architectures from the assessed evidence |

## Plain-Text Mirrors

| Resource | URL | Contents |
|---|---|---|
| llms.txt (this file) | https://layer2c.com/llms.txt | Index of all assessments with summaries |
| llms-full.txt | https://layer2c.com/llms-full.txt | Complete layer-by-layer data for all vendors |
| home.md | https://layer2c.com/home.md | Plain-text homepage — vendor table, framework overview, navigation |
| experience.md | https://layer2c.com/experience.md | How the site works from a buyer's and vendor's perspective — UX, workflow, interaction model |
| Articul8 AI Platform (markdown) | https://layer2c.com/assessment/articul8.md | Full assessment in markdown |
| Articul8 AI Platform (JSON) | https://layer2c.com/assessment/articul8.json | Structured source JSON — same data, machine-readable |
| AWS AI Infrastructure (markdown) | https://layer2c.com/assessment/aws.md | Full assessment in markdown |
| AWS AI Infrastructure (JSON) | https://layer2c.com/assessment/aws.json | Structured source JSON — same data, machine-readable |
| Microsoft Azure AI Infrastructure (markdown) | https://layer2c.com/assessment/azure.md | Full assessment in markdown |
| Microsoft Azure AI Infrastructure (JSON) | https://layer2c.com/assessment/azure.json | Structured source JSON — same data, machine-readable |
| Cisco Secure AI Factory with NVIDIA (markdown) | https://layer2c.com/assessment/cisco.md | Full assessment in markdown |
| Cisco Secure AI Factory with NVIDIA (JSON) | https://layer2c.com/assessment/cisco.json | Structured source JSON — same data, machine-readable |
| CoreWeave AI Cloud (markdown) | https://layer2c.com/assessment/coreweave.md | Full assessment in markdown |
| CoreWeave AI Cloud (JSON) | https://layer2c.com/assessment/coreweave.json | Structured source JSON — same data, machine-readable |
| Databricks Data Intelligence Platform (markdown) | https://layer2c.com/assessment/databricks.md | Full assessment in markdown |
| Databricks Data Intelligence Platform (JSON) | https://layer2c.com/assessment/databricks.json | Structured source JSON — same data, machine-readable |
| Dell AI Factory with NVIDIA (markdown) | https://layer2c.com/assessment/dell.md | Full assessment in markdown |
| Dell AI Factory with NVIDIA (JSON) | https://layer2c.com/assessment/dell.json | Structured source JSON — same data, machine-readable |
| Google Cloud AI Infrastructure (markdown) | https://layer2c.com/assessment/gcp.md | Full assessment in markdown |
| Google Cloud AI Infrastructure (JSON) | https://layer2c.com/assessment/gcp.json | Structured source JSON — same data, machine-readable |
| HPE Private Cloud AI (markdown) | https://layer2c.com/assessment/hpe.md | Full assessment in markdown |
| HPE Private Cloud AI (JSON) | https://layer2c.com/assessment/hpe.json | Structured source JSON — same data, machine-readable |
| IBM / Red Hat OpenShift AI (markdown) | https://layer2c.com/assessment/ibm.md | Full assessment in markdown |
| IBM / Red Hat OpenShift AI (JSON) | https://layer2c.com/assessment/ibm.json | Structured source JSON — same data, machine-readable |
| Intel AI Infrastructure Portfolio (markdown) | https://layer2c.com/assessment/intel.md | Full assessment in markdown |
| Intel AI Infrastructure Portfolio (JSON) | https://layer2c.com/assessment/intel.json | Structured source JSON — same data, machine-readable |
| Kamiwaza AI Orchestration Platform (markdown) | https://layer2c.com/assessment/kamiwaza.md | Full assessment in markdown |
| Kamiwaza AI Orchestration Platform (JSON) | https://layer2c.com/assessment/kamiwaza.json | Structured source JSON — same data, machine-readable |
| Lenovo Hybrid AI Advantage with NVIDIA (markdown) | https://layer2c.com/assessment/lenovo.md | Full assessment in markdown |
| Lenovo Hybrid AI Advantage with NVIDIA (JSON) | https://layer2c.com/assessment/lenovo.json | Structured source JSON — same data, machine-readable |
| NetApp Intelligent Data Infrastructure (markdown) | https://layer2c.com/assessment/netapp.md | Full assessment in markdown |
| NetApp Intelligent Data Infrastructure (JSON) | https://layer2c.com/assessment/netapp.json | Structured source JSON — same data, machine-readable |
| Nutanix Cloud Platform with Enterprise AI (markdown) | https://layer2c.com/assessment/nutanix.md | Full assessment in markdown |
| Nutanix Cloud Platform with Enterprise AI (JSON) | https://layer2c.com/assessment/nutanix.json | Structured source JSON — same data, machine-readable |
| NVIDIA AI Platform (markdown) | https://layer2c.com/assessment/nvidia.md | Full assessment in markdown |
| NVIDIA AI Platform (JSON) | https://layer2c.com/assessment/nvidia.json | Structured source JSON — same data, machine-readable |
| Oracle Cloud Infrastructure (OCI) AI Infrastructure (markdown) | https://layer2c.com/assessment/oci.md | Full assessment in markdown |
| Oracle Cloud Infrastructure (OCI) AI Infrastructure (JSON) | https://layer2c.com/assessment/oci.json | Structured source JSON — same data, machine-readable |
| Palantir AIP + Foundry + Apollo (markdown) | https://layer2c.com/assessment/palantir.md | Full assessment in markdown |
| Palantir AIP + Foundry + Apollo (JSON) | https://layer2c.com/assessment/palantir.json | Structured source JSON — same data, machine-readable |
| Qlik (Cloud Analytics + Talend Cloud + Open Lakehouse) (markdown) | https://layer2c.com/assessment/qlik.md | Full assessment in markdown |
| Qlik (Cloud Analytics + Talend Cloud + Open Lakehouse) (JSON) | https://layer2c.com/assessment/qlik.json | Structured source JSON — same data, machine-readable |
| Salesforce (Agentforce 360 + Data 360 + Customer 360) (markdown) | https://layer2c.com/assessment/salesforce.md | Full assessment in markdown |
| Salesforce (Agentforce 360 + Data 360 + Customer 360) (JSON) | https://layer2c.com/assessment/salesforce.json | Structured source JSON — same data, machine-readable |
| Supermicro DCBBS & AI Data Platforms (markdown) | https://layer2c.com/assessment/supermicro.md | Full assessment in markdown |
| Supermicro DCBBS & AI Data Platforms (JSON) | https://layer2c.com/assessment/supermicro.json | Structured source JSON — same data, machine-readable |
| VAST AI Operating System (markdown) | https://layer2c.com/assessment/vast.md | Full assessment in markdown |
| VAST AI Operating System (JSON) | https://layer2c.com/assessment/vast.json | Structured source JSON — same data, machine-readable |
| VMware Private AI Foundation with NVIDIA (markdown) | https://layer2c.com/assessment/vmware.md | Full assessment in markdown |
| VMware Private AI Foundation with NVIDIA (JSON) | https://layer2c.com/assessment/vmware.json | Structured source JSON — same data, machine-readable |