feat(memory): emotional salience tagging and cross-session distress persistence #34

Merged

will.anderson merged 2 commits from improve/soul-memory-formation into main 2026-06-22 17:14:33 +00:00

Conversation 0 Commits 2 Files Changed 2

+225 -4

2 Commits

Author	SHA1	Message	Date
will.anderson	0c5b966773	fix(chat): fix auto_persist timestamp extraction and bell label uniqueness ... - engram_compile: BellEvent nodes do not carry created_at in the engram node JSON; extract the unix timestamp from the embedded ' | ts:NNNNN' pattern in the content string instead. Fall back to created_at/updated_at if the marker is absent. Guard str_to_int against empty string so the 72h recency check never silently treats every node as epoch-0 stale. - auto_persist: append the current unix timestamp to the BellEvent label ('bell:soft:1749876543') to make it unique per turn. The previous label ('bell:soft') was the same for every soft bell, causing engram to treat all subsequent writes as updates to the same node.	2026-06-22 12:09:00 -05:00
will.anderson	b2008f4894	feat(memory): emotional salience tagging and cross-session distress persistence ... - auto_persist: detect bell level (soft/hard) on every user message using safety_detect_bell_level; write a dedicated BellEvent engram node with calibrated salience alongside the Conversation node when a bell fires. Tag the Conversation node with bell:soft/bell:hard and 'affective' for direct discovery without scanning all chat nodes. - auto_persist: track per-session bell count, dominant level, and last signal in state (session_bell_count/level/signal keys) so downstream functions can act on the emotional history without re-scanning engram. - engram_compile: include the top-1 most recent BellEvent node within 72h in every context build. Distress context from earlier turns (same or recent session) automatically travels into all subsequent LLM calls. - hist_trim_with_bell_guard: replace hist_trim at the handle_chat call site. Before evicting the oldest turn from the 20-turn window, inspect the user message for bell signals. If a bell was present, write a preservation BellEvent to engram before dropping the turn so the full message survives the rolling window. - session_hist_save: after writing the history node, check session bell counters. On the first save where bell_count > 0, write a session:emotional-summary BellEvent node with distress signal, count, and dominant level. A state flag prevents duplicate writes on subsequent saves in the same session.	2026-06-22 11:23:15 -05:00