{
  "id": "dell",
  "name": "Dell AI Factory with NVIDIA",
  "subtitle": "Mapped to the 4+1 Layer AI Infrastructure Model",
  "version": "v2.6 - Codified-Criteria Audit & Watch-List Roll",
  "date": "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.",
  "status": "complete",
  "summary": {
    "title": "Summary Finding",
    "paragraphs": [
      "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.",
      "Dell's capture is decoupled and therefore mostly invisible. The data and table formats are genuinely open: Iceberg, Trino, S3-interface object storage. Schemas lift and catalogs swap. That openness is true and reassuring, and it's the layer Dell's own teams point to when they push back on authority scores. The captive layers sit above the data: the MetadataIQ catalog structure, Data Orchestration Engine pipeline logic, PowerRack integration, and Spectrum-X fabric opinions. The buyer feels portable because the bytes are portable. The opinions aren't.",
      "Dell's owned capability above the rack is thin by design: validated ISV blueprints and human services at Layer 2B, chassis-level management at Layer 2A. GPU scheduling judgment is NVIDIA's regardless of whose paper the license rides on. The deskside agentic runtime is pre-GA and watch-listed, not scored.",
      "The reasoning-plane gap is no longer just this instrument's finding; it's Dell's stated strategy. In a July 2026 briefing, Dell confirmed both halves of the boundary: the telemetry exists from Layer 0 up, and the decision layer is deliberately left to the ecosystem. 'I can give you the telemetry, but the ultimate decision comes down to somebody making the decision.' Security is not governance. Security constrains who can access the platform. Governance constrains what the platform does. The Dell AI Factory has security. It does not yet have governance at the infrastructure level.",
      "That does not make the AI Factory weak. It exposes where the next control-plane battle will be fought."
    ]
  },
  "layers": [
    {
      "id": "layer0",
      "label": "Layer 0",
      "shortName": "Compute",
      "title": "Compute & Network Fabric",
      "purpose": "Raw compute, networking, and acceleration fabric",
      "status": "strong",
      "statusLabel": "Dell Strength",
      "nvidia": [
        {
          "component": "GPU/Accelerator Silicon",
          "detail": "Blackwell, Vera Rubin — the compute engines Dell builds around."
        },
        {
          "component": "NVLink / NVSwitch",
          "detail": "Intra-node high-bandwidth interconnect defining memory and compute topology."
        },
        {
          "component": "Spectrum Ethernet Silicon",
          "detail": "Dell brands and rack-integrates NVIDIA switching silicon."
        }
      ],
      "gap": "Dell retains platform packaging authority at Layer 0, but the accelerator fabric and high-performance AI networking roadmap are structurally tied to NVIDIA. Dell provides genuine engineering differentiators in thermal design, rack integration, and mechanical authority. The networking silicon dependency is worth tracking.",
      "borrowedJudgment": "Structural co-dependency: Dell retains mechanical authority, NVIDIA retains silicon authority. If NVIDIA changes the Spectrum roadmap, Dell's PowerRack networking story changes with it. From the buyer's seat, the ratings are unaffected by which vendor holds the captive layer: PowerRack and PowerSwitch opinions can't leave regardless of whose silicon sits under the Dell brand.",
      "notes": "AMD alternative exists under 'Dell AI Platform with AMD' (separate SKUs). MI350P PCIe, air-cooled, ROCm/vLLM stack. Different Layer 2B story entirely. Watch-list (ISC, June 22, 2026, not scored): PowerEdge XE8812 — Vera Rubin NVL4, up to 144 GPUs per rack, fanless 100% direct liquid cooling, ORv3-style rack, 300kW+, Quantum-X800 InfiniBand. 'Globally available early next year' (early 2027). Scores as a component at GA.",
      "components": [
        {
          "component": "PowerRack",
          "detail": "Turnkey rack-scale: compute, networking, storage integrated with thermal/power management as one unit. Integrated-system rule: the buyer's rack-integration opinions cannot be lifted to another vendor as deployed.",
          "dapm": "Ceded"
        },
        {
          "component": "PowerEdge XE9812 (Vera Rubin NVL72)",
          "detail": "10x lower cost-per-token than Blackwell for agentic inference. Commodity-substitutable server: NVL72 systems ship from multiple OEMs, so workloads move without rebuilding.",
          "dapm": "Retained"
        },
        {
          "component": "Pro Max GB300 (Deskside)",
          "detail": "120B–1T parameter models. MaxCool liquid cooling. ~3 month break-even vs cloud.",
          "dapm": "Retained"
        },
        {
          "component": "PowerSwitch SN6000-series",
          "detail": "NVIDIA Spectrum-6 Ethernet. 800+ Tb/sec east-west. Networking opinions are embedded in the Dell/Spectrum-X stack with no abstraction layer offered that would make them portable to alternative switching infrastructure such as Juniper or Aruba.",
          "dapm": "Ceded"
        },
        {
          "component": "PowerCool CDU C7000",
          "detail": "First rack-mount CDU for Vera Rubin NVL72 density. 4U, 19\", up to 40°C facility water. Physical plant accumulates no portable opinions — no lock-in surface.",
          "dapm": "Retained"
        }
      ]
    },
    {
      "id": "layer1a",
      "label": "Layer 1A",
      "shortName": "Storage",
      "title": "Data Storage & Governance",
      "purpose": "Durable, governed data foundation — the Governance Catalog that Layer 2C queries",
      "status": "strong",
      "statusLabel": "Dell Strength",
      "nvidia": [
        {
          "component": "cuVS (Vector Search)",
          "detail": "GPU-accelerated vector indexing (12x claimed). The GPU-accelerated path is not yet GA on Dell paper (watch-listed at 1B) — dependency finding, not shipping capability."
        },
        {
          "component": "CX-8/CX-9 SuperNICs",
          "detail": "Storage-side RDMA for GPU-direct access."
        },
        {
          "component": "NeMo Retriever Connector",
          "detail": "PowerScale integration for GPU-accelerated retrieval."
        }
      ],
      "gap": "Dell's strongest layer after Layer 0. Trust3 AI provides agentic-AI-aware governance. The Exascale 3-in-1 architecture signals where the platform is heading on data locality, but it is watch-listed pending GA confirmation and not scored. The strategic question: is MetadataIQ metadata rich enough to drive Layer 2C placement decisions? Dell's marketing says yes. The proof is whether any Layer 2C can query it programmatically. The July 2026 briefing confirmed the telemetry and access-control surfaces exist; the reasoning consumer does not.",
      "borrowedJudgment": "Low. Dell owns the storage platforms, metadata layer, and cyber resilience stack. NVIDIA provides acceleration, not governance logic. From the buyer's seat, the captive value is MetadataIQ: catalog structure and indexing opinions cannot leave the Dell platform. ObjectScale's S3 interface keeps object opinions portable to any S3 platform (Delegated — a proprietary implementation behind a multi-vendor standard, not an open substrate the enterprise operates); Trust3's governance policies are the partner's captive surface — Ceded to Trust3, not to Dell.",
      "notes": "Data Analytics Engine Agentic Layer + MCP Server (Feb 2026) blur 1A/1B boundary — search, analytics, and orchestration surfaced as a single queryable service. Briefing (July 2026): AIDP access control is agent-aware — a user, an agent, or an agent acting on behalf of a user, with governance on where data lives and is processed through the pipeline; recorded as confirmation of this cell's framing. The briefing also named agent memory (store/retrieve of distilled agent memory) — not documented as GA anywhere the instrument can cite; unscored, fact question pending in Dell's written feedback. Watch-list (announced March 16, 2026; rolled July 12, 2026, not scored): Dell Exascale Storage (3-in-1: PowerScale + ObjectScale + Lightning FS on one platform, 10+ PB/rack, 6 TB/s reads) — current Dell materials still say 'available 2H 2026'; not doc-confirmed. Lightning FS shipped April 2026. New at the May 2026 announcements: Exascale expands to 4-in-1 with PowerFlex block (unified PowerRack architecture), itself dated 1H 2027. Scores when Dell documentation confirms GA.",
      "components": [
        {
          "component": "PowerScale (File Engine)",
          "detail": "MetadataIQ integration. NeMo Retriever connector. pNFS 25% throughput improvement. PowerScale storage opinions (configs, tiering policies, performance tuning) are captive to the Dell platform — the enterprise cannot lift them to Alletra or VAST without rebuilding.",
          "dapm": "Ceded"
        },
        {
          "component": "ObjectScale (Object Storage)",
          "detail": "S3-compatible. S3 over RDMA. NVIDIA Omniverse integration. Palantir Ontology deploys here. S3-compatible interface; object-storage opinions (buckets, lifecycle, policies) lift to any S3 platform. ObjectScale is a proprietary implementation behind the multi-vendor S3 standard — the consumed interface keeps object opinions portable, so Delegated (not an open substrate the enterprise operates, which would be Retained). The captive surface is MetadataIQ, not ObjectScale itself.",
          "dapm": "Delegated"
        },
        {
          "component": "MetadataIQ",
          "detail": "Indexes billions of files across PowerScale/ObjectScale. Foundation of the governance catalog. Metadata indexing opinions and catalog structure are captive to Dell.",
          "dapm": "Ceded"
        },
        {
          "component": "Trust3 AI Integration",
          "detail": "Storage-layer governance: sensitive data discovery, 'write once, apply everywhere' policy, AI auditing. EU AI Act/GDPR/HIPAA. Proprietary single-vendor governance platform on Dell paper — the 'write once, apply everywhere' policies are authored in Trust3's engine and do not lift to another governance ISV without rebuilding. Channel-substitution rule: Ceded to the chosen partner through any paper.",
          "dapm": "Ceded"
        },
        {
          "component": "Cyber Resilience (Built-in)",
          "detail": "Zero Trust, encryption, RBAC, immutable snapshots, XDR, data masking, air-gapped backup. Security implementation captive to Dell storage platforms — policies and configurations do not lift to another vendor's storage.",
          "dapm": "Ceded"
        }
      ]
    },
    {
      "id": "layer1b",
      "label": "Layer 1B",
      "shortName": "Retrieval",
      "title": "Context Management & Retrieval",
      "purpose": "Low-latency retrieval for RAG — vector/hybrid search, context windows",
      "status": "moderate",
      "statusLabel": "Elastic-Powered Retrieval",
      "nvidia": [
        {
          "component": "NVIDIA cuVS",
          "detail": "GPU-accelerated hybrid search (12x indexing claimed). Upstream Elasticsearch 9.4 took cuVS to GA April 2026; not yet GA on Dell paper — watch-listed, dependency finding."
        },
        {
          "component": "NVIDIA STX Architecture",
          "detail": "BlueField-4 + ConnectX-9 + Spectrum-X + DOCA. Storage-side acceleration — available to ALL storage vendors."
        },
        {
          "component": "NeMo Retriever",
          "detail": "PowerScale connector for GPU-accelerated retrieval."
        }
      ],
      "gap": "Three-party dependency: Dell (storage + metadata), Elastic (search intelligence), NVIDIA (acceleration). STX is non-differentiating — every storage vendor has it. Dell's differentiation is MetadataIQ integration and the Elastic partnership, not NVIDIA acceleration.\n\nFrontier check (capability rule 6, July 2026): the 1B frontier is now integrated AI-retrieval platforms delivered on vendor paper — VAST InsightEngine natively and through the Cisco and Supermicro channels (strong). Dell's DSE is a general-purpose search engine (rule 4 favors its generality — Elasticsearch runs retrieval workloads Dell never anticipated) that the customer assembles into RAG, with the GPU-accelerated path still unconfirmed on Dell paper. Real, deployable, general, but below the frontier and gated — moderate holds on rules 5 and 6.",
      "borrowedJudgment": "Moderate, distributed across two partners. Search intelligence is Elastic's. Acceleration is NVIDIA's. Dell's durable value is the data substrate — if you swap search engines, PowerScale data doesn't move. From the buyer's seat the retrieval opinions themselves (Elasticsearch indices, queries, pipelines) lift to any Elastic deployment, which is what keeps the layer Delegated rather than Ceded.",
      "notes": "No retrieval quality observability (recall@k, latency percentiles) that a Layer 2C could use for placement decisions — the July 2026 briefing's telemetry discussion was token/usage metrics, not retrieval quality. Watch-list (rolled July 12, 2026, flag sharpened — not scored): GPU-accelerated vector indexing for the Data Search Engine — Dell's own materials dated it 'available 1H 2026'; 1H 2026 has ended, and the Q2 2026 AI Data Platform administrators guide (April 13, 2026) does not confirm it. Upstream Elasticsearch cuVS went GA April 2026, but upstream GA never moves an OEM cell. This is now a slipped date, not a pending one — the top fact question for the next Dell briefing; scores when Dell docs confirm. Briefing (July 2026): knowledge graphs, graph databases, and unified streaming ingest named as AIDP capabilities — none documented GA; fact questions pending written feedback. Placement note: the instrument scores retrieval (DSE) at 1B and movement (DOE/DAE) at 1C; Dell's AIDP framing bundles them. Vendor-feedback posture: portability claims on pre-GA features are untestable and carry no DAPM weight — written feedback should arrive with GA documentation.",
      "components": [
        {
          "component": "Dell Data Search Engine (Elastic)",
          "detail": "Elasticsearch 9.4. Hybrid keyword+vector search. MetadataIQ integration. LangChain support. Available now on Dell paper; the GPU-accelerated path is watch-listed pending Dell doc confirmation. Elasticsearch opinions (indices, queries, pipelines) lift to any Elastic deployment.",
          "dapm": "Delegated"
        },
        {
          "component": "Incremental Indexing",
          "detail": "Only updated files re-indexed. Keeps retrieval synchronized with governance catalog.",
          "dapm": "Delegated"
        },
        {
          "component": "Analytics Engine Agentic Layer + MCP Server",
          "detail": "Unifies vector stores across Iceberg, Data Search Engine, PostgreSQL+PGVector. Agent-queryable through the open MCP interface.",
          "dapm": "Delegated"
        }
      ]
    },
    {
      "id": "layer1c",
      "label": "Layer 1C",
      "shortName": "Pipelines",
      "title": "Data Movement & Pipelines",
      "purpose": "Move/transform data — ETL/ELT, lineage, cost-aware movement, KV cache tiering",
      "status": "moderate",
      "statusLabel": "Dell + Dataloop",
      "nvidia": [
        {
          "component": "NVIDIA CMX",
          "detail": "BlueField-4 powered context memory tier (G3.5). Pre-GA — watch-listed here and on the NVIDIA row; dependency finding, not shipping capability."
        },
        {
          "component": "NVIDIA STX Reference Architecture",
          "detail": "Storage-side infrastructure reference. Non-differentiating for Dell."
        },
        {
          "component": "Blueprints, NIMs, AI-Q Blueprint",
          "detail": "Pre-built pipeline components through the Marketplace."
        }
      ],
      "gap": "Dell's most significant strategic software move. Dataloop gives Dell proprietary orchestration logic — its first owned software asset in the data lifecycle. From the buyer's seat that ownership reads as decoupled capture: the data and table formats are open (Iceberg, Trino), so schemas lift and engines swap, while the pipeline opinions built in the no-code tooling are captive to Dell. The July 2026 briefing pushback made the instrument's case: open formats prove data portability, and data portability is the decoy — it says nothing about where orchestration authority accumulates.",
      "borrowedJudgment": "From the buyer's seat: the enterprise inherits Dell's orchestration opinions outright at the engine (Ceded, first-party — Dell borrows little from partners there). Starburst-layer analytics judgment is swappable (Delegated). KV-cache judgment moved to the watch-list with the capability.",
      "notes": "NAND Research flagged maturity concern: young acquisition as enterprise orchestration engine vs. established Databricks/Snowflake. HyperFRAME: only 14% of orgs have AI-ready data architecture. Watch-list (announced GTC, March 2026; checked July 7, 2026, not scored): KV cache offload to PowerScale/ObjectScale/Lightning FS via NVIDIA CMX — 19x TTFT and 5.3x QPS are demo claims; CMX is pre-GA (watch-listed on the NVIDIA row) and Dell's language is staged availability 'throughout the year.' Scores when Dell docs confirm; the 'Context Moves to Storage' framing travels with it. Briefing (July 2026): unified streaming ingest named as an AIDP capability — not documented GA; fact question pending.",
      "components": [
        {
          "component": "Data Orchestration Engine (Dataloop)",
          "detail": "No-code/low-code AI data lifecycle. Dell's most meaningful software acquisition (~$120M, Dec 2025). GA confirmed: deployment documentation on Dell InfoHub and an orderable product page (verified July 2026). Proprietary pipeline orchestration — pipeline definitions built in the engine are captive to Dell.",
          "dapm": "Ceded"
        },
        {
          "component": "Orchestration Engine Marketplace",
          "detail": "200+ models, NVIDIA NIMs, Blueprints, AI-Q templates. Substitutable catalog content.",
          "dapm": "Delegated"
        },
        {
          "component": "Data Analytics Engine (Starburst)",
          "detail": "GPU-accelerated SQL. Agentic Layer + MCP Server for agent access. Trino/Iceberg substrate: schemas and materialized views lift to another engine, catalogs swap — the briefing's own portability argument is the Delegated rationale.",
          "dapm": "Delegated"
        }
      ]
    },
    {
      "id": "layer2a",
      "label": "Layer 2A",
      "shortName": "Orchestration",
      "title": "Infrastructure Orchestration",
      "purpose": "GPU scheduling, quotas, RBAC, fair-share scheduling, utilization optimization",
      "status": "moderate",
      "statusLabel": "Rack-Level Management",
      "nvidia": [
        {
          "component": "GPU Operator + Network Operator + NIM Operator",
          "detail": "Three of four K8s operators in the reference architecture are NVIDIA's."
        },
        {
          "component": "NVIDIA Run:ai",
          "detail": "GPU scheduling, quotas, fair-share. THIS IS the Layer 2A function. NVIDIA-acquired."
        },
        {
          "component": "NVIDIA AI Enterprise",
          "detail": "Commercial platform wrapping the full GPU orchestration and management stack."
        }
      ],
      "gap": "Dell manages the rack. NVIDIA manages the GPU-aware substrate. That distinction matters because AI Factory differentiation depends less on whether the rack can be deployed and more on how scarce accelerated capacity is scheduled, partitioned, licensed, and governed at runtime. ClearML provides floating NVAIE license management — three authorities for one optimization function.",
      "borrowedJudgment": "High. GPU-aware orchestration primitives are NVIDIA-controlled. Dell's authority is limited to physical chassis management (Layer 0), storage provisioning (Layer 1A), and deployment automation (Day 0/1). No alternative GPU scheduler exists within the Dell AI Factory. The July 2026 briefing confirmed the posture: Dell positions everything above the rack as ecosystem, not owned capability.",
      "notes": "ClearML is the most interesting independent Layer 2A play. If Dell wanted proprietary 2A capability, acquiring or deep-partnering ClearML would be the most direct path. Pending (July 2026, not scored): Dell Automation Platform / private cloud briefing — the lifecycle-automation story (including the Nutanix-on-PowerStore private cloud landing July 2026) has not been briefed in over a year and may bear on this cell. Fact questions for that briefing: does the automation platform do anything GPU-aware itself (scheduling, partitioning, quota) or stop at deployment automation; who operates it day-2; can a customer run it without Dell services.",
      "components": [
        {
          "component": "Integrated Rack Controller",
          "detail": "Physical rack management — power, thermal, firmware, device inventory. Operates below Layer 2A. The buyer's rack-management opinions (power/thermal/firmware baselines) are captive to Dell PowerRack.",
          "dapm": "Ceded"
        },
        {
          "component": "OpenManage Enterprise",
          "detail": "Infrastructure lifecycle management. Manages the chassis, not GPU workloads. Fleet templates, policies, and baselines do not lift to another OEM's management plane.",
          "dapm": "Ceded"
        },
        {
          "component": "Dell CSI Operator",
          "detail": "Dell's one K8s operator — storage provisioning, not compute orchestration. The consumed interface is CSI/Kubernetes, a genuine multi-vendor standard: provisioning opinions live in Kubernetes-standard objects (StorageClasses, PVCs) and survive a swap to another vendor's CSI driver without rebuilding the layer.",
          "dapm": "Delegated"
        }
      ]
    },
    {
      "id": "layer2b",
      "label": "Layer 2B",
      "shortName": "Runtime",
      "title": "Application Runtime & Execution",
      "purpose": "Model serving, agent execution, inference APIs, distributed inference",
      "status": "moderate",
      "statusLabel": "Blueprints + Services",
      "nvidia": [
        {
          "component": "NemoClaw (OpenClaw Stack)",
          "detail": "Open-source agent runtime (Apache 2.0). Alpha — not GA, watch-listed. Jensen: 'the operating system for personal AI.'"
        },
        {
          "component": "OpenShell",
          "detail": "Sandboxed agent runtime with security/privacy controls. Spans deskside to data center. Alpha — not GA, watch-listed."
        },
        {
          "component": "NeMo Guardrails",
          "detail": "Runtime safety boundaries — what agents are NOT allowed to do. Constraint enforcement, not placement."
        },
        {
          "component": "Dynamo",
          "detail": "Distributed inference framework. KV-aware routing to cache-warm nodes. Closest thing to a placement decision in the stack — but single-variable optimization."
        },
        {
          "component": "NIMs + AI Enterprise",
          "detail": "Containerized model serving + commercial platform."
        }
      ],
      "gap": "What ships on Dell paper at 2B is exactly what a customer can buy and keep or swap today: validated ISV agent platforms delivered as Dell blueprints, and Dell's human expertise to deploy them. Dell owns no runtime software — model serving, agent execution, guardrails, and distributed inference are NVIDIA or ISV capabilities, carried in the dependency column. The NVIDIA deskside agent runtime (NemoClaw/OpenShell) is alpha and watch-listed, consistent with its treatment on the NVIDIA row. Dynamo's KV-aware routing remains the closest thing to placement reasoning in the stack — single-variable cache-locality optimization, not multi-variable policy.",
      "borrowedJudgment": "Total for the runtime the enterprise actually consumes: the NVIDIA path arrives with NVIDIA's judgment end to end — closed NIM serving decisions the enterprise can't inspect, Dynamo routing behavior, guardrail defaults. That judgment is inherited through the dependency column, not through a scored Dell component. Dell's owned contribution is curation and services; the blueprint menu keeps pre-purchase choice open (deployed platforms capture per-choice, to the ISV rather than to Dell), and Accelerator Services expertise transfers to the customer.",
      "notes": "Jensen's 'OS for personal AI' is a Layer 2B claim. An OS manages execution. A control plane manages placement and policy. Watch-list (checked July 7, 2026, not scored): Deskside Agentic AI (Pro Max workstations + NVIDIA NemoClaw/OpenShell + Dell Services) — the runtime is alpha (Apache 2.0), watch-listed on the NVIDIA row; scores when GA on Dell paper. Likely lands Delegated at GA (open substrate, self-hostable) — noted, not pre-scored. The deskside hardware is scored at Layer 0 (Pro Max GB300, Retained); the services are scored here (Retained). Dell's written feedback on the 2B ratings is pending (July 2026 briefing).",
      "components": [
        {
          "component": "Agentic AI Platform (Blueprints)",
          "detail": "Cohere North, DataRobot, ClearML blueprints. Dell provides hardware substrate and services. Menu-altitude Delegated: the choice among validated ISV platforms is real before purchase. Once deployed, each chosen platform captures per its own terms — a production Cohere North estate's orchestration opinions are Ceded to Cohere through any paper, per the channel-substitution rule. Dell holds the menu, not the capture.",
          "dapm": "Delegated"
        },
        {
          "component": "Accelerator Services for Agentic AI",
          "detail": "Dell's human-delivered value: strategy, deployment, optimization. Services, not software — expertise transfers to the customer, no captive opinion layer.",
          "dapm": "Retained"
        }
      ]
    },
    {
      "id": "layer2c",
      "label": "Layer 2C",
      "shortName": "Reasoning",
      "title": "Agentic Infrastructure — The Reasoning Plane",
      "purpose": "Policy-driven placement and resource coordination — the Autonomy Layer",
      "status": "gap",
      "statusLabel": "Enterprise Responsibility",
      "nvidia": [
        {
          "component": "AI-Q 2.0 Reference Architecture",
          "detail": "Multi-agent workflow scaffolding. Does NOT make placement decisions."
        },
        {
          "component": "OpenShell Governance",
          "detail": "Runtime security sandboxing. Layer 2B constraint enforcement, not 2C placement reasoning. Alpha — not GA."
        },
        {
          "component": "Dynamo KV-Aware Routing",
          "detail": "Performance-aware routing (single variable). Not multi-variable policy optimization."
        }
      ],
      "gap": "The 4+1 model defines Layer 2C as a required function of AI infrastructure — policy-driven decisions about where compute runs relative to data, which model serves which request, and how cost/compliance/latency are arbitrated in real time. Dell does not provide this function. The enterprise retains responsibility for it.\n\nApplying the 'Routing Is Not Reasoning' test: AI-Q 2.0 = workflow scaffolding. OpenShell/NeMo Guardrails = constraint enforcement. Dynamo = performance routing. None provides multi-variable policy-driven placement.\n\nThe July 2026 briefing confirmed the gap in Dell's own words, twice. First, the telemetry-versus-decision boundary: Dell has telemetry from Layer 0 'all the way to 2B or even 2C,' token metrics per query, tools and guardrails — 'but the ultimate decision of what is economical or not comes down to somebody making the decision. I can give you the telemetry.' Dell provides the inputs to a reasoning plane and explicitly disclaims the decision layer. Second, the strategy: 2C and above is a deliberate ecosystem play — 'we designed the ecosystem program for 2C and 3 to give the flexibility and not try to be the winner of all, because we don't know who's going to win those layers.' The gap is a decision, not an omission. For the buyer that matters: bringing your own 2C (Kamiwaza, ClearML, potentially Palantir Ontology) collides with no Dell roadmap.\n\nThe enterprise must build custom 2C logic (6-12 months), bring a partner, or operate without it. Most will choose option 3 — the gap isn't visible until production agentic workloads expose it.\n\nDell + Intel 'actively addressing' an AI-factory control plane (SiliconANGLE, May 2026) remains security/governance framing with no product announced — still not scoreable.",
      "borrowedJudgment": "There is no judgment to borrow — the enterprise retains full responsibility for this function. That responsibility is implicit: most enterprises operating Dell AI Factory infrastructure do not yet recognize Layer 2C as a distinct function they need to provide.",
      "notes": "Dave Vellante (theCUBE): 'The AI factory requires a new control plane — one that governs data, models and agents in real time.' That control plane is Layer 2C. Briefing (July 2026), vendor position recorded: 2C can't be productized because the intelligence is subjective — 'I can give you the tools, but I can't create the intelligence for you.' That argues the gap is universal, not that Dell fills it; it moves no cell. Scope clarification from the same exchange: the instrument rates infrastructure 2C (policy-driven placement — which model, which region, which cost/compliance tier), not domain reasoning; the GDPR-placement example is deterministic given telemetry Dell confirms it has. The capability spans 1B/1C (data boundaries) and 2C (agent/model placement) — confirmed as the instrument's split.",
      "components": []
    },
    {
      "id": "layer3",
      "label": "Layer 3 (+1)",
      "shortName": "Applications",
      "title": "AI Application Layer — The Value Plane",
      "purpose": "AI-powered business capabilities — business logic, workflow automation",
      "status": "partner",
      "statusLabel": "Partner Ecosystem",
      "nvidia": [
        {
          "component": "NemoClaw / OpenClaw Runtime",
          "detail": "Execution surface for Layer 3 applications. NVIDIA provides substrate; ISVs provide business logic. Alpha — not GA, watch-listed at 2B."
        }
      ],
      "gap": "One of the strongest on-prem AI ecosystem stories in market. Each partner maps to a coherent use case. But each brings its own governance domain — Palantir Ontology governs within Palantir's domain, ServiceNow Otto within ServiceNow's. Nobody governs ACROSS domains on shared infrastructure. Security protects the platform from threats. Governance constrains what the platform does. Both are necessary. Only security is present.",
      "borrowedJudgment": "Distributed across partners, which is architecturally correct at Layer 3. The structural problem: no cross-domain infrastructure judgment (Layer 2C) constrains all agents regardless of which ISV built them.",
      "notes": "5,000+ AI Factory customers (Dell, May 18, 2026 release; up from 3,000 at GTC). As they move to production agentic workloads, the multi-agent governance problem becomes visible. More ISV partners = more independent agent populations = more urgent need for Layer 2C — now also Dell's stated design ('not try to be the winner of all,' July 2026 briefing).",
      "components": [
        {
          "component": "Dell AI Ecosystem Program",
          "detail": "Structured ISV validation path. Partners: Google, Hugging Face, OpenAI, Palantir, Reflection, ServiceNow, SpaceXAI. Substitutable partners on Dell paper.",
          "dapm": "Delegated"
        },
        {
          "component": "Dell Enterprise Hub (Hugging Face)",
          "detail": "Curated open-weight models on PowerEdge. DeepSeek, GLM, Kimi, Gemma, Nemotron, Mistral, Arcee. Model choices and fine-tunes are portable — open-weight substrate.",
          "dapm": "Delegated"
        },
        {
          "component": "Security Stack",
          "detail": "CrowdStrike + Fortanix + F5 + Intel confidential computing. Infrastructure security, not agent governance. Substitutable security ISVs — distinct from the Ceded cyber-resilience implementation built into Dell storage at 1A.",
          "dapm": "Delegated"
        }
      ]
    }
  ]
}