chore(agent-memory): upgrade 4.42.0 → 4.42.1 — declare a fact consulted to make a decision; check for declaration gaps before archiving one - #107
Merged
Conversation
…ed to make a decision; check for declaration gaps before archiving one Mode B upgrade (PATCH, guidance only). Reconcile re-copied DECAY.md, REVIEW.md and .agent/schema.md (stock 4.42.0 before); the protocol semantic step re-copied memory/PROTOCOL.md (byte-identical to the 4.42.0 template). Stamped 4.42.1. Ran in a throwaway worktree of origin/main. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
What
agent-memory Mode B upgrade 4.42.0 → 4.42.1 (PATCH, guidance only). Reconcile re-copied
DECAY.md,REVIEW.mdand.agent/schema.md— each was stock 4.42.0, so staleness only; the protocol semantic step re-copiedmemory/PROTOCOL.md(byte-identical to the 4.42.0 template). Hooks, the CI floor and the built-ins are unchanged. Stamped 4.42.1; every re-copied file byte-identical to its MANIFEST source;memory-lint: 0 errors, 0 warning(s) (Python/Node identical);memory-lint --stagedon this change → ok. Ran in a throwaway git worktree oforigin/main; the checkout was not touched.What changes for this repo's sessions. The protocol's Maintain memory while working rule now tracks every fact id relied on — a fact is relied on when it shaped a decision, i.e. you would have decided differently without it. An edit or a closure is always a use; a read that shaped nothing is not. Nothing can catch an undeclared consultation, so declare it when writing the log. At review time,
REVIEW.mdstep 6 adds declaration gaps (facts): before archiving a fact as faded, search the window's logs for its subject (not its id) and read the hits; a fact whose subject a session exercised without declaring it is kept and declared, not archived. A mention is not an exercise.Why
Archival is the costliest memory error, and this one was invisible to tooling: a fact consulted to make a decision leaves no diff, so
[undeclared-reference]cannot see it,refresh-metadatareads the reliance as non-use, and a review archives a fact that is in use whilememory-lintreports clean. The field report from mercury-composable and mercury documented three such archivals in five weeks, each caught only by a human-guided read of the logs; the tool's own repo had a fourth. Upstream release: https://github.com/Accenture/mercury-go/releases/tag/v4.42.1Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
🤖 Generated with Claude Code