The Design Challenge · Four acts from real engagements
The strongest vendor story starts with an operating question. A Design Challenge carries one question from a working conversation into a challenged architecture, a measured lab, and a record the field can cite.
The program · Act I to Act IV
The conversation fixes the question. The challenge makes the vendor answer it in the open. The lab makes the boundary observable. The published record lets the field cite all three.
How to read this pageEach act is illustrated with published work, chosen to show what that act looks like in practice. The lab runs whether or not a vendor pays for it: 18 of 19 published labs are unsponsored. Commissioned Design Challenges publish at their own destinations; the first is underway with Google Cloud. The selection and the argument are editorial, not any vendor’s message.
Road Trip / Airstream
A working session with the operators, long enough to get past the architecture diagram and reach the decision that actually stalls.
Jump to Act I ↓Recorded design challenge
The vendor works the architecture on camera. The problem arrives from outside, and the answer gets challenged while the field watches.
Jump to Act II ↓Layer2C Labs
The design goes onto real infrastructure. Seams, controls, and failure paths become measured evidence with the limits stated.
Jump to Act III ↓The CTO Advisor · AEO / GEO
The findings become a record people and assistants can retrieve, and prompts the field can carry into a live customer engagement.
Jump to Act IV ↓Act I · The conversation
Real builders, a physical whiteboard, and enough time to get past the architecture diagram. These Town of Vail examples show the technical texture that establishes a Design Challenge.
EngagementHPE · Sponsored Road Trip content from the Town of Vail field engagement, published in 2026.
01THE CTO ADVISOR · ROAD TRIPReference film · Town of Vail + HPE
Keith goes inside the Town of Vail deployment to show how HPE infrastructure, NVIDIA accelerated computing, and Kamiwaza orchestration come together around real municipal workloads.
02THE CTO ADVISOR · ROAD TRIPReference film · Town of Vail data story
A second view into the Vail project: how decades of difficult municipal records became usable context for practical AI services, and why the data work matters as much as the models.
Act II · The challenge
This is the beat a vendor is actually buying. The problem arrives from outside, their architects answer it on camera, and the answer gets pushed on while the field watches.
EngagementArticul8 · Sponsored content, not a design challenge. The same challenge beat inside an editorial interview.
03THE CTO ADVISOR · DESIGN CHALLENGEReference film · Articul8
Articul8’s CTO takes the architecture question on camera. Keith brings the problem, the answer gets pushed on, and the assumptions behind it end up on the record instead of in a message track.
The format flip
Keith brings the problem
The vendor works the solution
Keith challenges the design
Layer2C Labs validates
A rehearsed message meets an architect and dies. A challenged one survives the question an account executive usually needs a sales engineer to answer.
Act III · The lab
A design that has not run is still an opinion. The lab is where it goes onto real infrastructure, gets measured, and comes back with its limits attached. Most of these run because a question is worth answering, not because a vendor asked.
EngagementLayer2C Labs · 18 of 19 published labs are unsponsored, including the one leading this act. The second is sponsored by Kamiwaza and says so.
Lab 003 · Editorial, unsponsored
A local bug-fix agent was supposed to need a frontier tier to escalate to. Gated by a deterministic harness with every call metered, the same-tier repair loop returned nothing.
What it does not prove.The task set is small. Eight tasks in the culminating run, 26 calibrated. Good for the architecture verdict, not a benchmark of pass rates.
Read the full lab ruling ↗Nobody commissioned this one. It is one of 18 unsponsored labs out of 19 published.
04LAYER2C LABS · LAB 015Reference film · Layer2C Lab 015
The lab build behind the ruling: a bench of analysts, one vendor each, running the same assessment instrument on Kamiwaza workrooms. The question is whether the platform keeps every analyst inside the evidence the curator approved.
Lab 015 · Sponsored precedent
What it does not prove.Nothing here is a security result. Every account was authorized and acting in good faith. One deployment, one release, two workrooms, one assessment workload.
Read the full lab ruling ↗Kamiwaza sponsored this lab. They did not choose the vendors or see the production instrument, and the record states that the findings include the ones they would not have chosen.Act IV · Publish and activate
The findings become a record a person or an assistant can retrieve. Every assessment, lab, and transcript turns into grounded context for the prompts the field carries into a customer conversation.
ArtifactsThe standing corpus: 27 independent vendor assessments, 19 lab records, and the router at labs.layer2c.com/llms.txt. Plus the HPE-sponsored paper below.
A sponsored publication · what one looks like
HPE-sponsored paper · January 2026
“Sensors everywhere, decisions nowhere.”
The published record from the Vail work: a repeatable CTO framework that starts with decision friction, designs the human and AI loop, builds shared capability, targets mundane cross-department decisions, and orchestrates an ecosystem rather than a product stack.
Read the 14-page paper ↗The activation layer · AEO / GEO
Architecture discovery
“Map this customer’s current AI architecture across the 4+1 layers. Identify which decisions are Retained, Delegated, or Ceded, and give me the five questions needed to validate the map.”First meeting · Architecture workshop
Competitive positioning
“Compare our platform with the customer’s incumbent for this workload. Use the Layer2C assessments and labs to distinguish capability from authority, cite the evidence, and name what remains unproven.”Account planning · Technical validation
Customer follow-through
“Turn the findings from this conversation into a Design Challenge brief: one testable architecture question, the authority boundary, success metrics, evidence required, and the next workshop agenda.”Solution design · Next-step activation
The response carries the relevant Layer2C assessment, lab ruling, transcript, evidence limits, and disclosure. The claim is corpus presence, never ranking or placement.
What the vendor walks away with
A sharper story tied to an enterprise architecture decision, answered in the open rather than rehearsed.
A credible proof set spanning video, measured lab work, and editorial analysis.
An account executive who cites instead of claiming, and can hold the architecture conversation without a sales engineer in the room.
Bring the architecture. We’ll bring the hard question.