People Memories

**Judgement** People Memories is a strong, pragmatic “personal CRM-lite” for your assistant. It offers solid functionality (capture, recall, summarize, search, export, reminders) in a simple JSON-backed store, well-suited for users who want their assistant to remember human details without relying on external services. **Strengths** - Good breadth of commands: `remember`, `recall`, `summarize`, `search`, `export`, `list`, and reminder digests. - Smart indexing with tags + keyword extraction for faster, more flexible lookups. - Voice/chat integration that auto-captures “remember …” cues, keeping friction low. - Local, transparent storage that can be scripted against (cron, dashboards, custom tools). **Key Risks / Limitations** - **Privacy & data security**: Stores sensitive personal data (preferences, birthdays, relationship context) in a plain JSON file under `~/.clawdbot/`. There’s no mention of encryption, access controls, or data minimization. On shared machines, poorly secured accounts, or synced home directories, this could expose private information about other people. - **Consent & ethics**: You might store detailed information about people (including birthdays, habits, and possibly sensitive topics) without their knowledge or consent. In some jurisdictions, that can raise regulatory concerns (e.g., GDPR) if used in professional contexts. - **Scalability & robustness**: JSON-based storage is fine for small/medium volumes but may become slow or fragile at large scale, especially if multiple processes (cron, voice integrations, manual commands) write concurrently without explicit locking. - **Usability for non-technical users**: Heavy reliance on CLI + cron + Telegram setup means it’s best suited to technical users; there’s no UI yet beyond the assistant and command line. **Recommended Scenarios** - Individuals or power users who want a **personal memory layer** for their assistant (e.g., remembering what friends like, follow-up topics, or event dates) and are comfortable editing/inspecting a JSON file and configuring cron. - Solo professionals using it as a **lightweight local CRM** for clients or collaborators—especially where they control their own machine and can manage data responsibly. - Workflows that benefit from **meeting prep or social recall**, such as quickly generating a fact card for someone before a call. - Users who prefer **local, inspectable storage** and don’t want data about their contacts going to third-party cloud services. **Use with Caution** - In regulated or privacy-sensitive environments (healthcare, HR, legal) where storing personal data about others may trigger compliance obligations. - On shared or poorly secured machines, or where home directories are broadly accessible or synced without proper safeguards. - For very large teams or contact lists, where a more robust database and explicit access controls would be advisable.