Why an encoding stack
Foundation models default to industrial-age vocabulary because that vocabulary dominates training data. Prompt engineering can shift outputs at the surface, but the underlying defaults reassert under load — under context pressure, ambiguity, or when the model has to reason about novel situations.
The encoding stack gives VCP a substrate that does not depend on prompt-level overrides. Each layer makes a different aspect of VCP machine-executable.
The three layers
Layer A — Lexicon (lexical)
The structured vocabulary of VCP. Each entry encodes a load-bearing term with its industrial counterpart, operational definition, distinguishing signals, and contrastive training pairs. The Lexicon is the formal evolution of the Value-First Language Translation Guide.
Layer B — VCP-Lang (structural)
The grammar for declaring Values, Context, and Trust in parseable syntax. VCP-Lang declarations are structured statements AI systems can read, validate, and execute against. VCP-Lang descends from the March 2026 HCP-Lang work.
Layer C — Value Graph (relational)
The specification for encoding mutual value creation as a platform-agnostic relational structure. The Value Graph formalizes relationships the Value-First methodology already describes — particularly the Three-Org Model and the Value Path — into a graph specification AI systems can traverse.
Read the Value Graph spec v0.1 →
How the layers work together
A VCP-aligned system declares its values, context, and trust commitments using VCP-Lang, references terms whose meaning is fixed by the Lexicon, and operates over relationships modeled in the Value Graph. An AI system reading those declarations can verify alignment, surface drift, and generate outputs that respect the protocol without re-deriving the methodology from natural-language description.
Status
All three layers are at v0.1 — defined, scoped, and entering implementation. The Lexicon has the longest history (descended from a multi-year language guide). VCP-Lang is the newest layer. The Value Graph is being formalized from existing relational frameworks.
The encoding stack is not VCP. It is the substrate that makes VCP executable. VCP can be referenced without invoking the encoding stack; the encoding stack should not be referenced without invoking VCP, because the stack exists to serve the protocol.