Module 10: Next steps and resources

10.1 — Continue learning

• VCP Inspector: inspector.valuecontextprotocol.org — decode or encode CSM-1 codes, simulate capability negotiation, and explore sample inputs. The Inspector does not read multi-line CSM-1 tokens.
• VCP documentation: valuecontextprotocol.org/docs — eight guides and the protocol paper (PDF), covering integration concepts and selected parts of the specification
• Playground: valuecontextprotocol.org/playground — experiment with CSM-1 tokens interactively
• Interactive demos: valuecontextprotocol.org/demos — nine educational scenarios: The Driver's Seat, Gentian, Campion, Marta, Relay, Economic Governance, Ren, Noor, and Dr. Hana
• CSM-1 specification: valuecontextprotocol.org/docs/csm1-specification — reference for CSM-1 codes and tokens. The full protocol specification is the VCP-Spec repository.

10.2 — Start building

Published 4.2.0. Registry releases exist for every artifact; conformance claims remain same-program evidence. Install from the registries (pip install value-context-protocol==4.2.0, npm install @creedspace/vcp-sdk@4.2.0, cargo add vcp-core@4.2.0), or, to build from source, run these commands in a VCP-SDK checkout of the v4.2.0 tag:

Python SDK:

python -m pip install ./python

TypeScript WebMCP integration:

npm install ./webmcp

Rust SDK:

cargo build --manifest-path ./rust/Cargo.toml -p vcp-core

VCP v3.1 is the current protocol source baseline. SDK 4.2.0 also contains some v3.2 features, each marked as experimental.

• API Reference: valuecontextprotocol.org/docs/api-reference
• Getting Started Guide: valuecontextprotocol.org/docs/getting-started

10.3 — Project and source

• Creed Space: creed.space — project and research information
• GitHub: github.com/Creed-Space — source, examples, specifications, and issue tracking

10.4 — Before provider integration

• Choose the supported protocol baseline and negotiated extensions
• Define trust anchors, bundle acquisition, revocation, and degraded-operation policy
• Validate against shared conformance vectors at an exact Spec and SDK revision
• Publish compatibility and limitations without implying certification

10.5 — For governance teams

• Treat VCP evidence as one part of the wider legal, risk, privacy, security, and human-oversight system
• Assign authorship, review, attestation, publication, revocation, and appeal authority
• Keep experimental protocol features visibly separate from accepted baselines
• Require human and legal review before making compliance or certification claims