Use Layer2C to Pressure-Test AI Infrastructure Claims
Layer2C helps enterprise technology leaders evaluate where AI infrastructure vendors actually operate — across compute, data, orchestration, runtime, reasoning, and applications — and where the enterprise still owns governance, cost, evidence, and accountability.
This site is for CIOs, CTOs, platform leaders, enterprise architects, and procurement decision makers who need to understand what they are actually buying before they buy it.
What This Helps You Do
Use Layer2C to:
- Compare vendors beyond "AI platform" marketing
- Identify which layers a vendor actually controls versus delegates or cedes
- Read each component's portability (Retained, Delegated, or Ceded) and each layer's decision authority (who decides, whether you can see it, whether you can override it)
- Find governance gaps before production — not after
- Build sharper RFP and briefing questions grounded in architecture
- See where vendor claims depend on partners, roadmaps, or borrowed judgment
- Map operating model implications before a contract is signed
The Buyer Problem
Every vendor claims to be the AI platform. But enterprise buyers do not buy platforms in the abstract. They inherit operating models, governance boundaries, cost exposure, audit responsibilities, and architectural dependencies.
The question most RFPs fail to ask is not "what does this platform do?" It is:
"If this system needs to change, be audited, be constrained, or be overridden — who has the authority to do it?"
That question is what the Decision Authority Placement Model (DAPM) answers, through two readings of one instrument. The first is portability, read per component: Retained (I possess the capability and can operate it independently of this provider), Delegated (someone else provides it, and I can substitute that provider without reconstructing my accumulated opinions), or Ceded (changing providers requires reconstructing those opinions). The second is decision authority, read per layer: who makes the runtime tradeoff (the enterprise, the vendor, the model, or code the enterprise controls), whether the enterprise can see it, whether the enterprise can override it, and the direction that follows (Retained, Delegated, Ceded, or Absent). Neither reading is the capability grade.
A Ceded component can be excellent. A Retained component can be inferior. The portability reading tells you what leaves with you; the decision-authority reading tells you what the marketing deck does not: when your organization needs to change, audit, or override this capability at runtime, can it?
How to Use the Assessments
Start with the comparison page. Get the layer status matrix, the portability profiles, and the per-layer decision-authority readings for all vendors side by side before reading any individual assessment.
Review the vendor's portability profile (the Retained-to-Ceded ratio across components) for what you could take elsewhere, then the decision-authority reading at each layer for who decides while you stay. A Ceded authority reading at Layer 2C — the reasoning plane — is the most consequential governance risk: the vendor or its model decides and you cannot override it.
Read the full assessment for your shortlisted vendors. Each layer includes gap analysis, borrowed judgment assessment, and working notes.
Look specifically for borrowed judgment — where a vendor's capability claim depends on a partner's roadmap rather than their own. This is where platform stories overreach.
Convert gap findings into briefing or RFP questions. Layer2C gives you the architectural basis for questions vendors are rarely asked. Use the 4+1 AI Platform RFP Framework to translate Layer2C findings directly into procurement language.
The Layer 2C Governance Test
The most consequential layer for enterprise governance is Layer 2C — the Agentic Infrastructure layer, also called the Reasoning Plane. This is where AI agents and models are orchestrated, constrained, monitored, and held accountable.
A vendor passes the Layer 2C test if its infrastructure can make policy-driven placement decisions — not just route requests, but reason about which model, agent, or resource should handle a task given current policy, cost constraints, compliance requirements, and available evidence.
Most vendors today have routing at Layer 2C but not reasoning. Routing is load balancing. Reasoning is governance. If the vendor you are evaluating cannot demonstrate policy-driven placement with evidence capture and audit trails, you are buying a capable system that is not governable at the infrastructure level.