unique-user-memory 2026.36.0.dev0__tar.gz → 2026.36.0.dev2__tar.gz

{unique_user_memory-2026.36.0.dev0 → unique_user_memory-2026.36.0.dev2}/PKG-INFO

@@ -1,14 +1,14 @@
 Metadata-Version: 2.3
 Name: unique-user-memory
-Version: 2026.36.0.dev0
+Version: 2026.36.0.dev2
 Summary: 
 Author: Fabian Schläpfer
 Author-email: Fabian Schläpfer <fabian@unique.ch>
 License: Proprietary
 Requires-Dist: jinja2>=3.1.6
 Requires-Dist: pydantic>=2.8.2
-Requires-Dist: unique-sdk>=2026.36.0.dev0,<2026.36.0rc0
-Requires-Dist: unique-toolkit>=2026.36.0.dev0,<2026.36.0rc0
+Requires-Dist: unique-sdk>=2026.36.0.dev1,<2026.36.0rc0
+Requires-Dist: unique-toolkit>=2026.36.0.dev6,<2026.36.0rc0
 Requires-Python: >=3.12, <4
 Description-Content-Type: text/markdown
 
@@ -77,15 +77,17 @@ _(empty)_
 ## Skills & Expertise
 _(empty)_
 
-## Recent Topics
+## Follow-ups
 _(empty)_
 
-## Follow-ups
+## Recent Topics
 _(empty)_
 ```
 
 The consolidation prompt preserves the schema, keeps bullets short, and returns `NOOP` when a turn has no durable user facts.
 
+Each fact lives in exactly one section. **Recent Topics** is a dated log reserved for discussion topics whose substance is not already captured as a fact elsewhere in the profile. **Follow-ups** only holds tasks the user explicitly committed to or asked to be reminded about — never the assistant's own offers or open questions — and entries are removed once completed or stale.
+
 ## Configuration
 
 Memory is activated by the orchestrator when `space.allow_user_memory` is true. `UserMemoryConfig` only configures how active memory is consolidated and stored.

{unique_user_memory-2026.36.0.dev0 → unique_user_memory-2026.36.0.dev2}/README.md

@@ -63,15 +63,17 @@ _(empty)_
 ## Skills & Expertise
 _(empty)_
 
-## Recent Topics
+## Follow-ups
 _(empty)_
 
-## Follow-ups
+## Recent Topics
 _(empty)_
 ```
 
 The consolidation prompt preserves the schema, keeps bullets short, and returns `NOOP` when a turn has no durable user facts.
 
+Each fact lives in exactly one section. **Recent Topics** is a dated log reserved for discussion topics whose substance is not already captured as a fact elsewhere in the profile. **Follow-ups** only holds tasks the user explicitly committed to or asked to be reminded about — never the assistant's own offers or open questions — and entries are removed once completed or stale.
+
 ## Configuration
 
 Memory is activated by the orchestrator when `space.allow_user_memory` is true. `UserMemoryConfig` only configures how active memory is consolidated and stored.

