Repository navigation
fix: restrict automatic recall to canonical atoms - #41
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Automatic recall could inject ordinary conversation when no promoted fact matched. It now gathers canonical atoms only, including optional vector atom hits, and returns empty when none match. Explicit memory tools retain multi-source/raw access.
atomOnly: trueto shared Runtime and filters externally prefetched results at prompt rendering. Cache scope separates source modes, raw policies, sessions, and manual snapshots.Clarification and acceptance
Scope and results: Atom-only automatic recall in HANDOFF; design: ADR-044.
Target branch
Type of change
Test plan
make all RUN='.venv/bin/python -m'with dedicated PostgreSQL 16: format/lint/strict mypy pass; 1608 passed, 12 optional host cases skipped.2fef395.npm run typecheckandnpm run buildpass.The dedicated Harness run covers the ordinary gate's missing-Harness cases. Real Hermes installation E2E and running OpenClaw host hooks remain untested. Existing low-value/off-topic atoms can still be selected.
Checklist