You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Slice: eager memory admission on UI save with join-only wake #353
As a Human saving Memory through the UI, I want the change recorded durably at save time and carried by the next turn without an extra waiting turn, so that a crash loses nothing. As a Human saving ten times in a row, I want one coalesced notice, not ten rows. As a Human whose bot is idle, I want saves to never wake the bot alone.
Acceptance criteria
A UI save admits a memory-change notice immediately (durable across Host restart).
The notice rides the next turn of any trigger with no extra waiting turn.
No save ever wakes an idle bot by itself.
Rapid saves coalesce into one bounded notice.
Live verification on an isolated Host with a real model.
Scope decision: ordinary Memory browsing is read-only (ADR-0088), and inline UI saving is not part of the requested flow. #350 remains open for delivery of external Memory changes through the Inbox; #352 is the remaining implementation slice. The existing explicit Human save service contract is unchanged by this triage.
Activity
DoodleBears commentedon Sep 29, 2026
Scope decision: ordinary Memory browsing is read-only (ADR-0088), and inline UI saving is not part of the requested flow. #350 remains open for delivery of external Memory changes through the Inbox; #352 is the remaining implementation slice. The existing explicit Human save service contract is unchanged by this triage.