Release boundaries
| Surface | Status |
|---|---|
| Core specification | VCP v3.1 source baseline. A fixed, ratified release of the specification has not been issued yet. |
| v3.2 adaptation amendments and VEP-0004 | Pre-release or experimental |
| Python, Rust, and WebMCP packages | SDK 4.2.0, published on PyPI, npm, and crates.io |
| Demo Site | Educational application, not conformance evidence |
Tools
| Tool | Location | Purpose |
|---|---|---|
| VCP Inspector | inspector.valuecontextprotocol.org | Decode and encode CSM-1 codes and simulate capability negotiation |
| Playground | valuecontextprotocol.org/playground | Experiment with contexts and tokens, including prototype formats used only on this site |
| Interactive demos | valuecontextprotocol.org/demos | Illustrative scenarios, not third-party integration claims |
| Source repositories | github.com/Creed-Space | Specification, SDK, examples, and conformance vectors |
Package and API cheat sheet
SDK 4.2.0 is published on PyPI, npm, and crates.io. Each install row gives the registry command; the "from source" rows build the same release from a VCP-SDK checkout of the v4.2.0 tag.
| Operation | Maintained form |
|---|---|
| Install Python | python -m pip install value-context-protocol==4.2.0 |
| Install Python from source | python -m pip install ./python |
| Parse Python identity | Token.parse("family.safe.guide@1.2.0") |
| Parse Python CSM-1 | CSM1Code.parse("N5+F+E") |
| Verify Python bundle | Orchestrator(trust).verify(bundle) |
| Enforce Python policy | PDPEnforcer(fail_closed=True).evaluate(...) |
| Install WebMCP | npm install @creedspace/vcp-sdk@4.2.0 |
| Install WebMCP from source | npm install ./webmcp |
| Register browser tools | await registerVCPTools(config) |
| Install Rust | cargo add vcp-core@4.2.0 |
| Build Rust from source | cargo build --manifest-path ./rust/Cargo.toml -p vcp-core |
| Parse Rust identity | VcpToken::parse("family.safe.guide@1.2.0") |
Enforcement decisions
| Decision | Meaning | Application responsibility |
|---|---|---|
ALLOW | Registered plugins did not block the action | Continue only if all other security and business gates also pass |
BLOCK | Policy rejects the action | Stop the action and expose only a safe, useful reason |
MODIFY | A plugin requests a constrained change | Apply only a reviewed transformation and re-evaluate when required |
ESCALATE | A plugin requests a higher-authority decision | Route it to a human review process your application owns. The SDK
4.2.0 enforcer has no escalation handler, so its final decision is BLOCK; the plugin's ESCALATE decision stays
in the result's decision list for your application to act on. |
Verification outcomes
| Category | Outcomes | Default response |
|---|---|---|
| Success | VALID | Continue to local enforcement |
| Security | SIZE_EXCEEDED, INVALID_SIGNATURE, INVALID_ATTESTATION, HASH_MISMATCH, FUTURE_TIMESTAMP, REPLAY_DETECTED, TOKEN_MISMATCH, REVOKED | Reject and investigate as appropriate |
| Trust and configuration | INVALID_SCHEMA, UNTRUSTED_ISSUER, UNTRUSTED_AUDITOR, BUDGET_EXCEEDED, SCOPE_MISMATCH | Reject and repair configuration or inputs |
| Temporal | NOT_YET_VALID, EXPIRED | Reject; obtain an appropriate current bundle |
| Transient | REVOCATION_UNAVAILABLE, FETCH_FAILED (defined, but SDK 4.2.0 never returns it) | Reject; retry within your deadline. Any degraded mode runs without this bundle. |
CSM-1 quick reference
Code format: {persona}{adherence}[+scopes][:namespace][@version]
Personas: N (Nanny), Z (Sentinel), G (Godparent), A (Ambassador), M (Muse), D (Mediator), C (Custom, which requires a namespace)
Adherence levels: 0 Minimal (advisory only), 1 Relaxed, 2 Moderate, 3 Standard, 4 Strict, 5 Maximum
Scopes: F (Family), W (Work), P (Privacy), E (Education), T (Technical), O (Official), V (Vulnerable), A (Adult), H (Health), S (Social), R (Religious). A cannot be combined with F, V, or H.
Personal state dimensions
| Dimension | Example values | Intensity |
|---|---|---|
| Cognitive State | focused, distracted, overloaded, foggy, reflective | Optional 1 to 5 |
| Emotional Tone | calm, tense, frustrated, neutral, uplifted | Optional 1 to 5 |
| Energy Level | rested, low_energy, fatigued, wired, depleted | Optional 1 to 5 |
| Perceived Urgency | unhurried, time_aware, pressured, critical | Optional 1 to 5 |
| Body Signals | neutral, discomfort, pain, unwell, recovering | Optional 1 to 5 |
Attestation types
| Type | Claim boundary |
|---|---|
INJECTION_SAFE | An authorized auditor asserts the defined injection-safety review was completed |
CONTENT_SAFE | An authorized auditor asserts the defined content-safety review was completed |
FULL_AUDIT | An authorized auditor asserts the organization's defined full-audit evidence exists |
COMPETENCE_CALIBRATION | An authorized auditor asserts the defined competence-calibration review was completed |
Only INJECTION_SAFE and FULL_AUDIT pass SDK 4.2.0
bundle verification; a bundle attested CONTENT_SAFE or COMPETENCE_CALIBRATION fails with INVALID_ATTESTATION (see Module 6.3).
A valid attestation proves that an auditor recognized by your configured trust anchors signed the claim. It does not prove the quality, legality, or completeness of the review behind it.