lethe-delete 0.1.0__tar.gz

lethe_delete-0.1.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 BlueTier Operations
+
+   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.

lethe_delete-0.1.0/PKG-INFO

@@ -0,0 +1,209 @@
+Metadata-Version: 2.4
+Name: lethe-delete
+Version: 0.1.0
+Summary: The forget button for AI — provable data-subject deletion for AI memory, with signed deletion certificates.
+Project-URL: Repository, https://github.com/bluetieroperations-create/lethe
+Project-URL: Documentation, https://github.com/bluetieroperations-create/lethe/blob/main/docs/m2m.md
+Keywords: gdpr,ccpa,dsar,right-to-be-forgotten,deletion,vector-database,rag,ai-memory,mcp,compliance
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Security
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: psycopg[binary]>=3.1
+Requires-Dist: cryptography>=42
+Requires-Dist: click>=8.1
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: jsonschema>=4.21; extra == "dev"
+Requires-Dist: mcp>=1.9; extra == "dev"
+Provides-Extra: mcp
+Requires-Dist: mcp>=1.9; extra == "mcp"
+Requires-Dist: jsonschema>=4.21; extra == "mcp"
+Dynamic: license-file
+
+# Lethe — the forget button for AI
+
+**Everyone built AI memory. Nobody built the provable delete.** Lethe deletes a
+person's data from your AI memory (vector store, RAG index, caches, logs) on a
+GDPR/CCPA request — and hands you a **signed certificate** proving it happened.
+
+Self-hosted: Lethe runs inside *your* infrastructure. The tool that erases your
+data never becomes a new place your data goes.
+
+> **Status:** v0.1, early but real. Connectors: **pgvector** + **Pinecone**.
+> The full delete loop is tested end-to-end against real Postgres (pgvector);
+> the Pinecone connector is unit-tested against a mock `Index`, not live
+> Pinecone. Hardened through four rounds of adversarial self-review (internal,
+> not third-party). Not yet on PyPI.
+
+---
+
+## Why
+
+GDPR **Article 17** (right to erasure) covers personal data in agent memory —
+conversation history, retrieved chunks, **and embeddings**. Fines reach 4% of
+global revenue, and the EU's data-protection authorities are actively auditing
+deletion (the EDPB's 2026 sweep checked 764 organizations and found "lack of
+automated deletion mechanisms" almost everywhere). Meanwhile *no vector
+database offers provable deletion* — teams hand-roll it.
+
+If you sell AI to enterprises, you've probably hit the sharper version: a
+customer's security review asks *"prove you can delete a user's data from your
+AI,"* and you can't. Lethe is the answer you hand them.
+
+## How it works
+
+```
+tag(subject → record)  →  forget(subject)  →  delete from your stores
+                                            →  verify the records are gone
+                                            →  signed deletion certificate
+                                            →  tamper-evident audit entry
+```
+
+You never have to remember to call `tag` everywhere: wrap your vector store
+once and writes tag themselves.
+
+## Quickstart (drop-in)
+
+```bash
+pip install -e .            # from source for now (PyPI soon)
+lethe keygen --out lethe_key.bin     # one-time: your signing key (prints the public key)
+export DATABASE_URL=...              # your own Postgres
+export LETHE_SALT=...                # a secret; pseudonymizes subjects in the ledger
+lethe init-db                        # creates Lethe's ledger + audit tables
+```
+
+Wire Lethe to your store, then **wrap your vector store** so every write is
+tagged for deletion:
+
+```python
+import os, psycopg
+from lethe import Lethe
+from lethe.ledger import Ledger
+from lethe.audit import AuditLog
+from lethe.signing import Signer
+from lethe.connectors.pgvector import PgVectorConnector
+from lethe.integrations.langchain import LetheVectorStore
+
+conn = psycopg.connect(os.environ["DATABASE_URL"])
+lethe = Lethe(
+    ledger=Ledger(conn),
+    audit=AuditLog(conn),
+    signer=Signer.from_private_bytes(open("lethe_key.bin", "rb").read()),
+    connectors={"pgvector": PgVectorConnector(conn)},
+    salt=os.environ["LETHE_SALT"],
+)
+
+# Wrap once. Declare which metadata field names the data subject.
+store = LetheVectorStore(
+    my_vectorstore, lethe,            # any LangChain-style store
+    store="pgvector", namespace="docs",
+    subject_key="user_id",
+    id_key="doc_id",                  # recommended: bind ids from metadata
+)
+
+# Use it like a normal vector store — tagging happens automatically.
+store.add_documents([Document(page_content="...",
+                              metadata={"user_id": "alice@example.com",
+                                        "doc_id": "doc-123"})])
+```
+
+When a deletion request comes in:
+
+```python
+cert = lethe.forget("alice@example.com")   # deletes everywhere + returns the certificate
+```
+
+Verify a certificate (pin the operator's *published* public key — a certificate
+that vouches for itself proves nothing):
+
+```python
+from lethe.certificate import verify_certificate
+assert verify_certificate(cert, trusted_public_key=PUBLISHED_PUBKEY)
+```
+
+## The certificate
+
+Ed25519-signed, tamper-evident, independently verifiable. It states exactly what
+happened and **scopes its claim honestly** — *"deleted across these retrieval
+layers and verified absent,"* never "perfectly erased everywhere" (backups and
+model weights are out of scope by definition). `verified_absent` means Lethe
+re-queried the configured endpoint immediately after deleting and saw the
+records gone *at issue time* — it is not a guarantee against read replicas,
+query caches, or asynchronous propagation (notably Pinecone, whose deletes are
+eventually consistent).
+
+```json
+{
+  "all_verified": true,
+  "records_deleted": 2,
+  "layers": [{"store": "pgvector", "namespace": "docs",
+              "deleted_count": 2, "verified_absent": true, "erased": true}],
+  "claim": "Deleted across the listed retrieval layers and verified absent. ...",
+  "signature": "…", "public_key": "…"
+}
+```
+
+## CLI
+
+| Command | Purpose |
+|---|---|
+| `lethe keygen --out KEY` | Create the Ed25519 signing key (prints the public key to publish) |
+| `lethe init-db` | Create Lethe's ledger + audit tables in your Postgres |
+| `lethe forget SUBJECT` | Delete a subject everywhere; prints the signed certificate |
+| `lethe verify CERT --public-key PUB` | Verify a certificate against the operator's published key |
+| `lethe audit-head` | Print the audit-log tip hash (record it out-of-band) |
+| `lethe verify-audit --expected-head H` | Detect tampering/truncation of the audit log |
+
+## For AI agents (MCP)
+
+Lethe ships an MCP server so autonomous agents can execute provable deletion
+and verify certificates machine-to-machine:
+
+    pip install "lethe-delete[mcp]"
+    lethe-mcp
+
+Destructive deletes are two-step (preview → confirm token → forget), and any
+agent can verify a certificate with zero infrastructure (you still need the
+operator's published public key to pin against). Full guide:
+[docs/m2m.md](docs/m2m.md).
+
+## Security model & honest limits
+
+- **Self-hosted.** The SDK and the provenance ledger run in your own Postgres.
+  Lethe-the-project never sees your data. The salt stays in your app.
+- **No raw PII in the ledger.** Subjects are stored as HMAC-SHA256 hashes.
+- **Verify with a pinned key.** An unpinned certificate check only proves
+  internal consistency; always pin your published public key.
+- **`verified_absent` is a point-in-time re-query, not a replication proof.**
+  For eventually-consistent stores (Pinecone) a delete may not have propagated
+  to every replica at issue time. pgvector verifies read-your-writes on one
+  connection; a read-replica DSN would reintroduce the gap.
+- **Audit truncation needs an out-of-band head.** Mid-chain edits are caught
+  automatically; detecting deletion of the *most recent* entries requires
+  recording `lethe audit-head` out-of-band and checking `verify-audit
+  --expected-head`.
+- **Coverage = what flows through Lethe.** Writes that bypass the wrapper/`tag`
+  aren't tracked. Wrap your store, or tag explicitly.
+- **Pre-existing data** (written before you adopted Lethe) needs retroactive
+  discovery — on the roadmap, not in v0.1.
+- **Not erasure from backups or model weights.** Out of scope by design; the
+  certificate says so.
+
+## Connectors
+
+- **pgvector** (and any Postgres table) — `PgVectorConnector`
+- **Pinecone** — `PineconeConnector` (pass your `Index`). Note: Pinecone
+  deletes are eventually consistent, so `verified_absent` is asserted at issue
+  time against the queried endpoint, not proven across replicas.
+- Roadmap: Weaviate, Qdrant, Redis, conversation logs.
+
+## License
+
+[Apache-2.0](LICENSE) — permissive, with an explicit patent grant.

lethe_delete-0.1.0/README.md

@@ -0,0 +1,180 @@
+# Lethe — the forget button for AI
+
+**Everyone built AI memory. Nobody built the provable delete.** Lethe deletes a
+person's data from your AI memory (vector store, RAG index, caches, logs) on a
+GDPR/CCPA request — and hands you a **signed certificate** proving it happened.
+
+Self-hosted: Lethe runs inside *your* infrastructure. The tool that erases your
+data never becomes a new place your data goes.
+
+> **Status:** v0.1, early but real. Connectors: **pgvector** + **Pinecone**.
+> The full delete loop is tested end-to-end against real Postgres (pgvector);
+> the Pinecone connector is unit-tested against a mock `Index`, not live
+> Pinecone. Hardened through four rounds of adversarial self-review (internal,
+> not third-party). Not yet on PyPI.
+
+---
+
+## Why
+
+GDPR **Article 17** (right to erasure) covers personal data in agent memory —
+conversation history, retrieved chunks, **and embeddings**. Fines reach 4% of
+global revenue, and the EU's data-protection authorities are actively auditing
+deletion (the EDPB's 2026 sweep checked 764 organizations and found "lack of
+automated deletion mechanisms" almost everywhere). Meanwhile *no vector
+database offers provable deletion* — teams hand-roll it.
+
+If you sell AI to enterprises, you've probably hit the sharper version: a
+customer's security review asks *"prove you can delete a user's data from your
+AI,"* and you can't. Lethe is the answer you hand them.
+
+## How it works
+
+```
+tag(subject → record)  →  forget(subject)  →  delete from your stores
+                                            →  verify the records are gone
+                                            →  signed deletion certificate
+                                            →  tamper-evident audit entry
+```
+
+You never have to remember to call `tag` everywhere: wrap your vector store
+once and writes tag themselves.
+
+## Quickstart (drop-in)
+
+```bash
+pip install -e .            # from source for now (PyPI soon)
+lethe keygen --out lethe_key.bin     # one-time: your signing key (prints the public key)
+export DATABASE_URL=...              # your own Postgres
+export LETHE_SALT=...                # a secret; pseudonymizes subjects in the ledger
+lethe init-db                        # creates Lethe's ledger + audit tables
+```
+
+Wire Lethe to your store, then **wrap your vector store** so every write is
+tagged for deletion:
+
+```python
+import os, psycopg
+from lethe import Lethe
+from lethe.ledger import Ledger
+from lethe.audit import AuditLog
+from lethe.signing import Signer
+from lethe.connectors.pgvector import PgVectorConnector
+from lethe.integrations.langchain import LetheVectorStore
+
+conn = psycopg.connect(os.environ["DATABASE_URL"])
+lethe = Lethe(
+    ledger=Ledger(conn),
+    audit=AuditLog(conn),
+    signer=Signer.from_private_bytes(open("lethe_key.bin", "rb").read()),
+    connectors={"pgvector": PgVectorConnector(conn)},
+    salt=os.environ["LETHE_SALT"],
+)
+
+# Wrap once. Declare which metadata field names the data subject.
+store = LetheVectorStore(
+    my_vectorstore, lethe,            # any LangChain-style store
+    store="pgvector", namespace="docs",
+    subject_key="user_id",
+    id_key="doc_id",                  # recommended: bind ids from metadata
+)
+
+# Use it like a normal vector store — tagging happens automatically.
+store.add_documents([Document(page_content="...",
+                              metadata={"user_id": "alice@example.com",
+                                        "doc_id": "doc-123"})])
+```
+
+When a deletion request comes in:
+
+```python
+cert = lethe.forget("alice@example.com")   # deletes everywhere + returns the certificate
+```
+
+Verify a certificate (pin the operator's *published* public key — a certificate
+that vouches for itself proves nothing):
+
+```python
+from lethe.certificate import verify_certificate
+assert verify_certificate(cert, trusted_public_key=PUBLISHED_PUBKEY)
+```
+
+## The certificate
+
+Ed25519-signed, tamper-evident, independently verifiable. It states exactly what
+happened and **scopes its claim honestly** — *"deleted across these retrieval
+layers and verified absent,"* never "perfectly erased everywhere" (backups and
+model weights are out of scope by definition). `verified_absent` means Lethe
+re-queried the configured endpoint immediately after deleting and saw the
+records gone *at issue time* — it is not a guarantee against read replicas,
+query caches, or asynchronous propagation (notably Pinecone, whose deletes are
+eventually consistent).
+
+```json
+{
+  "all_verified": true,
+  "records_deleted": 2,
+  "layers": [{"store": "pgvector", "namespace": "docs",
+              "deleted_count": 2, "verified_absent": true, "erased": true}],
+  "claim": "Deleted across the listed retrieval layers and verified absent. ...",
+  "signature": "…", "public_key": "…"
+}
+```
+
+## CLI
+
+| Command | Purpose |
+|---|---|
+| `lethe keygen --out KEY` | Create the Ed25519 signing key (prints the public key to publish) |
+| `lethe init-db` | Create Lethe's ledger + audit tables in your Postgres |
+| `lethe forget SUBJECT` | Delete a subject everywhere; prints the signed certificate |
+| `lethe verify CERT --public-key PUB` | Verify a certificate against the operator's published key |
+| `lethe audit-head` | Print the audit-log tip hash (record it out-of-band) |
+| `lethe verify-audit --expected-head H` | Detect tampering/truncation of the audit log |
+
+## For AI agents (MCP)
+
+Lethe ships an MCP server so autonomous agents can execute provable deletion
+and verify certificates machine-to-machine:
+
+    pip install "lethe-delete[mcp]"
+    lethe-mcp
+
+Destructive deletes are two-step (preview → confirm token → forget), and any
+agent can verify a certificate with zero infrastructure (you still need the
+operator's published public key to pin against). Full guide:
+[docs/m2m.md](docs/m2m.md).
+
+## Security model & honest limits
+
+- **Self-hosted.** The SDK and the provenance ledger run in your own Postgres.
+  Lethe-the-project never sees your data. The salt stays in your app.
+- **No raw PII in the ledger.** Subjects are stored as HMAC-SHA256 hashes.
+- **Verify with a pinned key.** An unpinned certificate check only proves
+  internal consistency; always pin your published public key.
+- **`verified_absent` is a point-in-time re-query, not a replication proof.**
+  For eventually-consistent stores (Pinecone) a delete may not have propagated
+  to every replica at issue time. pgvector verifies read-your-writes on one
+  connection; a read-replica DSN would reintroduce the gap.
+- **Audit truncation needs an out-of-band head.** Mid-chain edits are caught
+  automatically; detecting deletion of the *most recent* entries requires
+  recording `lethe audit-head` out-of-band and checking `verify-audit
+  --expected-head`.
+- **Coverage = what flows through Lethe.** Writes that bypass the wrapper/`tag`
+  aren't tracked. Wrap your store, or tag explicitly.
+- **Pre-existing data** (written before you adopted Lethe) needs retroactive
+  discovery — on the roadmap, not in v0.1.
+- **Not erasure from backups or model weights.** Out of scope by design; the
+  certificate says so.
+
+## Connectors
+
+- **pgvector** (and any Postgres table) — `PgVectorConnector`
+- **Pinecone** — `PineconeConnector` (pass your `Index`). Note: Pinecone
+  deletes are eventually consistent, so `verified_absent` is asserted at issue
+  time against the queried endpoint, not proven across replicas.
+- Roadmap: Weaviate, Qdrant, Redis, conversation logs.
+
+## License
+
+[Apache-2.0](LICENSE) — permissive, with an explicit patent grant.

lethe_delete-0.1.0/lethe/__init__.py

@@ -0,0 +1,5 @@
+from .core import Lethe
+from .models import Certificate, LayerResult, TagRecord
+from .version import __version__
+
+__all__ = ["__version__", "Lethe", "Certificate", "LayerResult", "TagRecord"]

lethe_delete-0.1.0/lethe/audit.py

@@ -0,0 +1,83 @@
+import hashlib
+import hmac
+import json
+
+import psycopg
+
+GENESIS = "0" * 64
+
+AUDIT_SCHEMA = """
+CREATE TABLE IF NOT EXISTS lethe_audit (
+    seq BIGSERIAL PRIMARY KEY,
+    entry JSONB NOT NULL,
+    prev_hash TEXT NOT NULL,
+    entry_hash TEXT NOT NULL,
+    created_at TIMESTAMPTZ NOT NULL DEFAULT now()
+);
+"""
+
+
+def _entry_hash(prev_hash: str, entry: dict) -> str:
+    data = prev_hash + json.dumps(entry, sort_keys=True, separators=(",", ":"))
+    return hashlib.sha256(data.encode()).hexdigest()
+
+
+class AuditLog:
+    def __init__(self, conn: psycopg.Connection):
+        self.conn = conn
+
+    def init_schema(self) -> None:
+        with self.conn.cursor() as cur:
+            cur.execute(AUDIT_SCHEMA)
+        self.conn.commit()
+
+    def _last_hash(self) -> str:
+        with self.conn.cursor() as cur:
+            cur.execute("SELECT entry_hash FROM lethe_audit ORDER BY seq DESC LIMIT 1")
+            row = cur.fetchone()
+        return row[0] if row else GENESIS
+
+    def append(self, entry: dict) -> str:
+        prev = self._last_hash()
+        h = _entry_hash(prev, entry)
+        with self.conn.cursor() as cur:
+            cur.execute(
+                "INSERT INTO lethe_audit (entry, prev_hash, entry_hash) VALUES (%s, %s, %s)",
+                (json.dumps(entry), prev, h),
+            )
+        self.conn.commit()
+        return h
+
+    def head(self) -> str:
+        """Current tip hash (GENESIS if the log is empty). Record this
+        out-of-band; later pass it to verify_chain(expected_head=...) to detect
+        tip-truncation (deletion of the most recent entries)."""
+        return self._last_hash()
+
+    def verify_chain(self, expected_head: str | None = None) -> bool:
+        """Verify the hash chain links from genesis to the current tip.
+
+        SECURITY: an internal walk proves no entry was *altered* or removed from
+        the *middle* (that breaks a prev_hash link), but it CANNOT detect tip
+        truncation — deleting the most recent entries leaves a self-consistent,
+        merely shorter chain. To catch an attacker lopping off the tail (erasing
+        evidence of recent erasures), the operator must record the head hash
+        out-of-band and pass it as ``expected_head`` — the same pin-it-externally
+        discipline the certificate uses for the trusted public key. With no
+        entries the head is ``GENESIS``.
+        """
+        with self.conn.cursor() as cur:
+            cur.execute(
+                "SELECT entry, prev_hash, entry_hash FROM lethe_audit ORDER BY seq ASC"
+            )
+            rows = cur.fetchall()
+        prev = GENESIS
+        for entry, prev_hash, entry_hash in rows:
+            if prev_hash != prev:
+                return False
+            if _entry_hash(prev_hash, entry) != entry_hash:
+                return False
+            prev = entry_hash
+        if expected_head is not None and not hmac.compare_digest(prev, expected_head):
+            return False
+        return True