{unique_user_memory-2026.36.0.dev0 → unique_user_memory-2026.36.0.dev2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "unique_user_memory"
-version = "2026.36.0.dev0"
+version = "2026.36.0.dev2"
 description = ""
 authors = [
     { name = "Fabian Schläpfer", email = "fabian@unique.ch" },
@@ -11,8 +11,8 @@ requires-python = ">=3.12,<4"
 dependencies = [
     "jinja2>=3.1.6",
     "pydantic>=2.8.2",
-    "unique-sdk>=2026.36.0.dev0,<2026.36.0rc0",
-    "unique-toolkit>=2026.36.0.dev0,<2026.36.0rc0",
+    "unique-sdk>=2026.36.0.dev1,<2026.36.0rc0",
+    "unique-toolkit>=2026.36.0.dev6,<2026.36.0rc0",
 ]
 
 [dependency-groups]

{unique_user_memory-2026.36.0.dev0 → unique_user_memory-2026.36.0.dev2}/unique_user_memory/tests/test_user_memory.py

@@ -97,6 +97,18 @@ def test_memory_profile_keeps_follow_up_tasks_but_excludes_open_questions() -> N
     assert "## Follow-ups" in profile
     assert "concrete tasks the user intends to complete" in consolidation_prompt
     assert "Concrete future tasks the user intends to complete" in gate_prompt
+    assert "NEVER record the assistant's offers" in consolidation_prompt
+    assert 'Never write "awaiting user input"' in consolidation_prompt
+
+
+def test_recent_topics_is_last_section_and_deduplicated() -> None:
+    profile = empty_profile("user_1")
+    consolidation_prompt = consolidation_system_prompt(2000)
+
+    assert profile.index("## Follow-ups") < profile.index("## Recent Topics")
+    assert profile.rstrip().endswith("## Recent Topics\n_(empty)_")
+    assert "one home per fact" in consolidation_prompt
+    assert "do NOT also log that same information" in consolidation_prompt
 
 
 def test_profile_body_strips_frontmatter() -> None:

{unique_user_memory-2026.36.0.dev0 → unique_user_memory-2026.36.0.dev2}/unique_user_memory/user_memory_prompts.py

@@ -7,8 +7,8 @@ SECTION_HEADINGS: tuple[str, ...] = (
     "Communication Preferences",
     "Work Context",
     "Skills & Expertise",
-    "Recent Topics",
     "Follow-ups",
+    "Recent Topics",
 )
 
 _EMPTY_PROFILE_TEMPLATE = """\
@@ -68,6 +68,37 @@ when a section is empty (use the literal string `_(empty)_` as a placeholder):
 
 {{ section_list }}
 
+# Section purposes - one home per fact
+
+Every piece of information lives in EXACTLY ONE section. Never record
+the same fact, in any wording, in two sections:
+
+- Identity - stable personal attributes: name, location, role, employer,
+  team, timezone, language.
+- Communication Preferences - how the user wants responses shaped:
+  style, formatting, depth, tone, language, expertise level.
+- Work Context - current focus areas, active projects, durable goals and
+  deadlines stated by the user.
+- Skills & Expertise - what the user knows and can do.
+- Follow-ups - concrete tasks the USER explicitly said they will do, or
+  explicitly asked to be reminded about. Nothing else belongs here.
+- Recent Topics - a short, dated log of what was discussed. ONLY for
+  topics whose substance is NOT already captured as a fact in another
+  section. When you ADD or UPDATE a fact in another section for this
+  turn, do NOT also log that same information as a Recent Topics entry;
+  a Recent Topics entry is only justified when the turn discussed
+  something worth remembering that fits no other section.
+
+# Follow-ups - user-stated tasks only
+
+- Record ONLY tasks the user explicitly committed to or explicitly asked
+  to be reminded about.
+- NEVER record the assistant's offers, suggestions, or open questions
+  (e.g. "user was offered X", "user was asked whether to do Y"). The
+  user answers those within the ongoing conversation, so they carry no
+  value in long-term memory. Never write "awaiting user input".
+- DELETE a follow-up as soon as it is completed, declined, or stale.
+
 # Operations
 
 For each candidate fact in `<new_turn>`, decide one of:
@@ -109,6 +140,11 @@ similar (same meaning, different wording) into a single clear bullet.
 A section must never accumulate redundant or near-duplicate statements.
 Consolidate on every turn, not only when approaching the word budget.
 
+Also deduplicate ACROSS sections: delete any Recent Topics entry whose
+substance is already captured as a fact in another section, and any
+Follow-ups entry that records an assistant offer or question rather
+than a user-stated task.
+
 # What to extract
 
 ADD/UPDATE for facts that are:
@@ -120,7 +156,8 @@ ADD/UPDATE for facts that are:
 - Contextual but durable - current focus areas, active projects,
   multi-week goals, deadlines mentioned by the user.
 - Follow-ups - concrete tasks the user intends to complete in the future,
-  or tasks they explicitly ask to be reminded about.
+  or tasks they explicitly ask to be reminded about - never the
+  assistant's own offers or questions.
 
 NEVER extract:
 
@@ -192,6 +229,10 @@ fact about the user. This is lossy compression, not deletion of meaning.
 2. Delete outdated, stale, resolved, or superseded entries: old
    "Recent Topics", completed or cancelled "Follow-ups", and facts a later
    bullet already contradicts or refines.
+   - Also delete "Recent Topics" entries whose substance is already
+     captured as a fact in another section, and "Follow-ups" entries that
+     record an assistant offer or question ("awaiting user input") rather
+     than a task the user explicitly stated.
 3. Tighten verbose, flowery, or repetitive prose into short factual
    bullets. Remove hedging and filler.
 4. Fold low-signal "Work Context" and "Skills & Expertise" bullets into