Skip to content

fix: preserve memory relationships through recall - #7

Merged
cucupac merged 2 commits into
mainfrom
codex/preserve-recall-relationships
Sep 22, 2026
Merged

cucupac merged 2 commits into
mainfrom
codex/preserve-recall-relationships

Conversation

@cucupac

@cucupac cucupac commented Sep 22, 2026 •

Copy link
Copy Markdown
Owner

What Changed

Recall preserves the recorded relationships between retrieved memories. Fast-mode and fallback briefs keep selected memory order without repeating linked solutions.

Why

Retrieval used these relationships to find memories but discarded them before synthesis, leaving the agent to infer which outcome belonged to which situation.

How

  • Carry deduplicated memory_relations and their lifecycle metadata through the shared evidence pack, internal reads, and synthesis.
  • Include a relation only when both endpoints are selected and visible.
  • Render connected cases in prior_cases and raise an error when the relationship field is missing.
  • Reuse existing tables and queries, keeping retrieval ranking and limits unchanged.

@cucupac
cucupac merged commit 22f94a5 into main Sep 22, 2026
4 checks passed
@cucupac
cucupac deleted the codex/preserve-recall-relationships branch September 22, 2026 05:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant