The operating model underneath the show.

Every organization is running five layers — Data, Customer Value Model, Intelligence, Orchestration, and Interface — whether they've named them or not. The Five-Layer Operating Model makes the layers explicit so you can see what's missing, what's mis-stacked, and what's holding the whole thing together by accident.

Most organizations have a strong Layer 1 (data) and a strong Layer 5 (interface — the apps everyone uses). Layers 2, 3, and 4 are usually the gap. AI-native operations require all five.

The Value Path describes how relationships actually move — from a stranger encountering your work for the first time, through being a customer, through the moment when your work becomes part of how their organization operates, all the way through advocacy and championship. Eight stages, two halves: the Path to Value (Audience through Buyer) and the Path of Value (Value Creator through Champion).

The Value Path replaces the funnel. The funnel ends at the sale. The Path keeps going — and in AI-native organizations, the work after the sale is where the relationship actually compounds.

The Value Creation Protocol is an open standard for AI-native operations — implementable by anyone without a copyright license, contributor-extensible, and deliberately separate from any one company's program. The names "Value Creation Protocol" and "VCP" are trademark-protected to prevent fraudulent conformance claims. It's the protocol that the AI-Native Shift program builds on top of. It sits next to MCP (the Model Context Protocol) and HCP (the Human Context Protocol) as part of the open AI-native stack.

If you're building AI-native operations and you want to know what the open foundation looks like, this is the doorway. If you want to contribute to it, the canonical home for the protocol is at valuecreationprotocol.com.

Most organizations aren't failing at AI-native operations because they're doing something wrong. They're failing because they're caught in patterns that were reasonable for an industrial-age business and are no longer reasonable for an AI-native one. The Twelve Complexity Traps name those patterns — and once they're named, they can be seen, and once they're seen, they can be left.

The Twelve Traps are how we run diagnostics. The cohort opens with a Trap Assessment in Week 1 because the architecture work in Week 2 doesn't hold if the traps you're sitting in aren't surfaced first.

The Four Unified Views are the business outcomes the framework produces when it's actually deployed: Unified Customer View, Unified Revenue View, Unified Business Context, Unified Team Enablement. They're not features to implement. They're conditions to achieve — and they build in order, because each one depends on the foundations the previous one creates.

If the Five Layers describe how the system is built, the Four Unified Views describe what the system gives you when it's working.