rigorix-verifier (Python)
Strategy A parity for the Rigorix signed audit trail: an independent, protocol-only verifier so a Python consumer can check envelopes without shelling out to Rust. No engine dependency.
- HMAC-SHA256 over the canonical form (
signaturenulled) — byte-exact with the rigorix-oss engine and the Rust verifier. - JSON Schema conformance (draft 2020-12,
jsonschema). - ADR-016 chains: per-producer sequence +
prev_hashcontinuity, gaps accepted only when covered by a valid signed compaction checkpoint. - Ed25519 anchor artifacts (
cryptography): ledger receipt, history slice, compaction checkpoint.
Install
pip install rigorix-verifier==0.2.0 # published artifact (embedded corpus)
pip install . # or: pip install -e ".[test]" (from source)
Usage
import json
from rigorix_verifier import (
verify_signature, validate_envelope, verify_chain,
verify_chain_with_checkpoints, verify_history_slice,
)
envelope = json.load(open("envelope.json"))
verify_signature(envelope, "fixture-hmac-key-2026") # byte-exact HMAC
validate_envelope(envelope) # schema conformance
chain = json.load(open("chain.json"))
verify_chain(chain) # ADR-016 local chain
Canonical form
The HMAC is over serde_json::to_string(envelope with signature=None) as the
engine emits it: struct field order, skip_serializing_if fields omitted
when None/empty, non-skipped Option fields as null, scoring_results and
its dimensions maps sorted, and serde_json::Value payloads with sorted
keys. The field order is read from schemas/envelope.json. The committed
engine fixtures prove byte-exact parity (tests/test_envelope.py).
Contract corpus
Resolution (mirrors the Rust verifier):
RIGORIX_SDK_SCHEMAS— an explicit external corpus (CI/local override).- The bundled
rigorix_verifier/_schemasdirectory.
The bundled copy is generated from the repo-root schemas/ (the single
source of truth) by scripts/bundle_schemas.py:
the setuptools build_py/sdist hooks run it before packing, and
conftest.py runs it before tests. It is a real directory
(setuptools will not dereference a symlink into a wheel/sdist), never a
committed duplicate; tests/test_corpus_sync.py fails if it drifts from the
canonical corpus. The pack gate (python -m build → install wheel/sdist →
verify with RIGORIX_SDK_SCHEMAS unset) runs in CI. Run
python scripts/bundle_schemas.py manually if you need the copy outside a build.
Test
pytest -q
Metadata
Release files for rigorix-verifier 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| rigorix_verifier-0.5.0.tar.gz | 50.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rigorix_verifier-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 117.4 kB
Release files / rigorix_verifier-0.5.0.tar.gz
| Download URL | rigorix_verifier-0.5.0.tar.gz |
|---|---|
| Size | 50.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d8108001a94bfcf73254e0a534b0e6ec983fa1bc1a49b5283266dbbf2b6c7fb0
|
|
BLAKE2b-256 checksum How to use checksums |
8be3076040e86837e95208d45bd3aa9f75f2db0fbe13418de87cc4efed06baf4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 13, 2026.
Transparency logRelease files / rigorix_verifier-0.5.0-py3-none-any.whl
| Download URL | rigorix_verifier-0.5.0-py3-none-any.whl |
|---|---|
| Size | 66.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c85229497952abe9a5243930ebf5569d622af99c8181ec26946b7c7172d005b2
|
|
BLAKE2b-256 checksum How to use checksums |
4238b360959dd874711cfec9da6b3139a5f809f9122b7f3c463101c1a1af330f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 13, 2026.
Transparency log