aa8ceed4b6
Follow-up to the #88347 salvage: after release_all_under() force-closes a profile's shared connection, a store re-created on the same path registers a fresh entry under the same key. A stale holder that later calls close() would pop that fresh entry (its refs were transferred nowhere), letting a third store open a second connection to the same database — exactly the multi-writer contention the shared registry exists to prevent. close() now evicts the registry entry only when it is still its own.
Holographic Memory Provider
Local SQLite fact store with FTS5 search, trust scoring, entity resolution, and HRR-based compositional retrieval.
Requirements
None — uses SQLite (always available). NumPy optional for HRR algebra.
Setup
hermes memory setup # select "holographic"
Or manually:
hermes config set memory.provider holographic
Config
Config in config.yaml under plugins.hermes-memory-store:
| Key | Default | Description |
|---|---|---|
db_path |
$HERMES_HOME/memory_store.db |
SQLite database path |
auto_extract |
false |
Auto-extract facts at session end |
default_trust |
0.5 |
Default trust score for new facts |
hrr_dim |
1024 |
HRR vector dimensions |
Tools
| Tool | Description |
|---|---|
fact_store |
9 actions: add, search, probe, related, reason, contradict, update, remove, list |
fact_feedback |
Rate facts as helpful/unhelpful (trains trust scores) |