The open protocol
The Value Creation Protocol.
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. It's the protocol the AI-Native Shift program builds on top of. It's also the protocol any other organization, practitioner, or program can build on top of.
If the Five Layers describe how an AI-native organization is built, VCP is the open layer that lets two AI-native organizations describe what they've built in a structure the other one can read.
Why open
Three reasons VCP is open, not proprietary.
Because the shift is bigger than any one company
AI-native operations are an organizational transition every business has to make. No single vendor, no single program, no single methodology will get every organization through. An open protocol lets the work compound across organizations and practitioners who would never share proprietary frameworks.
Because protocols outlast products
The companies that built the early internet are mostly gone. The protocols they shipped (HTTP, SMTP, DNS) are still running everything. Open protocols are the durable layer. Programs and products built on top of them come and go. We're building VCP so the work outlasts any specific delivery vehicle — including ours.
Because contributors make protocols better
A protocol with one author is a manifesto. A protocol with contributors is a protocol. VCP exists to be extended by the practitioners actually doing AI-native operations work — Architects, Coaches, Educators — whose lived experience improves the protocol faster than any single team could.
The open AI-native stack
One protocol in a small family of open protocols.
VCP doesn't exist in isolation. It sits in the small but growing family of open protocols that together describe how AI-native systems actually work. MCP handles how AI reaches the machine context. HCP handles how AI represents the human context. VCP handles the value context — what creates value, for whom, and why — that the other two layers serve.
Diagram of the AI-native protocol stack showing three peer layers arranged vertically. Top layer: HCP (Human Context Protocol) — the human-context layer. How AI systems represent and respect human intent, authority, preferences, and history. Owner: Community. Status: HCP-Lang, March 2026. External: humancontextprotocol.com. Middle layer: VCP (Value Creation Protocol) — the value-creation layer. What creates value, for whom, and why — across the full relationship lifecycle. Owner: Value-First Team. Open standard, version 0.1 draft. Implement freely; trademark-protected naming. Within VCP, an Encoding Stack shows three sub-layers left to right: Layer A Lexicon (structured vocabulary), Layer B VCP-Lang (declarative grammar), Layer C Value Graph (relational specification). Each sub-layer feeds the next. Bottom layer: MCP (Model Context Protocol) — the machine-context layer. How AI systems reach tools, data, and external capability surfaces. Owner: Anthropic. Released 2024. External: modelcontextprotocol.io. A caption reads: Three peer layers — each necessary, none sufficient.
MCP — Model Context Protocol
Defines how AI models reach tools, data, and external capability surfaces. The machine-context layer. Owner: Anthropic. Released 2024. modelcontextprotocol.io.
VCP — Value Creation Protocol
Defines what creates value, for whom, and why — across the full relationship lifecycle. The value-creation layer. Owner: Value-First Team. Open standard, trademark-protected naming. valuecreationprotocol.com.
HCP — Human Context Protocol
Defines how AI systems represent and respect human intent, authority, preferences, and history. The human-context layer. Owner: Community. Status: HCP-Lang, March 2026. humancontextprotocol.com.
Open protocol, delivered program
VCP is the open foundation. The AI-Native Shift is one program built on it.
The AI-Native Shift program is a four-week cohort intensive that delivers a working AI-native stack built on VCP. The program is proprietary to Value-First Team — the delivery method, the facilitation approach, the operating playbook, the agents that run alongside the cohort.
VCP is not proprietary. The protocol itself — the Five-Layer Operating Model, the Value Path, the Twelve Complexity Traps, the Four Unified Views, the Core Beliefs — is published as an open standard. Another organization could read VCP, build their own program on top of it, and deliver to their own clients without paying us anything and without obtaining any license. We consider that a feature.
The relationship is the same shape as Linux and Red Hat: the kernel is open, the enterprise distribution is paid. The Linux project doesn't compete with Red Hat. Red Hat doesn't gate Linux. The AI-Native Shift program doesn't compete with VCP. VCP doesn't gate the AI-Native Shift program. They serve different audiences with different readiness.
The protocol itself
What VCP defines.
-
The Five Core Beliefs
The philosophical foundation: Natural Value Flow over Artificial Control, Empowerment over Learned Helplessness, Wholeness over Fragmentation, AI-Human Partnership over Replacement, Emergence over Predictability.
-
The Five-Layer Operating Model
The architectural foundation: Data · Customer Value Model · Intelligence · Orchestration · Interface.
Open the reference -
The Value Path
The eight-stage relationship model: Audience → Researcher → Hand-Raiser → Buyer → Value Creator → Adopter → Advocate → Champion.
Open the reference -
The Twelve Complexity Traps
The diagnostic frame: the twelve patterns that produce friction in AI-native transitions.
Open the reference -
The Four Unified Views
The outcome frame: Unified Customer View · Unified Revenue View · Unified Business Context · Unified Team Enablement.
Open the reference -
The Organizational Frame
Three functional orientations — Customer relationships · Operations · Financial health — replacing the twelve-department default with a simpler organizing logic.
Every concept in VCP has a canonical reference. None of it is gated. If you want to read VCP cover to cover, the protocol's home is at valuecreationprotocol.com.
How VCP grows
VCP improves through practitioners doing the work.
VCP is a living protocol. Its current state — version 1.0 of the Five Core Beliefs, version 1.0 of the Four Unified Views, the canonical references for the Value Path and the Twelve Traps — reflects what we've learned from real engagements. Future versions will reflect what contributors learn from theirs.
If you're an Architect, a Coach, or an Educator doing AI-native operations work and you've found patterns that VCP doesn't yet name — or doesn't name well — the protocol wants your contribution. The Value-First Collective is the structured community where practitioners contribute to VCP and to each other's practices.
As a reader
Read the canonical references. Use the language in your own work. Cite VCP when you do. No registration required. No license to sign.
As a contributor
Join the Collective — a paid community for practitioners committing to extend and apply VCP in their own engagements. The Collective is where protocol contributions, practitioner directory listing, and contribution-based value sharing live.
How VCP is published
An open standard, not a copyright-licensed work.
VCP is published as an open standard. No copyright license of any kind — open-source, content, or otherwise — attaches to the specification. Anyone may implement the protocol. Anyone may reference, quote, and discuss it. The author does not require a license for any of these activities and does not enforce copyright against good-faith implementation, reference, or commentary.
The names “Value Creation Protocol” and “VCP” are trademark-protected. The trademark prevents a third party from publishing a competing specification under the same name, or from claiming “VCP-compliant” status without meeting the conformance criteria. Trademark protection is the mechanism that keeps the specification coherent; copyright licensing is not.
This posture follows the pattern established by widely-adopted convention-style specifications — Markdown (John Gruber, 2004), the 12-Factor App methodology (Heroku, 2011), and the spirit of IETF RFCs. In each case, the specification was published without a formal copyright license, the name was protected via trademark or common-law identity, and broad community implementation occurred on the strength of publication and convention alone.
The full open-standard posture — including practical guidance for implementers, the comparable-precedent analysis, and the trademark policy direction — is at /legal/vcp-open-standard. The specification's canonical home is valuecreationprotocol.com.
Daily Brief
One shift, every weekday.
The Daily Brief takes the day’s episode and distills the architectural move underneath it.
Read it in two minutes. Sit with it for the rest of the day.
Unsubscribe at any time. Your address stays with us — never shared, never sold.