Skip to main content

VCP — Governance Layer

The Value Context Protocol lets an AI agent carry a machine-readable declaration of what it holds itself to, and lets other parties reason about it. This repository is the governance layer: the types, wire formats and algorithms for deciding things together — multi-stakeholder deliberation, constitutional amendment with quorum, attestation and trust chains, drift detection, and insurability scoring.

The protocol core (tokens, CSM1 codes, VCP-Lite, context) lives in the VCP SDK — pip install vcp-sdk. Spec and docs: https://valuecontextprotocol.org.

Apache-2.0.

⚠️ Read this before you deploy it

Several modules here are reference implementations, and they say so in their own docstrings.

The clearest example: GovernanceAuthority implements M-of-N constitutional amendment signing — and stores its state in module-level Python dicts. That means every registered authority and every in-flight amendment proposal is lost on restart, and a multi-instance deployment gets a different store per instance, so quorum can never actually be reached.

That is deliberate. This library defines the types, the wire format and the quorum semantics, and stays storage-agnostic so you can bind it to a durable, authenticated store you actually run. But if a constitution can be amended by an M-of-N vote, the record of who signed what must outlive a process restart — otherwise the governance is theatre.

Do not build real constitutional governance on the in-memory stores. Substitute a database first.

What's in here

Module What it does
consensus/ Schulze ranked-preference voting and the deliberation lifecycle
governance_authority M-of-N constitutional amendment with quorum
attestation_authority Federated trust chains (SELF / PEER / AUTHORITY / CHAIN) with drift-triggered revocation
drift_check Detects a constitution drifting from what it claimed to be
insurability / economic Auditability rubric — deliberately a rubric, not a model, so everyone computes it the same way
context_opacity Raw affective/somatic signals never reach the model; only a graded protection level does
audit_chain SHA-256 hash chain over decisions
identity/, semantics/, negotiation/, adaptation/, messaging/ Identity tokens, CSM1 semantics, negotiation, adaptation, envelopes

Signing

VCP never touches your keys. It depends on a two-method interface:

from vcp_governance.signer import Signer, Ed25519Signer

signer = Ed25519Signer(private_key_bytes=my_seed, key_id="my-issuer")   # key by INJECTION

Implement Signer yourself to back it with an HSM, a KMS, or anything else. Key custody is a deployment concern and belongs to you, not to a protocol library.

Defaults

vcp_governance/defaults.py gathers every value that points at Creed Space infrastructure, in one place, because they are the ones you are most likely to want to change and least likely to notice.

In particular, ASSESSOR_ID defaults to creed-space. If you issue your own competence claims, override it — otherwise your claims assert that we assessed them, which we did not.

Install

pip install vcp-governance          # once published
pip install vcp-governance[crypto]  # + the Ed25519 reference signer

Status

Extracted from the Creed Space monorepo. The public API may move before 1.0. Issues and PRs welcome.

Metadata

Release files for vcp-governance 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for vcp-governance 0.1.0
File Size Uploaded Provenance
vcp_governance-0.1.0.tar.gz 264.8 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for vcp-governance 0.1.0
File Interpreter ABI Platform
vcp_governance-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 569.5 kB

Release files / vcp_governance-0.1.0.tar.gz

Download URL vcp_governance-0.1.0.tar.gz
Size 264.8 kB
Tags Source
SHA-256 checksum
How to use checksums
b17a41f5d36974163401b3771d69da429272dbc36a3349b99b98f2fa5729acd5
BLAKE2b-256 checksum
How to use checksums
b7e6300086e08a5cf5d83c55a358fa35e7bad7aa996cfeebeee8556f98c96c6a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.6

Release files / vcp_governance-0.1.0-py3-none-any.whl

Download URL vcp_governance-0.1.0-py3-none-any.whl
Size 304.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5c630a25604120658f3eb674ec83c6efee7f321ba7d53b528382168012e8b9c4
BLAKE2b-256 checksum
How to use checksums
eca46f566b3d403358dc3bce28ba212187d8ee060a0a7dbdc267ee34d51e90de
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.6

Security for vcp-governance 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page