agent-evidence-verify 0.5.0__tar.gz

agent_evidence_verify-0.5.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; 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, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   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.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   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. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   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 (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   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 by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Sankalp Gilda
+
+   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.

agent_evidence_verify-0.5.0/MANIFEST.in

@@ -0,0 +1,9 @@
+recursive-include src *.py *.json
+recursive-include examples *.json *.txt *.py *.jsonl *.md *.html *.pub *.err *.bin
+graft examples/brokered-file-write/retained
+recursive-include tests *.py *.json *.zip
+recursive-include scripts *.py *.sh
+recursive-include docs *.md *.json
+recursive-include vectors-source-coverage *.json *.txt *.html *.py *.md
+recursive-include vectors-operand-lineage *.json *.py *.md
+recursive-include vectors-done-checks *.json *.py *.md

agent_evidence_verify-0.5.0/PKG-INFO

@@ -0,0 +1,111 @@
+Metadata-Version: 2.4
+Name: agent-evidence-verify
+Version: 0.5.0
+Summary: Check claims against pinned evidence offline, with replayable decisions
+License-Expression: Apache-2.0
+Project-URL: Documentation, https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/install.md
+Project-URL: Source, https://github.com/probityai/probity/tree/main/packages/agent-evidence-verify
+Project-URL: Issues, https://github.com/probityai/probity/issues
+Project-URL: Agent guide, https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/llms.txt
+Keywords: ai-agents,evidence-verification,provenance,offline,audit
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Information Technology
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Security
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: cryptography<51,>=50.0.2
+Requires-Dist: agent-evidence-vocabulary<0.10,>=0.8.0
+Requires-Dist: pyyaml<7,>=6.0.2
+Provides-Extra: test
+Requires-Dist: pytest<10,>=9.2.0; extra == "test"
+Requires-Dist: hypothesis<7,>=6.170.8; extra == "test"
+Provides-Extra: a2a
+Requires-Dist: a2a-sdk[http-server]==1.3.0; extra == "a2a"
+Requires-Dist: uvicorn==0.54.0; extra == "a2a"
+Dynamic: license-file
+
+# agent-evidence-verify
+
+[![PyPI](https://img.shields.io/pypi/v/agent-evidence-verify.svg)](https://pypi.org/project/agent-evidence-verify/)
+[![Downloads (PePy)](https://static.pepy.tech/badge/agent-evidence-verify)](https://pepy.tech/projects/agent-evidence-verify)
+
+An offline verifier that decides whether a claim holds against evidence bytes the consumer pinned, with adapters for source passages, operand lineage, authority captures, bounded absence and spend journals.
+
+It's for auditors, incident reviewers and relying parties who receive a claim about an AI system and need a decision they can replay, not a report they have to trust.
+
+Install the released package: `pip install agent-evidence-verify==0.5.0`.
+
+## Quick start
+
+Check a sample claim with the released package. You need Python 3.12 or newer and [uv](https://docs.astral.sh/uv/); nothing to clone, and a cold run takes about seven seconds. Version 0.5.0 ships the sample case and policies inside the wheel:
+
+```sh
+samples="$(uvx --from agent-evidence-verify==0.5.0 python -c 'import importlib.resources as r; print(r.files("agent_evidence_verify") / "samples")')"
+uvx agent-evidence-verify==0.5.0 "$samples/case.json" --policy "$samples/policy-june.json"
+```
+
+It prints a decision packet that opens:
+
+```text
+Probity decision packet v1
+Case: "source-coverage-demo"
+Claim: source_text_coverage/v1
+Decision: contradicted
+Reason: selected_span_missing_from_record
+Policy SHA-256: dfda1551714f92702169d1411af6b0bfeee54732f934ce71265534af775fa388
+```
+
+A selected passage is in the source capture but missing from the stored report. The packet goes on to list every artifact binding and check. Swap in `policy-april.json` for `not_established`, or `case-complete.json` with `policy-complete.json` for `supported`. To run from a pinned source checkout instead, see [Install a pinned version](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/install.md#run-the-source-quick-start).
+
+## Use the decision in a check
+
+All valid decisions exit 0, including `contradicted` and `not_established`. Exit 2 reports invalid input without a verdict. Require support for this claim by reading `decision`:
+
+```sh
+uvx agent-evidence-verify==0.5.0 "$samples/case.json" \
+  --policy "$samples/policy-june.json" --json > decision.json &&
+python3 - <<'PY'
+import json
+
+with open("decision.json") as stream:
+    result = json.load(stream)
+print(result["decision"], result["reason"])
+raise SystemExit(0 if result["decision"] == "supported" else 1)
+PY
+```
+
+This guard prints `contradicted selected_span_missing_from_record` and exits 1. `supported` means the stated claim passes the pinned policy's checks. Your application still owns authorization.
+
+## Status
+
+Version 0.5.0 is on PyPI and ships the sample inputs used above. See [release instructions](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/RELEASING.md) for checked artifacts and the [changelog](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/CHANGELOG.md) for what each release changed. Fourteen adapters ship in 0.5.0: `brokered_file_write/v1`, `source_text_coverage/v1`, `operand_lineage/v1`, `authority_anchor/v1`, `event_absence/v1`, `event_absence/v2`, `spend_reservation/v1`, the done-receipt checks for coding agents `protected_paths/v1`, `acceptance_observed/v1`, `tool_claim_match/v1`, `completion_claim/v1` and `probe_observed/v1`, `adversarial_execution_evidence/v1`, and `done_receipt/v2`, which derives a done receipt's two verdicts again from them: whether the work is done and whether the agent gamed the process. Each decision is `supported`, `contradicted` or `not_established`. The verifier checks supplied bytes only: it does not fetch URLs or authenticate the authority a policy names.
+
+## Documentation
+
+| page | read it for |
+| --- | --- |
+| [Start a project](https://github.com/new?template_name=evidence-starter&template_owner=probityai) | a template that checks an observer-recorded write with this verifier, pinned and in CI |
+| [Install a pinned version](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/install.md) | install outside the source checkout and replay three sample decisions |
+| [Choose a claim check](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/recipes.md) | select a task from checked recipes and retrieve exact commands and input digests |
+| [Select a consumer adapter](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/adapter-api.md) | supply exact adapter versions through adjudication, bundle creation and replay |
+| [Check a customer offer](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/customer-support-action.md) | compare a draft with raw company records and an exact manager approval |
+| <a name="run"></a><a name="inputs-and-decisions"></a>[Running the verifier](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/running.md) | every example command, the case and policy inputs, and what each decision means |
+| <a name="share-a-replayable-decision"></a><a name="index-decisions-and-disputes"></a>[Replayable decisions and the index](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/bundles-and-index.md) | ZIP bundles, replay, and the local index of decisions, challenges and supersessions |
+| <a name="operand-lineage"></a><a name="authority-anchor"></a><a name="event-absence"></a>[Adapters](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/adapters.md) | what operand lineage, authority anchor and event absence check, and what they leave to the consumer |
+| [Done-receipt checks](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/done-receipt.md) | check a coding agent's "done" against protected paths, an outside acceptance grade and its claimed command runs, with vantage and witness scope on every verdict |
+| [Spend reservations](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/spend-reservation.md) | replay a pinned budget journal, refuse dispatch without an affordable reservation, and keep pending calls charged |
+| [Observation vantage](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/observation-vantage.md) | select the producer and observation scope, replay bounded absence, and operate a witness with separate keys and retained heads |
+| [Adapter plan](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/architecture.md) | the architecture and the adapters planned next |
+| [A2A server and client](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/a2a.md) | send raw case bytes to an operator-configured verifier, or read a pinned Lab record |
+| [Source coverage](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/vectors-source-coverage/README.md), [operand-lineage](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/vectors-operand-lineage/README.md) and [done-check vectors](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/vectors-done-checks/README.md) | conformance cases with pinned bytes and expected decisions |
+
+## License
+
+Apache-2.0.

agent_evidence_verify-0.5.0/README.md

@@ -0,0 +1,78 @@
+# agent-evidence-verify
+
+[![PyPI](https://img.shields.io/pypi/v/agent-evidence-verify.svg)](https://pypi.org/project/agent-evidence-verify/)
+[![Downloads (PePy)](https://static.pepy.tech/badge/agent-evidence-verify)](https://pepy.tech/projects/agent-evidence-verify)
+
+An offline verifier that decides whether a claim holds against evidence bytes the consumer pinned, with adapters for source passages, operand lineage, authority captures, bounded absence and spend journals.
+
+It's for auditors, incident reviewers and relying parties who receive a claim about an AI system and need a decision they can replay, not a report they have to trust.
+
+Install the released package: `pip install agent-evidence-verify==0.5.0`.
+
+## Quick start
+
+Check a sample claim with the released package. You need Python 3.12 or newer and [uv](https://docs.astral.sh/uv/); nothing to clone, and a cold run takes about seven seconds. Version 0.5.0 ships the sample case and policies inside the wheel:
+
+```sh
+samples="$(uvx --from agent-evidence-verify==0.5.0 python -c 'import importlib.resources as r; print(r.files("agent_evidence_verify") / "samples")')"
+uvx agent-evidence-verify==0.5.0 "$samples/case.json" --policy "$samples/policy-june.json"
+```
+
+It prints a decision packet that opens:
+
+```text
+Probity decision packet v1
+Case: "source-coverage-demo"
+Claim: source_text_coverage/v1
+Decision: contradicted
+Reason: selected_span_missing_from_record
+Policy SHA-256: dfda1551714f92702169d1411af6b0bfeee54732f934ce71265534af775fa388
+```
+
+A selected passage is in the source capture but missing from the stored report. The packet goes on to list every artifact binding and check. Swap in `policy-april.json` for `not_established`, or `case-complete.json` with `policy-complete.json` for `supported`. To run from a pinned source checkout instead, see [Install a pinned version](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/install.md#run-the-source-quick-start).
+
+## Use the decision in a check
+
+All valid decisions exit 0, including `contradicted` and `not_established`. Exit 2 reports invalid input without a verdict. Require support for this claim by reading `decision`:
+
+```sh
+uvx agent-evidence-verify==0.5.0 "$samples/case.json" \
+  --policy "$samples/policy-june.json" --json > decision.json &&
+python3 - <<'PY'
+import json
+
+with open("decision.json") as stream:
+    result = json.load(stream)
+print(result["decision"], result["reason"])
+raise SystemExit(0 if result["decision"] == "supported" else 1)
+PY
+```
+
+This guard prints `contradicted selected_span_missing_from_record` and exits 1. `supported` means the stated claim passes the pinned policy's checks. Your application still owns authorization.
+
+## Status
+
+Version 0.5.0 is on PyPI and ships the sample inputs used above. See [release instructions](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/RELEASING.md) for checked artifacts and the [changelog](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/CHANGELOG.md) for what each release changed. Fourteen adapters ship in 0.5.0: `brokered_file_write/v1`, `source_text_coverage/v1`, `operand_lineage/v1`, `authority_anchor/v1`, `event_absence/v1`, `event_absence/v2`, `spend_reservation/v1`, the done-receipt checks for coding agents `protected_paths/v1`, `acceptance_observed/v1`, `tool_claim_match/v1`, `completion_claim/v1` and `probe_observed/v1`, `adversarial_execution_evidence/v1`, and `done_receipt/v2`, which derives a done receipt's two verdicts again from them: whether the work is done and whether the agent gamed the process. Each decision is `supported`, `contradicted` or `not_established`. The verifier checks supplied bytes only: it does not fetch URLs or authenticate the authority a policy names.
+
+## Documentation
+
+| page | read it for |
+| --- | --- |
+| [Start a project](https://github.com/new?template_name=evidence-starter&template_owner=probityai) | a template that checks an observer-recorded write with this verifier, pinned and in CI |
+| [Install a pinned version](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/install.md) | install outside the source checkout and replay three sample decisions |
+| [Choose a claim check](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/recipes.md) | select a task from checked recipes and retrieve exact commands and input digests |
+| [Select a consumer adapter](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/adapter-api.md) | supply exact adapter versions through adjudication, bundle creation and replay |
+| [Check a customer offer](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/customer-support-action.md) | compare a draft with raw company records and an exact manager approval |
+| <a name="run"></a><a name="inputs-and-decisions"></a>[Running the verifier](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/running.md) | every example command, the case and policy inputs, and what each decision means |
+| <a name="share-a-replayable-decision"></a><a name="index-decisions-and-disputes"></a>[Replayable decisions and the index](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/bundles-and-index.md) | ZIP bundles, replay, and the local index of decisions, challenges and supersessions |
+| <a name="operand-lineage"></a><a name="authority-anchor"></a><a name="event-absence"></a>[Adapters](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/adapters.md) | what operand lineage, authority anchor and event absence check, and what they leave to the consumer |
+| [Done-receipt checks](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/done-receipt.md) | check a coding agent's "done" against protected paths, an outside acceptance grade and its claimed command runs, with vantage and witness scope on every verdict |
+| [Spend reservations](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/spend-reservation.md) | replay a pinned budget journal, refuse dispatch without an affordable reservation, and keep pending calls charged |
+| [Observation vantage](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/observation-vantage.md) | select the producer and observation scope, replay bounded absence, and operate a witness with separate keys and retained heads |
+| [Adapter plan](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/architecture.md) | the architecture and the adapters planned next |
+| [A2A server and client](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/docs/a2a.md) | send raw case bytes to an operator-configured verifier, or read a pinned Lab record |
+| [Source coverage](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/vectors-source-coverage/README.md), [operand-lineage](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/vectors-operand-lineage/README.md) and [done-check vectors](https://github.com/probityai/probity/blob/main/packages/agent-evidence-verify/vectors-done-checks/README.md) | conformance cases with pinned bytes and expected decisions |
+
+## License
+
+Apache-2.0.

agent_evidence_verify-0.5.0/docs/RELEASING.md

@@ -0,0 +1,89 @@
+# Release a checked Python distribution
+
+PyPI 0.5.0 is the latest published release and the source is 0.5.0. The
+release carries the eight source-coverage inputs as package resources, added in
+source 0.1.1, and reads DSSE envelopes and completion receipts; the
+[changelog](../CHANGELOG.md) lists every change. The sample inputs remain authored
+synthetic records, not an outside run or a consumer's authority choice.
+
+## Read the installed sample
+
+Build and check the wheel with the release workflow before using this recipe.
+From the source root, install the checked artifact into a separate environment:
+
+```sh
+uv venv verify-env --python 3.12
+uv pip install --python verify-env/bin/python dist/agent_evidence_verify-0.5.0-py3-none-any.whl
+```
+
+Run Python from that environment. The data comes from the installed package:
+
+```python
+import json
+from importlib.resources import files
+from pathlib import Path
+from tempfile import TemporaryDirectory
+
+from agent_evidence_verify import adjudicate
+
+with TemporaryDirectory() as directory:
+    root = Path(directory)
+    for item in files("agent_evidence_verify.samples").iterdir():
+        if item.name.endswith((".json", ".html", ".txt")):
+            (root / item.name).write_bytes(item.read_bytes())
+    result = adjudicate(
+        json.loads((root / "case.json").read_bytes()),
+        json.loads((root / "policy-june.json").read_bytes()),
+        root,
+    )
+print(result["decision"], result["reason"])
+```
+
+It prints `contradicted selected_span_missing_from_record`. The installed CLI
+and API use the same inputs and decisions. The April policy returns
+`not_established` with `witness_outside_source_window`. The complete report
+returns `supported` with `all_selected_spans_present`. Valid decisions exit 0;
+malformed input exits 2 without a verdict. A consumer gate must read `decision`.
+
+`scripts/check-installed.py` exercises all three results through the installed
+API and CLI from an outside directory. It also checks malformed input. It needs
+no source checkout for its sample data.
+
+## Build and publish
+
+The workspace's [release process](../../../docs/architecture/MONOREPO.md#releases) builds and
+publishes this package. The shared `python-build.yml` workflow builds it on every pull request that
+touches it, with the hash-pinned tools in the root `requirements-release.lock`. It runs this
+member's `scripts/check-artifacts.py`, `scripts/check-artifacts-controls.py`,
+`scripts/check-installed.py` and `scripts/build-recipes.py --check` against the built files, and
+retains input hashes, the source commit, install reports and consumer results. These are build
+checks, not outside adoption.
+
+The release-tool lock selects setuptools 84.0.0. The source backend requires
+setuptools 77.0.3 or later for its SPDX license metadata, so compatible existing
+build environments do not have to use the release toolchain's exact version.
+
+The recipe index binds the implementation and fixture bytes, and the
+install-relevant keys of the package manifest (build system, name, version,
+Python requirement, runtime dependencies, scripts and setuptools layout).
+A change to an optional extra, such as a dependency-bot bump of the `a2a`
+pin, does not make it stale. After changing a bound input, run
+`uv run --directory packages/agent-evidence-verify python scripts/build-recipes.py`
+from the repository root and retain its generated files.
+
+A release is a non-prerelease GitHub release tagged `agent-evidence-verify-vX.Y.Z` on a commit of main,
+with `X.Y.Z` equal to this `pyproject.toml` version. `release.yml` publishes the files that run built
+and checked, with a GitHub build attestation and PyPI attestations, through the PyPI trusted publisher
+with owner `probityai`, repository `probity`, workflow `release.yml` and environment
+`pypi`. Releases 0.1.0 and 0.1.1 used tags `v0.1.0` and `v0.1.1`, which stay as they are.
+
+The root release-tool lock is regenerated from the repository root with:
+
+```sh
+uv pip compile --python-version 3.12 --generate-hashes --no-header --no-annotate \
+  requirements-release.in --output-file requirements-release.lock
+```
+
+Keep existing package versions and tags immutable. Publish changed artifact
+contents as a new version. Update current install instructions after the actual
+registry release; preserve historical tested source pins and input digests.

agent_evidence_verify-0.5.0/docs/a2a.md

@@ -0,0 +1,63 @@
+# A2A server and client
+
+The optional A2A interface uses the official Python SDK 1.2.1 and protocol 1.0 JSON-RPC. It calls the same adjudicator as `agent-evidence-verify` and returns its exact JSON decision bytes plus a readable packet.
+
+## Run a case
+
+From a pinned checkout:
+
+```sh
+uv sync --frozen --extra a2a
+uv run --frozen --extra a2a probity-a2a \
+  --policy examples/source-coverage/policy-june.json \
+  --artifact-root examples/source-coverage
+```
+
+In another terminal:
+
+```sh
+uv run --frozen --extra a2a probity-a2a-client verify \
+  examples/source-coverage/case.json \
+  --policy examples/source-coverage/policy-june.json
+```
+
+The client checks the agent card, sends the original case bytes, reads the completed task back and checks the result bindings. This example returns the existing source-coverage fixture's `contradicted` decision.
+
+The server owns the policy and evidence directory. The caller supplies a case, its byte length and SHA-256, and the expected consumer policy digest. The server admits raw JSON before adjudication, so duplicate keys and non-JSON numbers stay visible. URI parts, caller-selected directories and rewritten byte bindings are refused. Invalid input produces a protocol error; the client exits 2 without a verdict.
+
+## Read a Lab record
+
+Retain a register from a pinned [Atlas commit](https://github.com/probityai/agent-evidence/tree/main/site), then record its exact SHA-256. Add it to the server configuration:
+
+```sh
+uv run --frozen --extra a2a probity-a2a \
+  --policy examples/source-coverage/policy-june.json \
+  --artifact-root examples/source-coverage \
+  --lab-register /srv/probity/lab-register.json \
+  --lab-register-sha256 YOUR_RETAINED_REGISTER_SHA256
+```
+
+The client selects a record ID from that register:
+
+```sh
+uv run --frozen --extra a2a probity-a2a-client lab-record E6-observer-admission \
+  --register-sha256 YOUR_RETAINED_REGISTER_SHA256
+```
+
+The response retains the publisher's record, operator, source revisions, review state and executed scope. Reading a record does not rerun its study. The server reads its configured files only.
+
+## Discover and operate it
+
+The server listens on `127.0.0.1:41241`. It serves the agent card at `/.well-known/agent-card.json`, JSON-RPC at `/a2a/jsonrpc` and a short discovery file at `/llms.txt`. The card advertises only the configured skills and protocol 1.0; this interface does not enable the SDK's 0.3 compatibility routes.
+
+Requests are bounded to 384 KiB, with a 256 KiB raw case limit. Four assessments run at a time; the CLI admits up to 16 concurrent connections. The latest 128 completed tasks last for the current process. Save returned decision bytes with their source and policy bindings for retained evidence.
+
+For a maintained host process, install the pinned checkout at `/opt/agent-evidence-verify`, create a `probity` service account and put its policy and evidence under `/srv/probity`. Install [the service unit](../deployment/probity-a2a.service) after changing those operator-owned paths. It uses the locked optional dependencies and the same tested server command. Put an authenticated gateway in front for shared access and qualify its POST route before publishing its URL.
+
+Run the transport and existing verifier checks with:
+
+```sh
+uv run --frozen --extra test --extra a2a pytest
+```
+
+The transport tests start a real loopback HTTP server and use the official SDK client. They compare decision bytes with the existing examples and exercise task readback, admission failures, policy mismatches and a synthetic publisher-record round trip. The existing vector suites keep their own source pins and scopes.

agent_evidence_verify-0.5.0/docs/adapter-api.md

@@ -0,0 +1,75 @@
+# Select an adapter for one consumer
+
+Use the Python API to supply an additional claim adapter for one call:
+
+```python
+from agent_evidence_verify import adjudicate
+from your_application.checks import check_selected_claim
+
+decision = adjudicate(
+    case,
+    consumer_policy,
+    artifact_root,
+    adapters={"company_claim/v1": check_selected_claim},
+)
+```
+
+The policy selects the exact `claim_type` in its case assessment. An adapter
+for `company_claim/v1` cannot handle a request for `company_claim/v2` unless the
+consumer supplies that version separately. The kernel does not infer aliases,
+import plugins, or select code from a case or policy.
+
+The keyword-only `adapters` argument must be a mapping from names to callables.
+Names use `name/vN`: an ASCII letter followed by ASCII letters, digits,
+underscores, dots or hyphens, then `/v` and a positive decimal version. A leading
+zero is invalid. Each callback accepts `(case, policy, artifact_root)`.
+
+The kernel snapshots the existing registry and the supplied mapping before it
+reads the claim selection. It rejects collisions with registered claim types
+and reserved built-in names. It does not change either mapping. A selection
+affects only that call. The legacy `agent_evidence_verify.core.ADAPTERS` dictionary
+remains available for existing callers; changes to that dictionary affect
+later snapshots.
+
+An adapter returns `schema_version: probity-decision/v1`, matching `case_id`
+and `claim_type`, a `decision`, a `reason`, a `scope` object and a `checks` list.
+Decisions are `supported`, `contradicted` or `not_established`. The kernel checks
+the common envelope and adds the SHA-256 binding to the consumer policy.
+The adapter must validate its own evidence contract, required checks and policy
+rules. A policy hash does not prove that the adapter applied those rules.
+
+The callback receives deep copies of the case and policy. The kernel captures
+their JSON bytes and the policy digest before the callback. A callback that
+changes either control value raises `CaseError`, even if it returns a valid
+decision envelope. The caller's case and policy remain intact. This check
+covers control values, including artifact selectors, rather than changes to
+external files or other process state.
+
+Malformed selections and invalid envelopes raise `CaseError` without a
+decision. Missing evidence can produce `not_established` only when the selected
+adapter defines that valid evidence state.
+
+## Carry the selection through a bundle
+
+Supply the same explicit mapping when you create and replay a bundle:
+
+```python
+from pathlib import Path
+from agent_evidence_verify.bundle import create_bundle, replay_bundle
+
+selected = {"company_claim/v1": check_selected_claim}
+bundle_path = Path("decision.zip")
+create_bundle(case_path, policy_path, bundle_path, adapters=selected)
+replayed = replay_bundle(bundle_path, adapters=selected)
+```
+
+The bundle carries the case, policy, artifact bytes and decision. It does not
+carry executable adapter code. The recipient selects and pins that code
+separately. A bundle with an additional claim type cannot replay without the
+matching explicit adapter selection.
+
+Callbacks are trusted Python code. This API does not authenticate callbacks,
+establish evidence provenance or isolate code. Select them in application code,
+outside producer-supplied records. CLI and bundle entry points do not inherit a
+call's adapter mapping automatically. The CLI does not load additional adapters
+from record fields, archive members or module names.