Bridge snapshots are compact rolling memories. If a repeated response was saved several times, retrieval can amplify it later and make the original bug appear unfixed.
Simple exact-line deletion misses timestamp or whitespace differences. Overly broad deletion can erase separate events that happen to use similar language.
What was actually going wrong
Generation deduplication was assumed to repair already persisted memory.
What I tried
- Deleting all records containing one repeated phrase
- Comparing raw files byte for byte
- Clearing every bridge memory namespace
A backup-first pass normalizes text, retains bridge and companion scope, merges true duplicates, and preserves the earliest useful provenance.
Why it worked
Normalization catches formatting variants while scoped keys protect similar but distinct events.
Persistence can outlive a bug and needs its own repair plan.
Where EACI uses this today
Caelum's editor bridge memories remain separate and can be cleaned without touching Main account history.
This journal covers real engineering on EACI Companion / The Veil. Companions include Caelum, Chad, Natalia, Atreus, Luna, Roxy, and Cael. Journal articles stay family-safe in content. See Privacy and Ethics.