Skip to main content

verity

How do you trust what an AI agent built?

verity is a proof-chain registry for AI agents. It records what was built, what was claimed, what tests ran, and what they proved. Every chain is published to Walrus as an immutable blob. Any agent, on any machine, can pull it back and verify it.

CI Coverage PyPI version Python 3.11+ License: MIT PyPI Downloads


The model

feature → claim → test → evidence → release
                                       │
                              verity push ──► Walrus blob ID (immutable)
                              verity pull ◄── restore anywhere, any agent
  • feature — a capability being shipped
  • claim — a testable statement about the feature
  • test — the mechanism that exercises the claim
  • evidence — the pass/fail signal the test produced
  • release — a named snapshot; push() publishes it to Walrus

Built for the Sui Overflow hackathon, Walrus track.


Install

# Full install — everything included
uv tool install "walrus-verity[all]"

# Or with pip
pip install "walrus-verity[all]"

# Individual extras
pip install "walrus-verity[memwal]"   # MemWal semantic recall
pip install "walrus-verity[sign]"     # Ed25519 signing
pip install "walrus-verity[mcp]"      # MCP server

Quick start

The fastest path — one command records the full claim/test/evidence chain:

verity init --repo-id repo:my-project
verity track feat:auth tests/test_auth.py --title "Login succeeds"
verity validate
verity release 1.0.0
verity push                    # → blob: AbCdEfGh…
verity push --upload-artifacts # upload artifact files to Walrus first, then push registry

Or build the chain manually for full control:

# Phase 1 — add entities with neutral statuses
verity add feature  feat:auth "User authentication"
verity add claim    clm:auth.t1 "Login succeeds"  --feature feat:auth
verity add test     tst:auth.unit "Unit test"      --claim clm:auth.t1 --path tests/test_auth.py
verity add evidence evd:auth.ci "CI run"           --test tst:auth.unit --artifact artifacts/ci.json

# Phase 2 — promote statuses once the chain is fully linked
verity add evidence evd:auth.ci "CI run" --test tst:auth.unit --artifact artifacts/ci.json --status passed
verity validate      # → OK
verity release 1.0.0
verity push          # → blob: AbCdEfGh…

# Any agent, any machine, any future session:
verity pull AbCdEfGh…

Why neutral statuses first? verity validates after every add. Setting --status verified on a claim before its test exists will fail. Build the full chain first, then promote statuses.


Multi-agent trust

Agent A builds and signs. Agent B verifies before building on top.

# Agent A
verity push                                          # → blob_a
verity keygen --key ~/.verity/signing.key            # generate keypair once
verity sign --key ~/.verity/signing.key              # attest blob_a
verity push                                          # → blob_b (carries the attestation)

# Agent B — receives blob_b + pubkey
verity verify blob_b --pubkey-b64 <pubkey>
# blob: blob_b   repo: repo:my-project
# features 4  claims 5 (5 verified)
# chain valid ✓
# signature valid ✓   attests: blob_a…  signer: <pubkey>…

AI coding assistant integration

Skill installer — teaches your AI assistant the verity model, CLI, and API:

verity install-skill                    # Claude Code (global CLAUDE.md)
verity install-skill --tool cursor      # Cursor → .cursorrules
verity install-skill --tool windsurf    # Windsurf → .windsurfrules
verity install-skill --tool codex       # OpenAI Codex → AGENTS.md
verity install-skill --tool aider       # Aider → CONVENTIONS.md

MCP server — expose all verity tools natively to any MCP-compatible editor:

pip install "walrus-verity[mcp]"

Add to your claude_mcp_config.json (or equivalent):

{
  "mcpServers": {
    "verity": {
      "command": "verity-mcp",
      "env": {
        "WALRUS_PUBLISHER_URL": "https://publisher.walrus-testnet.walrus.space",
        "WALRUS_AGGREGATOR_URL": "https://aggregator.walrus-testnet.walrus.space"
      }
    }
  }
}
MCP tool Description
verity_init Create .verity/registry.json
verity_add_feature / claim / test / evidence Add chain entities
verity_set_status Promote status after chain is wired
verity_set_status_batch Promote multiple entities atomically in one call
verity_validate Validate the full chain
verity_release Fail-closed release
verity_push Push to Walrus; upload_artifacts=True uploads local artifact files first
verity_pull Fetch blob from Walrus; force=True to overwrite existing registry
verity_log Push history
verity_status Entity counts + validation summary
verity_diff Diff two Walrus blob snapshots
verity_export Export to SARIF, JUnit, or SPDX
verity_sign Sign the latest push with an Ed25519 key
verity_verify Fetch blob, validate chain, check signature
verity_recall Natural language query against MemWal

Export and interop

verity export --format sarif    # SARIF 2.1.0 — security findings dashboards
verity export --format junit    # JUnit XML  — CI test result viewers
verity export --format spdx     # SPDX 2.3   — software bill of materials

Recall

Push with MemWal to register semantic memories alongside the Walrus blob:

verity push --backend memwal

verity recall "what features have we built"
verity recall "what claims are verified"
verity recall "what was the latest release"

Watch mode

verity watch polls the registry file and validates (and optionally auto-pushes) on every change:

verity watch                       # poll every 5s, validate on change
verity watch --interval 30         # custom poll interval (seconds)
verity watch --auto-push           # push to Walrus on each valid change
verity watch --auto-push --backend memwal

Documentation

Full documentation is available at here — CLI reference, MCP server, Python API, schema, Walrus/MemWal setup, and multi-agent patterns.


Acknowledgements

The proof-chain model (feature → claim → test → evidence → release) is directly inspired by the ssot-registry project, licensed under Apache 2.0. verity adapts that model for AI agents and Walrus-backed persistence.


Contributing

See CONTRIBUTING.md.

License

MIT. See LICENSE.

Metadata

Release files for walrus-verity 0.3.15

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

Source distribution (sdist)

Source distribution for walrus-verity 0.3.15
File Size Uploaded Provenance Actions
walrus_verity-0.3.15.tar.gz 3.9 MB With provenance Details for walrus_verity-0.3.15.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for walrus-verity 0.3.15
File Interpreter ABI Platform Actions
walrus_verity-0.3.15-py3-none-any.whl Python 3 none any Details for walrus_verity-0.3.15-py3-none-any.whl

Total release size: 4.0 MB

Release files / walrus_verity-0.3.15.tar.gz

Download URL walrus_verity-0.3.15.tar.gz
Size 3.9 MB
Tags Source
SHA-256 checksum
How to use checksums
4978e5513b7eb3c39c15ef2663190908d93c838ac001f594a706102706d7ffcb
BLAKE2b-256 checksum
How to use checksums
1c6abe8b307c13a4fa14b9206691dcfb6e1a2b3b4cf9e3184cbef4b3fce7d336
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 30, 2026.

Transparency log

Release files / walrus_verity-0.3.15-py3-none-any.whl

Download URL walrus_verity-0.3.15-py3-none-any.whl
Size 39.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7c23f3e5ffb9ef76563634073a400506f7c30398e05ff9fd4a96fe1aff8c0c1f
BLAKE2b-256 checksum
How to use checksums
c2732f3797116cb87fa39e12792a023014d46257e5afb2ffa2412a9b8ab5729b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 30, 2026.

Transparency log

Security for walrus-verity 0.3.15

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for walrus_verity-0.3.15.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 30, 2026.

Transparency log

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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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