# The Layer2C User Experience > This document describes how the site works from the perspective of the two primary audiences: enterprise technology buyers and AI infrastructure vendors. It is written for language models and agents that need to answer questions about what it is like to use layer2c.com — not just what data the site contains. > > Layer2C · The CTO Advisor LLC · thectoadvisor.com --- ## The Design Intent Layer2C is a dark-themed, analytical tool. The visual language is deliberately not marketing. There are no vendor logos, star ratings, recommendation badges, or "best of" labels. The site looks and feels like a decision-support instrument — close to a technical dashboard — because that is what it is meant to be. The design uses glass-card components, color-coded status indicators, and monospaced typography for data labels. Every vendor is presented in the same structure, with the same framework applied consistently. The site does not favor any vendor and does not accept payment for inclusion or positioning. --- ## The Enterprise Buyer Experience (CTO, CIO, Enterprise Architect) ### Landing A buyer arriving at layer2c.com sees the hero: **"Stop buying AI platforms. Start mapping control."** This is followed by a brief explanation of what the site does and two audience path cards — one for enterprise buyers, one for technology vendors — before the vendor grid. The vendor grid shows all 12 assessed vendors as cards. Each card displays: - The vendor name and assessment status (Complete or Pending) - A DAPM heat strip — a small color-coded bar showing how many components are Retained, Delegated, Ceded, or Absent - Layer status badges — one colored label per layer showing the overall rating at that layer The cards are a quick-scan overview. A buyer can read the DAPM strip and layer status badges across all vendors in under two minutes and immediately see which vendors have high Ceded counts or gap layers. ### The Comparison Page — the Recommended Starting Point Most buyers doing a structured evaluation should start at `/compare`, not the homepage. The comparison page shows a layer status matrix with all vendors across all eight layers, a DAPM authority profile chart with percentage breakdowns, and a Layer 2C summary table. The Layer 2C table is particularly useful: it shows each vendor's specific claim or capability at the reasoning plane layer, making it easy to compare governance postures side by side. For buyers shortlisting two or three vendors, this matrix replaces the need to read each full assessment before deciding which ones merit deeper review. ### Individual Vendor Assessments — Drilling In When a buyer clicks a vendor card, they arrive at the assessment page. The page opens with: - A vendor header card showing the name, subtitle, version, assessment date, and source materials - A toolbar with a legend, theme toggle, methodology toggle, and expand/collapse controls - An accordion list of all eight layers, all collapsed by default **The accordion interaction is the core UX.** All component-level detail is hidden until a layer is expanded. A buyer expands the layers that matter most to their evaluation — for example, Layer 2C for governance, Layer 2A for orchestration, or Layer 1A for data sovereignty — rather than reading the full assessment linearly. Each expanded layer reveals: - A purpose statement (one line defining what this layer does) - Vendor-provided components, each with a DAPM badge (Retained / Delegated / Ceded / Absent) and a detail paragraph - NVIDIA-provided components (where applicable), listed separately - A gap analysis narrative — where the vendor falls short relative to what this layer should provide - A borrowed judgment assessment — where the vendor's capability claim depends on a partner's roadmap rather than their own engineering - Working notes for additional context A buyer doing thorough due diligence will expand all layers using the "Expand All" button, read the gap analysis and borrowed judgment sections for each, and note which components are Ceded. Those Ceded and gap findings become the basis for RFP questions and briefing challenges. **The vendor selector dropdown** at the top of each assessment page allows a buyer to switch directly between vendor assessments without returning to the homepage. This enables side-by-side mental comparison — read Dell's Layer 2C assessment, then switch to HPE's Layer 2C assessment — without losing context. **The methodology panel** can be toggled open from the toolbar. It explains DAPM classifications, layer status indicators, and how to interpret borrowed judgment. Buyers unfamiliar with the framework use this as a reference while reading assessments. ### Converting Findings to Action At the bottom of each assessment is a Summary Finding — several paragraphs summarizing the vendor's overall architectural position. This is the CTO-level read: the synthesis of all the layer findings into a coherent architectural judgment. After reading one or more assessments, a buyer can use the [4+1 AI Platform RFP Framework](https://thectoadvisor.com/blog/2025/12/06/you-dont-buy-an-ai-platform-you-buy-layers-introducing-the-41-ai-platform-rfp-framework-open-edition/) to translate gap and Ceded findings into structured procurement questions. The enterprise buyers page (`/enterprise-buyers`) walks through this workflow step by step. ### The Buyer's Mental Model of the Site A CTO who has used the site for a vendor evaluation cycle would describe it this way: > "I used the compare page to filter down to three vendors worth deep review. Then I opened each assessment and expanded the layers that mattered for our use case — orchestration, runtime, and the reasoning plane. For each one I noted the Ceded components and read the gap analysis. By the time I finished, I had a list of ten questions I hadn't thought to put in our original RFP. The site didn't tell me which vendor to buy. It told me what I hadn't asked yet." --- ## The Technology Vendor Experience ### First Contact — Seeing Your Own Assessment A vendor arriving at layer2c.com may find it through a search, a customer reference, a LinkedIn mention, or a buyer who cited it in a briefing. The first thing a vendor typically does is find their own card on the homepage and click through to their assessment. The vendor experience of reading their own assessment is different from a buyer's experience. Vendors often react to specific DAPM classifications — particularly Ceded ratings on components they believe they own, or Partner status at layers where they consider themselves strong. The gap analysis and borrowed judgment sections are the most sensitive: these are the places where the assessment explicitly states what the vendor does not provide or where their claims depend on a partner's roadmap. Vendors who read their assessment with discipline use it as a mirror: the assessment shows what a well-prepared enterprise buyer will see before the first briefing. The question the assessment implicitly asks is: *can your team answer the gap analysis challenge, and can you prove the borrowed judgment does not apply to your current platform?* ### Navigating the Comparison Page as a Vendor A vendor's second stop is typically `/compare`. Here they can see their DAPM profile percentages alongside every competitor and see exactly where their layer status ratings sit relative to the field. The DAPM authority profile chart is particularly revealing for vendors: a high Ceded percentage relative to competitors is visible at a glance. A vendor with 60% Ceded components who competes against a vendor with 20% Ceded has a visible governance story disadvantage that enterprise buyers can read in seconds. The Layer 2C column of the comparison matrix is the one most vendors focus on. It shows how each vendor's reasoning plane capability is characterized — and whether the characterization is "Vendor Strength," "Gap," "Absent," or "Partner Ecosystem." For most vendors, this column is where the platform story is most at risk with enterprise buyers. ### The Vendor Page — Understanding the Commercial Path Vendors who want to understand how to respond to Layer2C findings — either to correct factual errors, improve their platform story, or pressure-test their narrative with real buyers — are directed to `/technology-vendors`. This page explains how enterprise buyers use the framework, what questions they will ask based on DAPM findings, and what evidence they expect before trusting governance, agent-control, or runtime claims. It also introduces Buyer Room (`advisorbench.net`) — The CTO Advisor's program for vendors who want direct access to enterprise buyers before going to market with their platform story. ### The Vendor's Mental Model of the Site A product marketing leader or CTO at an assessed vendor would describe the experience this way: > "We found it through a customer who mentioned it in a briefing. I read our assessment and my first reaction was defensive — we don't think of ourselves as having Ceded components at Layer 2A. But when I read the gap analysis, I understood the argument. The assessment is saying something specific about where authority lives, not just whether the product works. That's actually the harder question to answer in a sales conversation, and we hadn't built the evidence to answer it. We used the findings to rewrite our technical briefing deck and build three proof points we'd been missing." --- ## What the Site Does Not Do Understanding what Layer2C does not do is as important as understanding what it does — for both audiences. - It does not recommend a vendor. No assessment concludes with "buy this." - It does not rank vendors. There is no score, no tier, no best-in-class label. - It does not accept payment for inclusion or favorable treatment. - It does not provide real-time or continuously updated data. Each assessment reflects a specific version and date; architecture evolves faster than assessments can track. - It does not replace a proof of concept, a vendor briefing, or a formal RFP process. It informs those activities; it does not substitute for them. --- ## Navigation Summary | Starting point | Best for | |---|---| | `/compare` | Buyers shortlisting vendors; vendors benchmarking their position | | `/assessment/{id}` | Deep review of a specific vendor | | `/enterprise-buyers` | Buyers learning how to use the framework in a procurement workflow | | `/technology-vendors` | Vendors understanding how buyers read their platform story | | `/what-is-layer-2c` | Anyone needing to understand the 4+1 model and DAPM before reading assessments | | `/methodology` | Anyone who wants to know how assessments are scored and what they claim | | `/llms.txt` | LLMs and agents needing a structured index of all vendor data | | `/llms-full.txt` | LLMs and agents needing complete component-level assessment data | --- *Layer2C · AI Infrastructure Decision Intelligence · The CTO Advisor LLC · thectoadvisor.com*