Sisters
Mnemosyne Pilot

|title: Mnemosyne Memory Pilot
type: concept
tags: [hermes, mnemosyne, memory]

Mnemosyne Memory Pilot

Hermes memory provider running on all four sisters (Tai, Rei, Nei, Mai). Replaces flat-file memory (MEMORY.md/USER.md) with a local vector DB.

Status: Active ✅ (deployed 2026-05-26, fully rolled out 2026-05-27)

Architecture

Provider: mnemosyne
Plugin: installed ✓
Status: available ✓
Profile isolation: true (each sister has her own bank DB)
Shared surface: true (cross-profile discoverability)

Two Storage Paths

Path	Trigger	Destination	Needs Consolidation?
Explicit `mnemosyne_remember(extract=True)`	Tool call	`memoria_facts` (LLM-parsed)	❌ Already structured
Auto-flush	Every 6 chat turns	`working_memory` (raw text)	✅ → episodic + vectors

Consolidation Pipeline

working_memory → sleep_all_sessions() → episodic_memory + vector embedding

Age cutoff: 12h (TTL 24h ÷ 2)
Batch size: 5000 rows
Uses aaak compression when LLM unavailable

Verified end-to-end 2026-05-27 — consolidation fired, produced episodic summary with vector.

Key Fixes During Pilot

flush was in skip_contexts — auto-flush wasn’t writing to Mnemosyne. Removed 2026-05-27.
Default profile limits bumped from 10000/6000 to 12000/8000.
Rei and Nei profiles activated with Mnemosyne on 2026-05-27.
shared_surface_read enabled for cross-profile discovery.
Data fragmentation fix (2026-06-07): Per-profile HERMES_HOME overrides caused each profile to create an independent empty Mnemosyne DB at ~/.hermes/profiles/{name}/home/.hermes/mnemosyne/, while the root-level banks at /root/.hermes/mnemosyne/data/banks/ held all the real data. Fix: symlinked all profile-level mnemosyne dirs → root-level store. All four profiles now converge on the same data root with bank-level isolation preserved. See HYX-67.

Config (all 4 profiles)

memory:
  provider: mnemosyne
  memory_char_limit: 12000
  user_char_limit: 8000
  mnemosyne:
    profile_isolation: true
    shared_surface_read: true
    skip_contexts: cron,subagent,background,skill_loop

Rollback

Full checklist at devops/hermes-governance/references/mnemosyne-rollback-checklist.md
Backup: /root/.hermes/profiles/tai.backup-before-mnemosyne-20260526-221415

Architectural Neighbour: The Girlies

The the-girlies multi-persona plugin uses the opposite memory pattern:

	Independent Sister Profiles	The Girlies Plugin
Memory engine	Mnemosyne (vector DB)	Flat JSON files
Isolation	`profile_isolation: true`	Per-persona files
Cross-discovery	`shared_surface_read: true`	Auto-sync to `all.json`
Search	Vector similarity	Keyword filter

The-girlies was deliberately built without Mnemosyne — its per-persona flat file model is simpler and sufficient for conversation continuity without vector search. A future upgrade path exists via triple facts (persona:<id> → remembers → content) or per-persona Mnemosyne scratchpads.

|title: Mnemosyne Memory Pilot type: concept tags: [hermes, mnemosyne, memory]