algovoi-composite-trust-query-lite
Open, content-addressed trust-verdict references for the AlgoVoi substrate. The lite, Apache-2.0 origination tier of the commercial AlgoVoi Composite Trust Query. It caps the open decision/receipt lifecycle: one recomputable address binds a categorical trust answer to the exact set of references it was computed over.
trust_query_ref = "sha256:" + SHA-256(JCS({ subject_refs, trust_outcome }))
subject_refs: the ordered list of references the verdict was reached over, each imported by hash (e.g. thepassport_ref,mandate_ref,policy_bound_refandguardrail_refof a decision chain). Order and membership are both byte-load-bearing.trust_outcome: a closed enum:TRUSTED,PROVISIONAL,INSUFFICIENT_EVIDENCE,UNTRUSTED.
Change which references were assessed, their order, or the verdict, and the trust_query_ref diverges, so a verdict cannot be re-pointed to a different set or silently drop a reference it claimed to assess. An outcome outside the enum, an empty list, or an empty member is rejected, not hashed.
Lite binds only. This package content-addresses the binding; the scoring and verification that produce the verdict stay commercial.
Use
from algovoi_composite_trust_query_lite import trust_query_ref
ref = trust_query_ref(
subject_refs=[
"sha256:b3594e33998af01bd1ad208172c5c1ac586daa8c75781379f034d97e50b1a9be", # passport_ref
"sha256:a4f8cb5ee09b29478ac1cc2f468d66e16d3d25f7a229a31d22ad521e11d04d35", # mandate_ref
"sha256:aaee2091799f376ee8cac802ea4920feaa4eca52950488a3e047ff82e6959a21", # policy_bound_ref
"sha256:2a444c629892f44fde1bd004aba9be01dd6cc7fe251eecdd545b82dca9f0bf97", # guardrail_ref (ALLOW)
],
trust_outcome="TRUSTED",
)
Lite vs commercial
| Lite (this package) | Commercial Composite Trust Query | |
|---|---|---|
| Licence | Apache-2.0, open | Commercial OEM |
| Reference | content-addressed trust_query_ref (binding only) |
the same, Falcon-1024 signed verdict |
| Scoring | bring your own | walks the audit chain, checks revocation/reversal/termination |
| Verifier | recompute the binding offline | maintained verifier under asserted jurisdictions |
Adopters (pin → key)
If you build on algovoi-composite-trust-query-lite, pin ==0.1.0, anchor a canonical trust_query_ref vector hash from composite_trust_query_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 composite_trust_query_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. tq-001, tq-002 and tq-003 cap the live decision chain in spend_decision_chain_v1.
Apache-2.0. Additive over the frozen canonicalisation substrate; sole AlgoVoi authorship.
Metadata
Release files for algovoi-composite-trust-query-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_composite_trust_query_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_composite_trust_query_lite-0.1.3-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | algovoi_composite_trust_query_lite-0.1.3-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 199.7 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
2904e6a350d7470f735295e8cb3e1699ed3a1fcf4c82ddfbc4d2e0aaf034be9f
|
|
BLAKE2b-256 checksum How to use checksums |
cb141fa7a91538aa383dc6b4b5e56850b6a2ecf7bb69b61c4b7da3ebc88cd710
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Security for algovoi-composite-trust-query-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.