What problem does it solve? Long-running agent conversations need durable memory that stays searchable while extraction happens asynchronously, without corrupting state or losing continuity between sessions. This Skill provides a deterministic CLI boundary that handles validation, transactions, cursors, and search merging so agents only make semantic decisions. ## Core Features & Use Cases - Atomic Pending Publication: Commit Snapshot updates, UT changes, and history cursor advances in a single SQLite transaction via publish-pending, with stale-revision and continuity checks. - Merged Pending/Built Search: Query memory immediately after publication; Pending UTs participate through lexical matching while Built indexes serve validated, hash-verified documents. - Frozen Batch Builds: Freeze Pending UTs into an exact-content batch, then build them into a stable index with Built-only validation that rolls back on any retrieval failure. - Use Case: An agent Harness extracts memory from a conversation in the background, publishes a proposal covering history events 81-120, searches the new Pending UTs instantly, then freezes and builds them into the validated Built index once a builder Agent reviews the batch. ## Quick Start Initialize a memory project with the dynamic memory CLI, then publish a proposal file and run a search query against the merged memory.