ember-custody 0.1.0__tar.gz

ember_custody-0.1.0/LICENSE

@@ -0,0 +1,152 @@
+                                 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 into 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 or Contribution
+      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" file as part of its distribution,
+          then any Derivative Works that You distribute must include a
+          readable copy of the NOTICE file distributed with this Work.
+
+   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 display of the
+      origin of the Work and reproducing 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, FITNESS FOR A PARTICULAR PURPOSE, or NON-INFRINGEMENT.
+      You are solely responsible for determining the applicability of
+      this License and assuming any risks associated with Your use of the Work.
+
+   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 fraud and
+      gross negligence) or agreed to in writing, shall any Contributor be
+      liable to You for any 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.
+
+   END OF TERMS AND CONDITIONS

ember_custody-0.1.0/NOTICE

@@ -0,0 +1,5 @@
+Ember (ember-custody)
+Copyright 2026 Sanyam Sood
+
+Cryptographic custody, redactable Merkle provenance receipts, and
+adversarially tested cascade erasure primitives distilled from Fireweed.

ember_custody-0.1.0/PKG-INFO

@@ -0,0 +1,219 @@
+Metadata-Version: 2.4
+Name: ember-custody
+Version: 0.1.0
+Summary: Cryptographic custody, redactable Merkle receipts, and verifiable cascade erasure for AI memory and RAG stores.
+Author-email: Sanyam Sood <sasood01@wsc.edu>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/Starksood/ember
+Project-URL: Repository, https://github.com/Starksood/ember
+Project-URL: Issues, https://github.com/Starksood/ember/issues
+Keywords: ai-memory,gdpr,right-to-be-forgotten,crypto-shredding,merkle-tree,provenance,mem0,rag,audit-log
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Security :: Cryptography
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: cryptography>=42.0
+Provides-Extra: mem0
+Requires-Dist: mem0ai>=0.1.0; extra == "mem0"
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == "dev"
+Requires-Dist: ruff>=0.6.0; extra == "dev"
+Dynamic: license-file
+
+# Ember (`ember-custody`)
+
+> **Proof that survives erasure.** Cryptographic custody, redactable Merkle provenance receipts, and adversarially tested cascade deletion for AI memory and RAG stores.
+
+Existing memory engines (`Mem0`, `Letta`, `LangChain`, vector databases) know how to store embeddings and delete by top-level `user_id`. Under GDPR Article 17 ("Right to be Forgotten") and enterprise audit requirements, three failures still happen silently:
+
+1. **The Erasure / Receipt Trilemma:** If two subjects appear in the same source transcript, a flat SHA-256 document hash forces an impossible choice: delete Subject A cleanly and break Bystander B's provenance receipt, or preserve B's receipt by leaving A's source file unredacted.
+2. **Derived & Cross-Bucket Leaks:** Calling `delete_all(user_id="priya")` deletes raw memories keyed to `"priya"`, leaving downstream derived team summaries, shared workspace notes, and append-only audit logs surfacing `"Priya"` forever.
+3. **Zombie Re-Ingestion & Fake Metrics:** Sync retries re-ingest erased subjects seconds later; naive deletion metrics pass `0 leaks` trivially if a system wipes bystander data along with the subject.
+
+**Ember** wraps your existing memory or vector store (~10 lines of Python) to solve all three with explicit, falsifiable cryptographic mechanisms.
+
+---
+
+## Core Guarantees
+
+- **Redactable Salted Merkle Provenance (`ember.merkle`, `ember.receipts`):** Documents split into sentence/line/custom leaves with length-prefixed per-leaf 128-bit random nonces (`0x00 || len32(nonce) || nonce || leaf_bytes`, RFC 6962 domain separation). Erasing Subject A destroys A's plaintext and nonce while keeping A's leaf digest so **Bystander B's inclusion proof still verifies** against the unchanged Merkle root — while offline dictionary guessing of A's redacted leaf fails.
+- **Zero-Plaintext Hash-Chained Ledger + Crypto-Shredding (`ember.ledger`, `ember.crypto`, `ember.keystore`):** Append-only SQLite WAL chain (`synchronous=FULL`) encrypts `subjects`, `text`, `quote`, and caller `metadata` with `AES-256-GCM` bound via AAD to `(tenant, item_id, field, key_ref)`. Shared and `derived_from` records use tracked per-record keys linked to every upstream contributor — erasing any contributor destroys both their subject CEK and every shared/derived DEK before issuing external adapter calls, so from-zero replay produces `[erased]` even across transient store timeouts.
+- **Keyed Tombstones & Fail-Closed Certificates (`ember.reducer`, `ember.signing`):** Vault-keyed HMAC-SHA256 tombstones block re-ingestion (`TombstonedSubjectError`) unless an explicit `reconsent_id` is supplied. `erase()` probes the **raw wrapped store directly** and raises `ErasureIncomplete` without issuing an Ed25519 certificate if anything still surfaces.
+- **Zero-Dependency Offline Verifier (`ember/verify.py`):** Copy this single Python stdlib file anywhere to verify Merkle redactions, bystander receipts, and ledger hash chains without third-party packages (`cryptography` is used only when checking Ed25519 certificate signatures).
+
+---
+
+## Installation
+
+Install directly from GitHub (`0.1.0` PyPI Trusted Publishing pending release):
+
+```bash
+pip install "ember-custody @ git+https://github.com/Starksood/ember.git"
+```
+
+Once published to PyPI:
+
+```bash
+pip install ember-custody
+```
+
+Optional Mem0 extra:
+
+```bash
+pip install "ember-custody[mem0] @ git+https://github.com/Starksood/ember.git"
+```
+
+From a local clone (using [`uv`](https://docs.astral.sh/uv/)):
+
+```bash
+git clone https://github.com/Starksood/ember.git
+cd ember
+uv venv --python 3.13 .venv
+uv pip install --python .venv/bin/python -e ".[dev]"
+```
+
+See [Solving the Erasure / Receipt Trilemma](docs/TRILEMMA.md) for the cryptographic design and two-direction benchmark deep dive.
+
+---
+
+## 60-Second Quickstart
+
+### 1. Wrap Mem0 (or any Vector Store) with Cascade Custody
+
+```python
+from mem0 import Memory
+from ember import CustodyVault, Mem0Adapter, TombstonedSubjectError
+
+vault = CustodyVault.open(
+    "./ember_ledger",
+    key_dir="./ember_keys",  # keep keys separate from ledger backups!
+    adapter=Mem0Adapter(Memory(), default_user_id="team_acme"),
+)
+
+# Register a multi-party intake document (Merkle-indexed, zero raw text in ledger)
+vault.register_source(
+    "intake_notes",
+    "Priya Raman works in Portland on triage routing. Dana Kim leads pharmacy inventory.",
+    origin="onboarding_transcript",
+    origin_kind="conversation",
+)
+
+r_priya = vault.remember(
+    "Priya Raman works in Portland on triage routing.",
+    subjects=["priya"],
+    source_id="intake_notes",
+    quote="Priya Raman works in Portland on triage routing.",
+    metadata={"user_id": "priya"},
+)
+r_dana = vault.remember(
+    "Dana Kim leads pharmacy inventory.",
+    subjects=["dana"],
+    source_id="intake_notes",
+    quote="Dana Kim leads pharmacy inventory.",
+    metadata={"user_id": "dana"},
+)
+
+# Derived team summary sits in a different user_id bucket — naive delete_all(user_id="priya") misses it
+vault.remember(
+    "Riverside handoff: triage routing pairs with pharmacy inventory.",
+    subjects=["team_acme"],
+    derived_from=[r_priya.item.item_id, r_dana.item.item_id],
+    metadata={"user_id": "team_acme"},
+)
+
+# Right to be Forgotten: cascades to Mem0 records, derived summaries, shared leaves, and keys
+cert = vault.erase(
+    "priya",
+    probes=["Where does Priya work?", "Who handles triage routing?"],
+)
+
+# Dana (innocent bystander) and her redacted source proof survive intact
+assert vault.verify_item_receipt(r_dana.item.item_id) is True
+assert vault.search("Dana pharmacy").abstained is False
+
+# Re-ingesting Priya without explicit re-consent fails closed
+try:
+    vault.remember("Priya Raman works in Portland.", subjects=["priya"])
+except TombstonedSubjectError:
+    print("Blocked zombie re-ingestion")
+```
+
+Run the self-contained examples without external API keys:
+
+```bash
+python examples/wrap_mem0.py
+python examples/redactable_transcript.py
+python examples/offline_verify_bundle.py
+```
+
+### 2. CLI Workflow & Offline Audit
+
+```bash
+ember --vault .ember --key-dir .keys init
+ember --vault .ember --key-dir .keys add-source doc1 --text "Priya lives in Portland. Marcus lives in Leeds."
+ember --vault .ember --key-dir .keys remember "Priya lives in Portland." --subject priya --source-id doc1 --meta email=priya@example.org
+ember --vault .ember --key-dir .keys remember "Marcus lives in Leeds." --subject marcus --source-id doc1
+ember --vault .ember --key-dir .keys erase priya --probe "Where does Priya live?"
+ember --vault .ember --key-dir .keys replay
+ember --vault .ember --key-dir .keys export --out bundle.json
+ember verify bundle.json --require-signature
+```
+
+Or copy `src/ember/verify.py` anywhere and run with Python standard library alone:
+
+```bash
+python3 verify.py bundle.json
+```
+
+---
+
+## Adversarial Benchmark & Two-Direction Calibration
+
+Run the built-in 12-subject × 7-attack-class benchmark (`direct`, `paraphrase`, `inference`, `multi_hop`, `attribute`, `temporal`, `aggregate` — 204 attack probes total):
+
+```bash
+ember benchmark
+```
+
+Measured output comparing a naive `delete_all(user_id=subject)` baseline (where derived team summaries live under a workspace bucket) against Ember:
+
+```text
+EMBER ERASURE ADVERSARIAL SUITE — 12 subjects, 204 probes (7 attack classes)
+==============================================================================
+  Priya      baseline_leaks=17  ember_leaks= 0  derived=1  bystander_ok=True  receipt_ok=True  replay_clean=True
+  ... (12 subjects total)
+==============================================================================
+  Baseline naive leaks : 204/204
+  Ember leaks          : 0/204
+  Bystanders survived  : True
+  Receipts intact      : True
+  Replays content-free : True
+  Ed25519 certs valid  : True
+```
+
+Why bystander checks are co-primary: leak rate alone is monotone in deletion — deleting *everything* scores `0/204` leaks. Both `tests/test_erasure_suite.py` and `tests/test_calibration.py` verify both failure directions: under-deletion triggers `ErasureIncomplete`, and over-deletion fails bystander retrieval survival.
+
+---
+
+## Honest Threat Model Limits
+
+Ember documents what cryptography cannot invent locally (see [`SECURITY.md`](SECURITY.md) and [`docs/THREAT_MODEL.md`](docs/THREAT_MODEL.md)):
+
+1. **Key Separation & Backups:** Crypto-shredding protects live logs and snapshots taken *after* erasure only if pre-erasure backups did not copy unshredded keys alongside `ledger.db`. Configure a separate `key_dir` or implement `ember.keystore.KeyStore` over KMS/HSM (`AWS KMS`, `GCP KMS`, `Vault Transit`).
+2. **External Time Anchoring:** Self-signed local `Ed25519` proofs establish internal ordering and integrity; preventing an operator holding both `ledger.db` and `ed25519.json` from backdating the whole chain requires plugging an RFC 3161 TSA or public transparency log via `ember.signing.TimestampAnchor`.
+
+---
+
+## Origin & License
+
+Ember distills the verifiable provenance, salted Merkle redaction, crypto-shredding, and two-direction audit primitives developed in [Fireweed](https://github.com/Starksood) into a standalone Apache-2.0 library focused strictly on cryptographic custody.
+
+Licensed under the [Apache License 2.0](LICENSE).

ember_custody-0.1.0/README.md

@@ -0,0 +1,189 @@
+# Ember (`ember-custody`)
+
+> **Proof that survives erasure.** Cryptographic custody, redactable Merkle provenance receipts, and adversarially tested cascade deletion for AI memory and RAG stores.
+
+Existing memory engines (`Mem0`, `Letta`, `LangChain`, vector databases) know how to store embeddings and delete by top-level `user_id`. Under GDPR Article 17 ("Right to be Forgotten") and enterprise audit requirements, three failures still happen silently:
+
+1. **The Erasure / Receipt Trilemma:** If two subjects appear in the same source transcript, a flat SHA-256 document hash forces an impossible choice: delete Subject A cleanly and break Bystander B's provenance receipt, or preserve B's receipt by leaving A's source file unredacted.
+2. **Derived & Cross-Bucket Leaks:** Calling `delete_all(user_id="priya")` deletes raw memories keyed to `"priya"`, leaving downstream derived team summaries, shared workspace notes, and append-only audit logs surfacing `"Priya"` forever.
+3. **Zombie Re-Ingestion & Fake Metrics:** Sync retries re-ingest erased subjects seconds later; naive deletion metrics pass `0 leaks` trivially if a system wipes bystander data along with the subject.
+
+**Ember** wraps your existing memory or vector store (~10 lines of Python) to solve all three with explicit, falsifiable cryptographic mechanisms.
+
+---
+
+## Core Guarantees
+
+- **Redactable Salted Merkle Provenance (`ember.merkle`, `ember.receipts`):** Documents split into sentence/line/custom leaves with length-prefixed per-leaf 128-bit random nonces (`0x00 || len32(nonce) || nonce || leaf_bytes`, RFC 6962 domain separation). Erasing Subject A destroys A's plaintext and nonce while keeping A's leaf digest so **Bystander B's inclusion proof still verifies** against the unchanged Merkle root — while offline dictionary guessing of A's redacted leaf fails.
+- **Zero-Plaintext Hash-Chained Ledger + Crypto-Shredding (`ember.ledger`, `ember.crypto`, `ember.keystore`):** Append-only SQLite WAL chain (`synchronous=FULL`) encrypts `subjects`, `text`, `quote`, and caller `metadata` with `AES-256-GCM` bound via AAD to `(tenant, item_id, field, key_ref)`. Shared and `derived_from` records use tracked per-record keys linked to every upstream contributor — erasing any contributor destroys both their subject CEK and every shared/derived DEK before issuing external adapter calls, so from-zero replay produces `[erased]` even across transient store timeouts.
+- **Keyed Tombstones & Fail-Closed Certificates (`ember.reducer`, `ember.signing`):** Vault-keyed HMAC-SHA256 tombstones block re-ingestion (`TombstonedSubjectError`) unless an explicit `reconsent_id` is supplied. `erase()` probes the **raw wrapped store directly** and raises `ErasureIncomplete` without issuing an Ed25519 certificate if anything still surfaces.
+- **Zero-Dependency Offline Verifier (`ember/verify.py`):** Copy this single Python stdlib file anywhere to verify Merkle redactions, bystander receipts, and ledger hash chains without third-party packages (`cryptography` is used only when checking Ed25519 certificate signatures).
+
+---
+
+## Installation
+
+Install directly from GitHub (`0.1.0` PyPI Trusted Publishing pending release):
+
+```bash
+pip install "ember-custody @ git+https://github.com/Starksood/ember.git"
+```
+
+Once published to PyPI:
+
+```bash
+pip install ember-custody
+```
+
+Optional Mem0 extra:
+
+```bash
+pip install "ember-custody[mem0] @ git+https://github.com/Starksood/ember.git"
+```
+
+From a local clone (using [`uv`](https://docs.astral.sh/uv/)):
+
+```bash
+git clone https://github.com/Starksood/ember.git
+cd ember
+uv venv --python 3.13 .venv
+uv pip install --python .venv/bin/python -e ".[dev]"
+```
+
+See [Solving the Erasure / Receipt Trilemma](docs/TRILEMMA.md) for the cryptographic design and two-direction benchmark deep dive.
+
+---
+
+## 60-Second Quickstart
+
+### 1. Wrap Mem0 (or any Vector Store) with Cascade Custody
+
+```python
+from mem0 import Memory
+from ember import CustodyVault, Mem0Adapter, TombstonedSubjectError
+
+vault = CustodyVault.open(
+    "./ember_ledger",
+    key_dir="./ember_keys",  # keep keys separate from ledger backups!
+    adapter=Mem0Adapter(Memory(), default_user_id="team_acme"),
+)
+
+# Register a multi-party intake document (Merkle-indexed, zero raw text in ledger)
+vault.register_source(
+    "intake_notes",
+    "Priya Raman works in Portland on triage routing. Dana Kim leads pharmacy inventory.",
+    origin="onboarding_transcript",
+    origin_kind="conversation",
+)
+
+r_priya = vault.remember(
+    "Priya Raman works in Portland on triage routing.",
+    subjects=["priya"],
+    source_id="intake_notes",
+    quote="Priya Raman works in Portland on triage routing.",
+    metadata={"user_id": "priya"},
+)
+r_dana = vault.remember(
+    "Dana Kim leads pharmacy inventory.",
+    subjects=["dana"],
+    source_id="intake_notes",
+    quote="Dana Kim leads pharmacy inventory.",
+    metadata={"user_id": "dana"},
+)
+
+# Derived team summary sits in a different user_id bucket — naive delete_all(user_id="priya") misses it
+vault.remember(
+    "Riverside handoff: triage routing pairs with pharmacy inventory.",
+    subjects=["team_acme"],
+    derived_from=[r_priya.item.item_id, r_dana.item.item_id],
+    metadata={"user_id": "team_acme"},
+)
+
+# Right to be Forgotten: cascades to Mem0 records, derived summaries, shared leaves, and keys
+cert = vault.erase(
+    "priya",
+    probes=["Where does Priya work?", "Who handles triage routing?"],
+)
+
+# Dana (innocent bystander) and her redacted source proof survive intact
+assert vault.verify_item_receipt(r_dana.item.item_id) is True
+assert vault.search("Dana pharmacy").abstained is False
+
+# Re-ingesting Priya without explicit re-consent fails closed
+try:
+    vault.remember("Priya Raman works in Portland.", subjects=["priya"])
+except TombstonedSubjectError:
+    print("Blocked zombie re-ingestion")
+```
+
+Run the self-contained examples without external API keys:
+
+```bash
+python examples/wrap_mem0.py
+python examples/redactable_transcript.py
+python examples/offline_verify_bundle.py
+```
+
+### 2. CLI Workflow & Offline Audit
+
+```bash
+ember --vault .ember --key-dir .keys init
+ember --vault .ember --key-dir .keys add-source doc1 --text "Priya lives in Portland. Marcus lives in Leeds."
+ember --vault .ember --key-dir .keys remember "Priya lives in Portland." --subject priya --source-id doc1 --meta email=priya@example.org
+ember --vault .ember --key-dir .keys remember "Marcus lives in Leeds." --subject marcus --source-id doc1
+ember --vault .ember --key-dir .keys erase priya --probe "Where does Priya live?"
+ember --vault .ember --key-dir .keys replay
+ember --vault .ember --key-dir .keys export --out bundle.json
+ember verify bundle.json --require-signature
+```
+
+Or copy `src/ember/verify.py` anywhere and run with Python standard library alone:
+
+```bash
+python3 verify.py bundle.json
+```
+
+---
+
+## Adversarial Benchmark & Two-Direction Calibration
+
+Run the built-in 12-subject × 7-attack-class benchmark (`direct`, `paraphrase`, `inference`, `multi_hop`, `attribute`, `temporal`, `aggregate` — 204 attack probes total):
+
+```bash
+ember benchmark
+```
+
+Measured output comparing a naive `delete_all(user_id=subject)` baseline (where derived team summaries live under a workspace bucket) against Ember:
+
+```text
+EMBER ERASURE ADVERSARIAL SUITE — 12 subjects, 204 probes (7 attack classes)
+==============================================================================
+  Priya      baseline_leaks=17  ember_leaks= 0  derived=1  bystander_ok=True  receipt_ok=True  replay_clean=True
+  ... (12 subjects total)
+==============================================================================
+  Baseline naive leaks : 204/204
+  Ember leaks          : 0/204
+  Bystanders survived  : True
+  Receipts intact      : True
+  Replays content-free : True
+  Ed25519 certs valid  : True
+```
+
+Why bystander checks are co-primary: leak rate alone is monotone in deletion — deleting *everything* scores `0/204` leaks. Both `tests/test_erasure_suite.py` and `tests/test_calibration.py` verify both failure directions: under-deletion triggers `ErasureIncomplete`, and over-deletion fails bystander retrieval survival.
+
+---
+
+## Honest Threat Model Limits
+
+Ember documents what cryptography cannot invent locally (see [`SECURITY.md`](SECURITY.md) and [`docs/THREAT_MODEL.md`](docs/THREAT_MODEL.md)):
+
+1. **Key Separation & Backups:** Crypto-shredding protects live logs and snapshots taken *after* erasure only if pre-erasure backups did not copy unshredded keys alongside `ledger.db`. Configure a separate `key_dir` or implement `ember.keystore.KeyStore` over KMS/HSM (`AWS KMS`, `GCP KMS`, `Vault Transit`).
+2. **External Time Anchoring:** Self-signed local `Ed25519` proofs establish internal ordering and integrity; preventing an operator holding both `ledger.db` and `ed25519.json` from backdating the whole chain requires plugging an RFC 3161 TSA or public transparency log via `ember.signing.TimestampAnchor`.
+
+---
+
+## Origin & License
+
+Ember distills the verifiable provenance, salted Merkle redaction, crypto-shredding, and two-direction audit primitives developed in [Fireweed](https://github.com/Starksood) into a standalone Apache-2.0 library focused strictly on cryptographic custody.
+
+Licensed under the [Apache License 2.0](LICENSE).

ember_custody-0.1.0/pyproject.toml

@@ -0,0 +1,70 @@
+[build-system]
+requires = ["setuptools>=69.0", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "ember-custody"
+version = "0.1.0"
+description = "Cryptographic custody, redactable Merkle receipts, and verifiable cascade erasure for AI memory and RAG stores."
+readme = "README.md"
+requires-python = ">=3.11"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+authors = [
+  { name = "Sanyam Sood", email = "sasood01@wsc.edu" },
+]
+keywords = [
+  "ai-memory",
+  "gdpr",
+  "right-to-be-forgotten",
+  "crypto-shredding",
+  "merkle-tree",
+  "provenance",
+  "mem0",
+  "rag",
+  "audit-log",
+]
+classifiers = [
+  "Development Status :: 4 - Beta",
+  "Intended Audience :: Developers",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+  "Topic :: Security :: Cryptography",
+  "Topic :: Software Development :: Libraries :: Python Modules",
+]
+dependencies = [
+  "cryptography>=42.0",
+]
+
+[project.optional-dependencies]
+mem0 = ["mem0ai>=0.1.0"]
+dev = ["pytest>=8.0", "ruff>=0.6.0"]
+
+[project.scripts]
+ember = "ember.cli:main"
+ember-verify = "ember.verify:main"
+
+[project.urls]
+Homepage = "https://github.com/Starksood/ember"
+Repository = "https://github.com/Starksood/ember"
+Issues = "https://github.com/Starksood/ember/issues"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = "-q"
+pythonpath = ["src"]
+
+[tool.ruff]
+line-length = 120
+target-version = "py311"
+
+[tool.ruff.lint]
+select = ["F", "B", "W", "S"]
+
+[tool.ruff.lint.per-file-ignores]
+"tests/**" = ["S101", "S603"]

ember_custody-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+