zanii-certify 0.5.0__tar.gz

zanii_certify-0.5.0/.gitignore

@@ -0,0 +1,15 @@
+node_modules/
+.venv/
+dist/
+__pycache__/
+*.db
+*.db-*
+.env*
+secrets/
+sectrets/
+.data/
+.pytest_cache/
+.ruff_cache/
+*.rar
+*.zip
+*.7z

zanii_certify-0.5.0/LICENSE

@@ -0,0 +1,159 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or Derivative
+          Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or agreed
+      to in writing, Licensor provides the Work (and each Contributor
+      provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES
+      OR CONDITIONS OF ANY KIND, either express or implied, including,
+      without limitation, any warranties or conditions of TITLE,
+      NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2026 Zanii
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

zanii_certify-0.5.0/PKG-INFO

@@ -0,0 +1,145 @@
+Metadata-Version: 2.5
+Name: zanii-certify
+Version: 0.5.0
+Summary: Build and verify Zanii Certify certificates for AI agents: fingerprints, signed certificates, status documents, test suites and the certify command line tool.
+Project-URL: Homepage, https://zanii.agency
+Author-email: Zanii <info@zanii.agency>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: ai-agents,ai-assurance,arabic,certification,ed25519,post-quantum,verifiable-credentials,zanii
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Security :: Cryptography
+Requires-Python: >=3.11
+Requires-Dist: zanii-blackbox<0.24,>=0.23.0
+Requires-Dist: zanii[pq]<0.27,>=0.26.2
+Description-Content-Type: text/markdown
+
+# zanii-certify
+
+Python SDK and `certify` CLI for Zanii Certify fingerprints, signed certificates,
+status, evidence sharing, runtime assurance and scheme governance. Requires Python
+3.11 or newer. Public functions are exported by the `zanii_certify` module; common
+signed formats are checked against the TypeScript SDK (`@zanii/certify` on npm) using
+shared vectors.
+
+## Install
+
+```sh
+pip install zanii-certify
+certify verify cert.json --online https://lab.zanii.agency
+```
+
+Certificate, status and signature checks work on every supported Python. The strict
+text-normalisation policy used to grade test suites pins the Unicode version and
+currently supports Unicode 16 and 17 (Python 3.14 or newer); on an older Python it
+reports the policy as unsupported instead of grading with different Unicode tables.
+
+Paths in backticks below (`spec/...`, `conformance/...`) are files of the Zanii Certify source repository, which is private; the specification documents are available from Zanii on request (info@zanii.agency).
+
+## Use this checkout
+
+From the repository root, install the locked workspace and inspect the current CLI:
+
+```sh
+uv sync --frozen
+uv run certify --help-v2
+```
+
+Save this as `example.py` at the repository root and run `uv run python example.py`.
+It needs no server, network access or signing key:
+
+```python
+from zanii_certify import (
+    build_fingerprint,
+    check_fingerprint,
+    prompt_sha256,
+    runtime_request_hash,
+    sha256_bytes,
+)
+
+fingerprint = build_fingerprint(
+    model="example-model@1",
+    prompt=prompt_sha256("Answer using the approved policy."),
+    tools=None,
+    policy=None,
+    knowledge=None,
+)
+assert check_fingerprint(fingerprint)
+print(fingerprint["id"])
+
+# Commit the exact request body bytes; this hash alone grants no permission.
+body = '{"amount_minor":100,"currency":"USD"}'
+print(runtime_request_hash({
+    "method": "POST",
+    "url": "https://bank.example/payments",
+    "body_sha256": sha256_bytes(body),
+}))
+```
+
+This produces the same two hashes as the
+TypeScript example (`packages/certify/README.md`). Fingerprint inputs contain
+hashes or `None`, rather than raw prompts/documents. Keep the original bytes:
+changing whitespace can change a commitment.
+
+## Verification policy
+
+`verify_certificate(certificate, **options)` is synchronous and returns a dictionary
+with `ok` and `reasons`. Optional checks run when their inputs/policies are supplied;
+an `ok` result alone does not mean every relying-party requirement was checked.
+
+- Supply fresh signed `status` and `revocation_list`, the expected `fingerprint`,
+  and `now` when a reproducible verification time is required.
+- Supply an independently approved `issuer_policy` and corresponding `issuer_doc`.
+  Downloaded metadata cannot nominate trusted keys. Key/PQ changes require local
+  review; `allow_no_pq` cannot override the pinned policy.
+- Supply `pq`/`status_pq` when required. For Level 3, supply the audit plus
+  `trusted_bodies` or an independently rooted `body_register`. Add witness,
+  licence and release policies where required. Strict withdrawal checking uses
+  the withdrawal log and `releases["rejectWithdrawn"] = True`; signed JSON policy
+  field names retain their wire spelling, even in Python.
+
+See the full verify_certificate signature (`python/src/zanii_certify/certificate.py`),
+policy tests (`python/tests/test_verification_policy.py`) and
+certificate contract (`spec/certificate.md`). Legacy optional behavior remains
+for compatibility; choose your relying-party policy explicitly. Offline evidence
+cannot reveal an undisclosed newer checkpoint or revocation.
+
+The CLI is offline by default. `--help-v2` lists current strict-policy, audit,
+witness and release options. `--online` enables bounded retrieval, including
+required PQ material. Accept only exit code 0 when every CLI check is required;
+exit code 2 means not fully checked. See the CLI contract (`spec/cli.md`).
+Python issuer retrieval uses at most four daemon-worker slots; a timed-out
+standard-library request may occupy its slot until it finishes.
+
+## Contracts and limits
+
+| Area | Contract |
+| --- | --- |
+| Fingerprints and certificates | Fingerprint (`spec/fingerprint.md`), certificate (`spec/certificate.md`) |
+| Status and freshness | Status v1/v2 (`spec/status.md`), witnesses (`spec/witness.md`), Bitstring Status List (`spec/bitstring-status.md`), assurance withdrawal (`spec/assurance-status.md`) |
+| Runtime releases, mandates, leases and knowledge proofs | Runtime assurance (`spec/runtime.md`) |
+| Scheme releases, exact text and transitions | Scheme (`spec/scheme.md`), immutable text (`spec/scheme-text.md`), checkpointed log (`spec/scheme-log.md`) |
+| Redacted evidence and inclusion proofs | Evidence sharing (`spec/evidence-share.md`) |
+
+Format-specific byte/count limits bound builders and verifiers. Preserve trusted
+freshness watermarks independently when the contract requires them. An inclusion
+proof establishes commitment, not content truth, ACL permission or quality.
+Node-only Nitro verification, runtime reporter and reference HTTP gateway are
+not exported by this Python package.
+
+## Check changes
+
+Run from the repository root:
+
+```sh
+uv run pytest python/tests
+uv run pytest python/tests/test_verification_policy.py
+uv run ruff check python
+```
+
+Shared vectors (`spec/vectors`) and conformance tests (`conformance`) verify
+the common wire formats and preserve old signed bytes when adding new versions.
+Local SDK tests do not qualify deployment security or capacity; see the
+readiness report (`docs/readiness-report.md`).

zanii_certify-0.5.0/README.md

@@ -0,0 +1,127 @@
+# zanii-certify
+
+Python SDK and `certify` CLI for Zanii Certify fingerprints, signed certificates,
+status, evidence sharing, runtime assurance and scheme governance. Requires Python
+3.11 or newer. Public functions are exported by the `zanii_certify` module; common
+signed formats are checked against the TypeScript SDK (`@zanii/certify` on npm) using
+shared vectors.
+
+## Install
+
+```sh
+pip install zanii-certify
+certify verify cert.json --online https://lab.zanii.agency
+```
+
+Certificate, status and signature checks work on every supported Python. The strict
+text-normalisation policy used to grade test suites pins the Unicode version and
+currently supports Unicode 16 and 17 (Python 3.14 or newer); on an older Python it
+reports the policy as unsupported instead of grading with different Unicode tables.
+
+Paths in backticks below (`spec/...`, `conformance/...`) are files of the Zanii Certify source repository, which is private; the specification documents are available from Zanii on request (info@zanii.agency).
+
+## Use this checkout
+
+From the repository root, install the locked workspace and inspect the current CLI:
+
+```sh
+uv sync --frozen
+uv run certify --help-v2
+```
+
+Save this as `example.py` at the repository root and run `uv run python example.py`.
+It needs no server, network access or signing key:
+
+```python
+from zanii_certify import (
+    build_fingerprint,
+    check_fingerprint,
+    prompt_sha256,
+    runtime_request_hash,
+    sha256_bytes,
+)
+
+fingerprint = build_fingerprint(
+    model="example-model@1",
+    prompt=prompt_sha256("Answer using the approved policy."),
+    tools=None,
+    policy=None,
+    knowledge=None,
+)
+assert check_fingerprint(fingerprint)
+print(fingerprint["id"])
+
+# Commit the exact request body bytes; this hash alone grants no permission.
+body = '{"amount_minor":100,"currency":"USD"}'
+print(runtime_request_hash({
+    "method": "POST",
+    "url": "https://bank.example/payments",
+    "body_sha256": sha256_bytes(body),
+}))
+```
+
+This produces the same two hashes as the
+TypeScript example (`packages/certify/README.md`). Fingerprint inputs contain
+hashes or `None`, rather than raw prompts/documents. Keep the original bytes:
+changing whitespace can change a commitment.
+
+## Verification policy
+
+`verify_certificate(certificate, **options)` is synchronous and returns a dictionary
+with `ok` and `reasons`. Optional checks run when their inputs/policies are supplied;
+an `ok` result alone does not mean every relying-party requirement was checked.
+
+- Supply fresh signed `status` and `revocation_list`, the expected `fingerprint`,
+  and `now` when a reproducible verification time is required.
+- Supply an independently approved `issuer_policy` and corresponding `issuer_doc`.
+  Downloaded metadata cannot nominate trusted keys. Key/PQ changes require local
+  review; `allow_no_pq` cannot override the pinned policy.
+- Supply `pq`/`status_pq` when required. For Level 3, supply the audit plus
+  `trusted_bodies` or an independently rooted `body_register`. Add witness,
+  licence and release policies where required. Strict withdrawal checking uses
+  the withdrawal log and `releases["rejectWithdrawn"] = True`; signed JSON policy
+  field names retain their wire spelling, even in Python.
+
+See the full verify_certificate signature (`python/src/zanii_certify/certificate.py`),
+policy tests (`python/tests/test_verification_policy.py`) and
+certificate contract (`spec/certificate.md`). Legacy optional behavior remains
+for compatibility; choose your relying-party policy explicitly. Offline evidence
+cannot reveal an undisclosed newer checkpoint or revocation.
+
+The CLI is offline by default. `--help-v2` lists current strict-policy, audit,
+witness and release options. `--online` enables bounded retrieval, including
+required PQ material. Accept only exit code 0 when every CLI check is required;
+exit code 2 means not fully checked. See the CLI contract (`spec/cli.md`).
+Python issuer retrieval uses at most four daemon-worker slots; a timed-out
+standard-library request may occupy its slot until it finishes.
+
+## Contracts and limits
+
+| Area | Contract |
+| --- | --- |
+| Fingerprints and certificates | Fingerprint (`spec/fingerprint.md`), certificate (`spec/certificate.md`) |
+| Status and freshness | Status v1/v2 (`spec/status.md`), witnesses (`spec/witness.md`), Bitstring Status List (`spec/bitstring-status.md`), assurance withdrawal (`spec/assurance-status.md`) |
+| Runtime releases, mandates, leases and knowledge proofs | Runtime assurance (`spec/runtime.md`) |
+| Scheme releases, exact text and transitions | Scheme (`spec/scheme.md`), immutable text (`spec/scheme-text.md`), checkpointed log (`spec/scheme-log.md`) |
+| Redacted evidence and inclusion proofs | Evidence sharing (`spec/evidence-share.md`) |
+
+Format-specific byte/count limits bound builders and verifiers. Preserve trusted
+freshness watermarks independently when the contract requires them. An inclusion
+proof establishes commitment, not content truth, ACL permission or quality.
+Node-only Nitro verification, runtime reporter and reference HTTP gateway are
+not exported by this Python package.
+
+## Check changes
+
+Run from the repository root:
+
+```sh
+uv run pytest python/tests
+uv run pytest python/tests/test_verification_policy.py
+uv run ruff check python
+```
+
+Shared vectors (`spec/vectors`) and conformance tests (`conformance`) verify
+the common wire formats and preserve old signed bytes when adding new versions.
+Local SDK tests do not qualify deployment security or capacity; see the
+readiness report (`docs/readiness-report.md`).

zanii_certify-0.5.0/pyproject.toml

@@ -0,0 +1,32 @@
+[project]
+name = "zanii-certify"
+version = "0.5.0"
+description = "Build and verify Zanii Certify certificates for AI agents: fingerprints, signed certificates, status documents, test suites and the certify command line tool."
+readme = "README.md"
+license = "Apache-2.0"
+authors = [{ name = "Zanii", email = "info@zanii.agency" }]
+requires-python = ">=3.11"
+keywords = ["ai-agents", "certification", "verifiable-credentials", "ai-assurance", "ed25519", "post-quantum", "arabic", "zanii"]
+classifiers = [
+  "Development Status :: 4 - Beta",
+  "Intended Audience :: Developers",
+  "Programming Language :: Python :: 3",
+  "Topic :: Security :: Cryptography",
+]
+dependencies = [
+  "zanii[pq]>=0.26.2,<0.27",
+  "zanii-blackbox>=0.23.0,<0.24",
+]
+
+[project.scripts]
+certify = "zanii_certify.cli:main"
+
+[project.urls]
+Homepage = "https://zanii.agency"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/zanii_certify"]