feat: archive invalid memories - #29
Open
faj-design5260 wants to merge 4 commits into
Open
faj-design5260 wants to merge 4 commits into
faj-design5260 wants to merge 4 commits into
Conversation
9 tasks
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.
Invalidating a memory moves it from the active tree into
archive/memories/, preserving content, identity, provenance and explicit history access. Normal Recall, Read and Context exclude invalid memories.Lifecycle contract
FileExistsErrorwithout overwriting either file.include_invalid/--historyand temporal--as-ofaccess without adding it to default retrieval. Raw evidence and provenance remain available. No bulk migration or production data operation is included.Evidence
git diff --check: passed.experiments/runs/archive-management-12-20260916/phase_a_b_report.mdandphase-a-fix-gates.log.mem context; none read the old invalid file through direct read or filesystem fallback, and Recall/Read ID sets did not change. NO E2E-SENSITIVE PATH FOUND in these probes. No answer-quality improvement is claimed, and no 12/24-question expansion is proposed.Agent management changes originally included in this PR were split into #31 for independent review. This PR keeps its original base and head history; the atomicity fix is an additional commit.