Truquence
Check whether supplied authorization, recovery and completion evidence agrees with a synthetic action contract before accepting an action.
Quick start
Requires Git, Python 3.10+ with venv/pip and a POSIX shell. Setup may fetch setuptools; samples run offline without an account.
git clone https://github.com/cplj/truquence-public.git
cd truquence-public
python3 -m venv .venv && . .venv/bin/activate && python3 -m pip install .
TQ_EXAMPLES="$(python3 -c 'import actioncontract; from pathlib import Path; print(Path(actioncontract.__file__).parent)')"
TQ_OUT="$(mktemp -d)"
truquence accept --contract "$TQ_EXAMPLES/contracts/synthetic.json" --results "$TQ_EXAMPLES/samples/sw.json" "$TQ_EXAMPLES/samples/ax.json" "$TQ_EXAMPLES/samples/ks.json" --out "$TQ_OUT/acceptance"
Actual sample output (JSON excerpt):
{"status":"PASS","counts":{"PASS":3,"FAIL":0,"UNKNOWN":0}}
Writes stdout JSON, $TQ_OUT/acceptance.json and .md. Hand-authored synthetic results do not prove external execution.
For AI agents
Run the commands above; replace all four input paths for your own evidence. --results order and JSON check keys: authorization=signwarden, recovery=axiocairn, completion=kinesift.
Exit 0 PASS, 1 FAIL, 2 UNKNOWN, 3 output/signing error; argparse usage errors also exit 2. FAIL and UNKNOWN block acceptance. Inspect status, findings and each action's checks; never infer retry permission.
Common errors
externally-managed-environmentor command missing: activate.venvand repeat installation there.- Missing venv/pip or old Python: provide Python 3.10+ with venv/pip.
- Missing/invalid input: correct paths in
inputs/findings, then rerun. - Output exists: retain partial files, reconcile them, then choose a fresh prefix.
Metadata
Release files for truquence 0.2.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 | Provenance | |
|---|---|---|---|---|
| truquence-0.2.0.tar.gz | 63.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| truquence-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 100.7 kB
Release files / truquence-0.2.0.tar.gz
| Download URL | truquence-0.2.0.tar.gz |
|---|---|
| Size | 63.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
738ff8b0a99d752c241c229e72729c5b9b893889e9cd07339029c1b135d95c8a
|
|
BLAKE2b-256 checksum How to use checksums |
2e8137e493fa1d0d82160d13bd51719b16ba7572367c1af640a4c1ec99803565
|
| 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 20, 2026.
Transparency logRelease files / truquence-0.2.0-py3-none-any.whl
| Download URL | truquence-0.2.0-py3-none-any.whl |
|---|---|
| Size | 37.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b8918bb09e4896f49f29e31ba359ac1285afe5701634e0e04efd556e6815114e
|
|
BLAKE2b-256 checksum How to use checksums |
d77059e72cf10d3d9fc027f31f8d383159eeebf66818dfbd032754d16e03d695
|
| 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 20, 2026.
Transparency logSecurity for truquence 0.2.0
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for truquence-0.2.0.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 Oct 20, 2026.
Transparency logA 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.