Reference
Glossary
The vocabulary VCP fixes. Industrial-age defaults sit nearby in the encoding work; this page lists the load-bearing terms VCP commits to.
Protocol Stack & Encoding Stack
- Value Creation Protocol (VCP)
- The protocol identity of the Value-First methodology — the methodology expressed in a form that machine systems can parse, declare, and execute. Sits atop MCP and HCP in the AI-native protocol stack.→
- Model Context Protocol (MCP)
- Gives AI systems capability — the ability to call tools, read context, and act in external systems. The bottom layer of the AI-native protocol stack.↗
- Human Context Protocol (HCP)
- Gives AI systems human context — the ability to represent and respect the interests, agency, and lived reality of the humans involved. The middle layer of the protocol stack.
- CVP (Customer Value Platform)
- The platform category for systems organized around customer relationships and value creation rather than internal record-keeping. HubSpot is the canonical implementing CVP for the Value-First methodology.→
- Encoding Stack
- The three-layer substrate that makes VCP machine-parseable: Lexicon (lexical), VCP-Lang (structural), Value Graph (relational).→
- Value-First Lexicon
- Layer A of the encoding stack. The structured vocabulary of VCP — each entry encodes a load-bearing term with its industrial counterpart, operational definition, and contrastive training pairs.→
- VCP-Lang
- Layer B of the encoding stack. The grammar for declaring Values, Context, and Trust in parseable syntax. Descends from the March 2026 HCP-Lang work.→
- Value Graph
- Layer C of the encoding stack. The specification for encoding mutual value creation as a platform-agnostic relational structure. Three-Org Model and Value Path expressed as graph traversal.→
- Value Activated
- The commercial state in which value has started flowing — what an industrial-age protocol would call "closed-won." Replaces the closing vocabulary because the relationship is beginning, not ending.
- Mutual Value Creation
- Value created across stakeholders, not extracted from them. Customers, employees, operators, and the organization itself are participants in value creation.
- Configuration Over Customization
- Favors configuring native platform capability over customizing bespoke architecture. Reduces consultant dependency and brittle integrations.
- Just-In-Time Operations
- Operations designed to deliver capability when needed, not to accumulate it against hypothetical need. Requires unified context as substrate.
- Unified Context
- Relationship history, preference signals, prior commitments, and current state held in one substrate. The operating layer all decisions reference. Fragmented context produces fragmented operations.
- AI-Native Shift
- The pattern of organizational transformation toward operations where AI is the substrate rather than an add-on. A methodology, not a program — implementations vary by firm.→
- Value-Led Growth
- Growth as a consequence of value created, not a function pursued. Replaces lead generation, conversion optimization, and growth-hacking framings.→
- Value Realities
- The operational realities of value creation in AI-native systems. Each reality is paired with the Complexity Trap it counters and the commitments it implies.→
Five Core Beliefs
- Natural Value Flow over Artificial Control
- Value exists and wants to flow naturally through human systems, independent of our efforts to control it.→
- Empowerment over Learned Helplessness
- Organizations thrive when people are empowered to create and share value naturally rather than waiting for permission or instruction.→
- Wholeness over Fragmentation
- Value multiplies through connection rather than division.→
- AI-Human Partnership over Replacement
- AI should multiply human capability, not replace it. Technology's highest purpose is to handle mechanical coordination while enhancing uniquely human capabilities like creativity, judgment, and connection.→
- Emergence over Predictability
- Reality reveals itself through engagement. It does not announce itself in advance.→
Four Unified Views
- Unified Strategy View
- The Strategy View brings human domain expertise, customer reality, commercial context and the broader knowledge of the business to the actual moment of decision. What the team can see, AI can see; that is how the view works, not what it is. Context is more than data. It comes in three layers: the data; the documentation and strategy; and the memory people never wrote down. It reaches the moment of decision through the people who hold the context and the AI that carries it: not locked in data warehouses requiring analyst requests, not siloed in departmental tools, but flowing to the people who need it, when they need it, in the format they can actually use.→
- Unified Customer View
- The view covers every relationship that can create value, not only customers. Everyone who serves a relationship sees the context they need for the decision in front of them, unified from wherever it lives, in the place they already work: not a separate dashboard to check, not a report to request. The Customer View lives in the records people work in.→
- Unified Revenue View
- The Revenue View holds the whole commercial picture. Before anything is booked, it makes visible the marketing activity, the emerging demand, the sales conversations, the opportunities and the proposals. After the commitment, it carries on through delivery, receipt, further orders, renewals and services.→
- Unified Operations View
- Teams amplified by AI partnership, not replaced by automation. Capability grows faster than headcount, so the people you have can do work they could not do before. Operations scale without creating complexity, and innovation becomes accessible rather than requiring massive investment.→
Value Path Stages
Twelve Complexity Traps
- AI Replacement Trap
- A pattern that derails value creation. See Trap canon page.→
- Advertising Trap
- A pattern that derails value creation. See Trap canon page.→
- Authority Trap
- A pattern that derails value creation. See Trap canon page.→
- B2B Trap
- A pattern that derails value creation. See Trap canon page.→
- Conformity Trap
- A pattern that derails value creation. See Trap canon page.→
- ERP Trap
- A pattern that derails value creation. See Trap canon page.→
- Lead Magnet Trap
- A pattern that derails value creation. See Trap canon page.→
- Leads Trap
- A pattern that derails value creation. See Trap canon page.→
- Managed Services Trap
- A pattern that derails value creation. See Trap canon page.→
- Measurement Trap
- A pattern that derails value creation. See Trap canon page.→
- Qualification Trap
- A pattern that derails value creation. See Trap canon page.→
- SaaS Trap
- A pattern that derails value creation. See Trap canon page.→
Glossary entries are drawn from the canonical methodology records. For any conflict between this page and a canon page, the canon page wins.
Protocol home
VCP is originated and canonically implemented by Value-First Team. Anyone may read, cite, and operate the protocol independently of firm engagement.