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.
fix(memory): Re-index MEMORY.md to fix corruption from #4730 #4888
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(memory): Re-index MEMORY.md to fix corruption from #4730 #4888
Changes from all commits
65bfa5af0f90f515b2c18ed9ae8b2a1cc4eFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change stores exact household composition (
5/1/4children split by specific marriages) in a durable memory artifact, whereas the previous form preserved only pattern-level context for calibration. Becausememory/**is long-lived substrate consumed across future sessions, persisting this level of relationship detail creates unnecessary personal-data retention risk without being required for the developmental-calibration behavior this file is meant to capture; this should remain de-identified/opaque-pointer level.Useful? React with 👍 / 👎.
Uh oh!
There was an error while loading. Please reload this page.