Metadata-Version: 2.4
Name: vaultmem
Version: 0.1.1
Summary: Zero-knowledge encrypted memory library for personal AI agents
Author: Avinash Gosavi
License: MIT
Project-URL: Homepage, https://github.com/aag1091-alt/vaultmem
Project-URL: Repository, https://github.com/aag1091-alt/vaultmem
Keywords: ai,memory,encryption,zero-knowledge,llm,agents,privacy,personal-ai
Classifier: Development Status :: 2 - Pre-Alpha
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
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
Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
Classifier: Topic :: Security :: Cryptography
Requires-Python: >=3.10
Description-Content-Type: text/markdown
Requires-Dist: cryptography>=42.0
Requires-Dist: argon2-cffi>=23.1
Requires-Dist: numpy>=1.24
Provides-Extra: local
Requires-Dist: sentence-transformers>=3.0; extra == "local"
Provides-Extra: dev
Requires-Dist: pytest>=8.0; extra == "dev"
Requires-Dist: pytest-benchmark>=4.0; extra == "dev"
Requires-Dist: sentence-transformers>=3.0; extra == "dev"

# VaultMem

**A zero-knowledge encrypted memory library for personal AI agents.**

## What This Is

VaultMem is an embeddable open-source library that any platform developer can integrate to give their users persistent, encrypted, portable AI memory — where the platform operator cryptographically cannot read user data.

This is the concrete implementation of **Layer 1 (Personal Storage Layer)** of the Memory-as-Asset framework proposed by Pan, Huang & Yang (arXiv:2603.14212, March 2026).

## The Problem

Every existing AI memory library (mem0, Zep, LangMem, Letta) stores user memories in plaintext on the platform's servers. The platform owns your memory. Switch platforms and you start from zero.

VaultMem flips this:
- User controls the encryption key (passphrase → Argon2id → session key)
- Key lives only in RAM during active sessions — never written to disk
- Platform developer embeds the library but cryptographically cannot read memories
- Users export their encrypted vault and take it anywhere

## Repository Structure

```
vaultmem/
├── research/           # All research gathered during ideation
│   ├── 01_existing_memory_systems.md
│   ├── 02_memory_as_asset_paper.md
│   ├── 03_privacy_taxonomy.md
│   ├── 04_voice_interfaces.md
│   ├── 05_author_contacts.md
│   └── 06_related_papers.md
├── paper/              # The arXiv paper being written
│   └── outline.md
├── design/             # Architecture and design decisions
│   └── vaultmem_architecture.md
└── README.md
```

## Status

- [x] Research phase complete
- [x] Architecture designed
- [x] Paper outline drafted
- [ ] Paper sections in progress
- [ ] Python prototype
- [ ] arXiv submission
- [ ] Outreach to MAS paper authors

## Related Work

- **Memory as Asset** (arXiv:2603.14212) — the framework paper this implements
- **Engram** (github.com/EvolvingLMMs-Lab/engram) — closest existing project, MCP tool not library
- **OpenSecret** (opensecret.cloud) — TEE-based alternative approach

## Paper Target

arXiv preprint → ICML 2026 workshop or NeurIPS 2026 workshop
