algovoi-payment-mandate-lite
The open, lite origination layer for AlgoVoi Payment Mandate. It content-addresses the
terms of a spend authority (payer, cap, period, revocation_state) into a
deterministic, recomputable mandate_ref.
This mandate_ref is exactly the mandate_ref that Spend Guardrail (lite) binds: pin the mandate by hash, then the pre-payment decision is bound to that hash. Change the cap, the period, or the revocation state and the reference diverges, so a decision made against one authority cannot be silently re-attributed to another. Additive over the frozen substrate (Apache-2.0):
mandate_ref = "sha256:" + SHA-256(JCS({cap, payer, period, revocation_state}))
Lite vs commercial
| Lite (this package) | Payment Mandate (commercial) | |
|---|---|---|
| Licence | Apache-2.0, open | Commercial OEM |
| Authority | content-addressed mandate_ref |
Falcon-1024 PQC signed mandate |
| Enforcement | reference only | authorize-charge against the per-period cap |
| Verifier | recompute offline | maintained verifier |
Pin lite, anchor a vector hash, carry the NOTICE → free v0 key.
Install & use
pip install algovoi-payment-mandate-lite
from algovoi_payment_mandate_lite import mandate_ref, verify
ref = mandate_ref("0x…payer", "1000", "monthly", "active") # cap is a string
verify(ref, "0x…payer", "1000", "monthly", "active") # True
verify(ref, "0x…payer", "2000", "monthly", "active") # False (cap tamper)
verify(ref, "0x…payer", "1000", "monthly", "revoked") # False (revocation tamper)
All four fields are byte-load-bearing; an empty or missing field is rejected, not hashed.
Conformance
conformance/payment_mandate_lite_v1/: 3 positives, 4 field-tamper negatives (payer / cap /
period / revocation), 2 rejection negatives (empty field), 2 invariants. mandate_1 and
mandate_2 equal the mandate_1 / mandate_2 references in spend_guardrail_lite_v1, so the
decision chain composes. Verifier imports only stdlib + rfc8785:
pip install rfc8785
python conformance/payment_mandate_lite_v1/verify.py
Adopters
The 4-check gate is scripts/check_v0_adoption.py (dependency + canonical hash anchor + NOTICE +
version pin → ISSUE_V0_KEY). Apply: chopmob@gmail.com.
License
Apache-2.0. Copyright 2026 AlgoVoi. Preserve the NOTICE in any distribution.
Metadata
Release files for algovoi-payment-mandate-lite 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| algovoi_payment_mandate_lite-0.1.3-cp311-cp311-manylinux1_x86_64.manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_5_x86_64.whl | CPython 3.11 | CPython 3.11 | Linux glibc 2.5+ x86-64, Linux glibc 2.17+ x86-64 | Details |
Release files / algovoi_payment_mandate_lite-0.1.3-cp311-cp311-manylinux1_x86_64.manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_5_x86_64.whl
| Download URL | algovoi_payment_mandate_lite-0.1.3-cp311-cp311-manylinux1_x86_64.manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 136.5 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
f1c3ab8aa2ec9dbe64a36dc891a16e0d9b65a73670ed502e09bd430100286de4
|
|
BLAKE2b-256 checksum How to use checksums |
0df7f51b5cfcaae92ca0b6b2d3bb90197de910f9c9fe00eb100858fd9ca11374
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Security for algovoi-payment-mandate-lite 0.1.3
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.