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
Four Unified Views
- Unified Business Context
- Intelligence available at decision moments through AI agents that understand complete business context—not locked in data warehouses requiring analyst requests, not siloed in departmental tools, not trapped in tribal knowledge, but flowing naturally to the people who need it, when they need it, in the format they can actually use. →
- Unified Customer View
- Every person in your organization who interacts with customers sees complete relationship context in the system where they already work—not a separate dashboard to check, not a report to request, but immediate visibility into everything that matters about each relationship. →
- Unified Revenue View
- Revenue operations integrated end-to-end—forecasting based on relationship patterns rather than gut feelings, commercial processes streamlined and automated, and financial health visible in real-time across the entire customer lifecycle. →
- Unified Team Enablement
- Teams amplified by AI partnership, not replaced by automation. Technology enables sophisticated capability without proportional headcount, 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.