evidencebound-core 0.4.0__tar.gz

evidencebound_core-0.4.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 [yyyy] [name of copyright owner]
+
+   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.

evidencebound_core-0.4.0/PKG-INFO

@@ -0,0 +1,253 @@
+Metadata-Version: 2.4
+Name: evidencebound-core
+Version: 0.4.0
+Summary: Framework-agnostic trust, provenance, verification, and selective-recovery runtime for autonomous AI systems.
+Author: Ruslan Vrublevskyi
+License-Expression: Apache-2.0
+Project-URL: Repository, https://github.com/evidencebound/evidencebound-core
+Project-URL: Issues, https://github.com/evidencebound/evidencebound-core/issues
+Project-URL: Changelog, https://github.com/evidencebound/evidencebound-core/blob/main/CHANGELOG.md
+Project-URL: Documentation, https://github.com/evidencebound/evidencebound-core/blob/main/docs/INTEGRATION.md
+Keywords: ai-safety,agents,provenance,verification,recovery
+Classifier: Development Status :: 3 - Alpha
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: crypto
+Requires-Dist: cryptography>=46; extra == "crypto"
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: ruff>=0.6; extra == "dev"
+Requires-Dist: mypy>=1.10; extra == "dev"
+Requires-Dist: build>=1.2; extra == "dev"
+Requires-Dist: cryptography>=46; extra == "dev"
+Requires-Dist: hypothesis<7,>=6; extra == "dev"
+Dynamic: license-file
+
+# EvidenceBound Core
+
+[![CI](https://github.com/evidencebound/evidencebound-core/actions/workflows/ci.yml/badge.svg)](https://github.com/evidencebound/evidencebound-core/actions/workflows/ci.yml)
+[![Release](https://img.shields.io/github/v/release/evidencebound/evidencebound-core)](https://github.com/evidencebound/evidencebound-core/releases/tag/v0.3.0)
+[![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue)](https://www.python.org/)
+[![License: Apache-2.0](https://img.shields.io/github/license/evidencebound/evidencebound-core)](LICENSE)
+
+## WebMCP Challenge: one human, one release, one capability
+
+A release manager has a simple problem: an AI agent may need permission to perform a controlled release action, but that permission must not survive after the human decision or the evidence behind it changes.
+
+EvidenceBound makes the human decision visible in the WebMCP capability surface itself. The agent starts with three safe tools. It can inspect release state and request approval, but it cannot approve, revoke, correct, or restore its own authority. When a human approves one exact release snapshot, a fourth tool — `execute_authorized_release` — appears. If the human corrects the security evidence or revokes approval, that tool disappears. Execution also re-checks current authority, so a stale retained capability cannot succeed after the decision changes.
+
+**Judge moment:** `3 tools → human approval → 4 tools → human correction/revocation → 3 tools`.
+
+**Live demo:** https://evidencebound.org/webmcp/ · **Judge guide:** [`WEBMCP.md`](WEBMCP.md)
+
+The controlled demo records `externalSideEffect=false`; it does not claim to perform a real external deployment.
+
+---
+
+**EvidenceBound is a framework-agnostic, LLM-independent runtime for binding agent outputs to evidence, provenance and policy; verifying protected state; computing dependency blast radius; and planning fail-closed selective recovery.**
+
+Created and maintained by Ruslan Vrublevskyi.
+
+> Status: **GitHub source release `v0.3.0` published 2026-08-17** from exact commit `2477164acfbdca6a843bf7b2eac5fa21ce9901b2`. The tagged source passed the full Python 3.10–3.13, clean-room, typing/build, benchmark and security CI gates before publication. Current `main` contains additional **Unreleased** hardening, including provider-neutral signed receipts, durable persistence/restart support, and a real Google ADK 2.7.0 lifecycle compatibility lane. PyPI is **not published**. Pre-1.0 API compatibility is not guaranteed.
+
+## Why EvidenceBound?
+
+Agent memory answers “what did the system remember?” EvidenceBound adds “what evidence supported it, which policy governed it, is the historical record intact, is it still applicable, and what must be recomputed if a dependency changes?”
+
+It is **not** a vector database, RAG framework, tracing backend, LLM framework, truth oracle, or consensus system. A cryptographic digest or signature can bind/authenticate bytes under configured trust roots; neither can make a malicious upstream source truthful. A durable database row is likewise not automatically trusted state.
+
+```mermaid
+flowchart LR
+  A[Agent / workflow] --> B[thin adapter]
+  B --> C[EvidenceBound Core]
+  C --> D[Evidence + provenance binding]
+  D --> E[Deterministic verification]
+  E --> F[Policy/version binding]
+  F --> G[Trust graph + invalidation]
+  G --> H[Recovery plan + proof receipt]
+  H --> I{Action gate}
+  I -->|ALLOW| J[Application action]
+  I -->|REVIEW_REQUIRED| K[Review / reverify]
+  I -->|BLOCK| L[Fail closed]
+```
+
+## Install
+
+From a checkout:
+
+```bash
+python -m pip install .
+```
+
+No unconditional runtime dependency is required beyond Python 3.10+. The SQLite reference persistence provider uses Python's stdlib `sqlite3` and therefore adds no third-party dependency.
+
+Optional Ed25519 signed-receipt reference provider:
+
+```bash
+python -m pip install '.[crypto]'
+```
+
+## 5-minute quickstart
+
+```python
+from evidencebound import (
+    EvidenceBound, EvidenceRecord, InvalidationReason,
+    PolicyBinding, ProvenanceRecord,
+)
+
+policy = PolicyBinding("research-policy", "1")
+eb = EvidenceBound(policy=policy)
+
+evidence = [EvidenceRecord(
+    evidence_id="paper-1",
+    payload={"claim": "observed"},
+    provenance=ProvenanceRecord("paper", "doi:10.0000/example"),
+)]
+
+research = eb.checkpoint(
+    agent="researcher",
+    evidence=evidence,
+    output={"summary": "supported"},
+)
+
+decision = eb.verify(research)
+print(decision.action)         # ALLOW for this complete/current snapshot
+print(decision.receipt)        # tamper-evident binding receipt
+
+plan = eb.invalidate(
+    checkpoint_id=research.checkpoint_id,
+    reason=InvalidationReason.EVIDENCE_CHANGED,
+)
+print(plan.reusable)
+print(plan.requires_verification)
+print(plan.recompute)
+```
+
+Run the complete external acceptance scenario:
+
+```bash
+python examples/golden_acceptance.py
+```
+
+It proves the intended sequence: checkpoint → receipt → tamper detection → historical integrity retained while applicability requires review → exact invalidation → consequential action blocked until successful path-specific re-verification.
+
+## Trust semantics
+
+Evidence state and record integrity are separate dimensions.
+
+- `UNCHANGED`: current evidence identity and digest match the protected snapshot.
+- `NEW`: a supplied current evidence ID was absent from the protected snapshot.
+- `CHANGED`: the digest differs. **This does not mean REFUTED.**
+- `STALE`: validity horizon has elapsed when an explicit current time is supplied.
+- `MISSING`: required current evidence is absent or its supplied identity does not match the protected record.
+- `REFUTED`: an upstream verifier explicitly marks evidence refuted.
+
+Current evidence mapping keys must match the contained `EvidenceRecord.evidence_id`; an identity mismatch fails closed rather than being accepted because payload bytes happen to match.
+
+Possible outcomes:
+
+- historical integrity `VERIFIED` + current applicability `VERIFIED` → `ALLOW`;
+- historical integrity `VERIFIED` + changed/stale/new/policy-drift applicability → `REVIEW_REQUIRED`;
+- integrity failure, missing/refuted evidence, identity mismatch, or required provenance loss → `BLOCK`.
+
+## What a receipt proves
+
+The base `ProofReceipt` binds a checkpoint to a deterministic SHA-256 digest under the versioned `EBCJ-1` canonicalization domain. `verify_receipt()` validates receipt metadata and checkpoint binding; `verify_verification_receipt()` additionally binds the supplied historical verification result. Unsigned receipts remain tamper-evident **when retained or anchored independently of mutable checkpoint state**, but they do not authenticate an issuer.
+
+Current `main` also exposes provider-neutral `ReceiptSigner` / `ReceiptVerifier` contracts plus `SignedProofReceipt`, `sign_receipt()` and `verify_signed_receipt()`. The optional Ed25519 provider lives under `evidencebound.providers.ed25519` and is not imported by core. ACTIVE keys may create new signatures; RETIRED keys may verify historical receipts; REVOKED/UNKNOWN keys and unsupported algorithms fail closed. Legacy unsigned receipts remain explicitly `UNSIGNED` and are never silently upgraded.
+
+A valid signature authenticates the signed receipt under the application's configured key identity/trust roots. It does **not** prove upstream truth, provenance honesty, secure key custody, secure time, or legal compliance. See [`docs/SIGNED_RECEIPTS.md`](docs/SIGNED_RECEIPTS.md).
+
+## Durable persistence and restart
+
+Current `main` defines a provider-neutral `PersistenceStore` contract and a stdlib reference implementation at `evidencebound.providers.sqlite.SQLiteStore`.
+
+```python
+from evidencebound.providers.sqlite import SQLiteStore
+
+with SQLiteStore("agent-state.sqlite3") as store:
+    store.commit_bundle(checkpoint, verification_result)
+
+# New process / later restart
+with SQLiteStore("agent-state.sqlite3") as store:
+    graph, verification_by_id = store.load_recovery_state()
+```
+
+Checkpoint, receipt, verification state and an optional replay record are committed as one transaction. A pre-commit interruption rolls the bundle back. On reopen, persisted verification is **not trusted because it was stored**: EvidenceBound reconstructs the checkpoint/receipt/result and re-runs deterministic result binding before the state can feed recovery as reusable.
+
+`SQLiteReplayGuard` preserves equal-payload duplicate detection and conflicting-payload rejection across restart. It remains an idempotency primitive, not an exactly-once guarantee. Unknown/incomplete persistence schemas fail closed; the alpha provider does not silently migrate trust-bearing history.
+
+SQLite is not claimed immutable or authenticated. For attackers able to rewrite both checkpoint and receipt state consistently, use an independent receipt anchor and/or signed receipts with independently protected verification roots as appropriate to the threat model. See [`docs/PERSISTENCE.md`](docs/PERSISTENCE.md).
+
+## Canonicalization
+
+`EBCJ-1` accepts null, booleans, integers, Unicode strings, lists, and string-keyed maps. Maps are sorted, JSON is compact UTF-8, and floats are rejected to avoid cross-runtime ambiguity. This is an EvidenceBound format, **not a claim of RFC 8785 compliance**. See [`SPEC.md`](SPEC.md).
+
+## Recovery
+
+`DependencyGraph` validates IDs/dependencies, rejects cycles, provides deterministic topological ordering, and computes exact descendants.
+
+`plan_recovery()` distinguishes:
+
+- `recompute`: checkpoints in the exact invalidation blast radius;
+- `reusable`: unaffected checkpoints with an `ALLOW` verification result cryptographically bound to the exact checkpoint currently in the graph;
+- `requires_verification`: unaffected state that cannot yet be trusted for reuse;
+- `blocked`: consequential actions that may not proceed.
+
+Re-verification requirements are dependency-path-specific, so an unrelated invalidation does not contaminate an independent branch. `ReplayGuard` provides in-process idempotent duplicate detection; `SQLiteReplayGuard` can persist those semantics across restart. Neither claims exactly-once execution.
+
+## Adapters
+
+Core never imports an agent framework. Included integration seams:
+
+- `evidencebound.adapters.run_guarded` — plain Python callable hook.
+- `evidencebound.adapters.google_adk.AdkCallbackAdapter` — dependency-free Google ADK seam. Current Unreleased `main` also includes `adk_consequential_action_allowed()`, a fail-closed application gate that requires explicit serialized EvidenceBound `ALLOW` callback state.
+
+The maintained compatibility CI currently installs **exactly `google-adk==2.7.0` on Python 3.13** in an isolated job after installing EvidenceBound without integration dependencies. A credential-free synthetic real ADK `BaseAgent`/`Runner` scenario proves runtime `callback_context` keyword invocation, persisted callback state on completed lifecycle, emitted state delta, and blocked consequential state when the async event stream is closed before `after_agent_callback`. This is evidence for the exact tested ADK version, not a blanket compatibility claim for other releases.
+
+See [`docs/INTEGRATION.md`](docs/INTEGRATION.md).
+
+## Verify this checkout
+
+```bash
+python -m pip install -e '.[dev]'
+pytest
+python examples/golden_acceptance.py
+python benchmarks/selective_recovery.py
+python -m compileall -q src examples benchmarks compat
+ruff check .
+mypy src/evidencebound
+python -m build
+```
+
+CI additionally performs an isolated clean-room installation, runtime-dependency assertion, pip-audit, Bandit scan, wheel reinstall/import, the benchmark acceptance scenario, and the isolated exact-version Google ADK compatibility lane. See `.github/workflows/ci.yml` and [`RELEASE_READINESS.md`](RELEASE_READINESS.md).
+
+## Security and non-goals
+
+Read [`THREAT_MODEL.md`](THREAT_MODEL.md) before using EvidenceBound for consequential actions. The library helps detect unsupported/missing/stale/refuted evidence when that state is supplied or derivable; it cannot establish truthfulness of a malicious source, protect a compromised runtime, guarantee safe key custody/immutable storage, or guarantee legal/regulatory compliance.
+
+## Project documents
+
+- [`ARCHITECTURE.md`](ARCHITECTURE.md)
+- [`SPEC.md`](SPEC.md)
+- [`THREAT_MODEL.md`](THREAT_MODEL.md)
+- [`SECURITY.md`](SECURITY.md)
+- [`CONTRIBUTING.md`](CONTRIBUTING.md)
+- [`ROADMAP.md`](ROADMAP.md)
+- [`docs/SIGNED_RECEIPTS.md`](docs/SIGNED_RECEIPTS.md)
+- [`docs/PERSISTENCE.md`](docs/PERSISTENCE.md)
+- [`docs/INTEGRATION.md`](docs/INTEGRATION.md)
+- [`RELEASE_READINESS.md`](RELEASE_READINESS.md)
+- [`FUNDING_READINESS.md`](FUNDING_READINESS.md)
+- [`PREEXISTING_WORK.md`](PREEXISTING_WORK.md)
+- [`LICENSE_DECISION.md`](LICENSE_DECISION.md)
+
+## License
+
+Apache-2.0. See [`LICENSE_DECISION.md`](LICENSE_DECISION.md) for the project-specific rationale and provenance boundary.