algovoi-refund-receipt-lite
Open, content-addressed refund references for the AlgoVoi substrate. The lite, Apache-2.0 origination tier of the commercial AlgoVoi Refund Receipt.
refund_ref = "sha256:" + SHA-256(JCS({ refund_amount, refund_result, subject_ref }))
It content-addresses the refund of a prior payment into a deterministic, recomputable reference:
subject_ref: the payment/decision being refunded, imported by hash. Typically theguardrail_refof the pre-payment decision or a settlement reference, so the refund composes onto the decision chain and closes the lifecycle after settlement.refund_result: a closed enum:FULL,PARTIAL,REJECTED.refund_amount: the amount returned, as a string ("0"for a REJECTED refund).
All three fields are byte-load-bearing: change the subject, the result, or the amount and the refund_ref diverges, so a refund cannot be silently re-pointed to another payment and neither the outcome nor the amount can be changed. A result outside the enum, or an empty subject_ref/refund_amount, is rejected, not hashed.
Use
from algovoi_refund_receipt_lite import refund_ref
ref = refund_ref(
subject_ref="sha256:2a444c629892f44fde1bd004aba9be01dd6cc7fe251eecdd545b82dca9f0bf97",
refund_result="FULL",
refund_amount="1000",
)
Lite vs commercial
| Lite (this package) | Commercial Refund Receipt | |
|---|---|---|
| Licence | Apache-2.0, open | Commercial OEM |
| Reference | content-addressed refund_ref |
the same, Falcon-1024 signed receipt |
| Carries | result + amount + subject (by hash) | + provider, timing, jurisdiction |
| Propagation | bring your own | closes original payment across settlement + retention chains |
| Verifier | recompute offline | maintained verifier |
Adopters (pin → key)
If you build on algovoi-refund-receipt-lite, pin ==0.1.0, anchor a canonical refund_ref vector hash from refund_receipt_lite_v1, and keep the NOTICE, you qualify for a free v0 licence key for algovoi-mandate-auditor. The gate is scripts/check_v0_adoption.py. Apply: email chopmob@gmail.com with your import-by-hash evidence and a copy of the NOTICE.
Conformance
The refund_receipt_lite_v1 vector set is published in the public corpus,
chopmob-cloud/algovoi-jcs-conformance-vectors,
with Python and Node runners. Python and TypeScript reproduce every value byte-for-byte. rf-001, rf-002 and rf-003 refund the ALLOW guardrail_ref in spend_guardrail_lite_v1 / spend_decision_chain_v1.
Apache-2.0. Additive over the frozen canonicalisation substrate; sole AlgoVoi authorship.
Metadata
Release files for algovoi-refund-receipt-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_refund_receipt_lite-0.1.3-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl | CPython 3.11 | CPython 3.11 | Linux glibc 2.17+ x86-64 | Details |
Release files / algovoi_refund_receipt_lite-0.1.3-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | algovoi_refund_receipt_lite-0.1.3-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 137.5 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
dd8a224bbee8f28565ef8294c726bc7c84a2b55602c25aae75d59dee8714c200
|
|
BLAKE2b-256 checksum How to use checksums |
f0a7b455c77722c651b3e0359dc2f3cf014f7c71e360cedc29b37ce6dc24a7f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Security for algovoi-refund-receipt-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.