docs: add memory quality,forgetting and lifecycle RFC - #1652
Merged
Teingi merged 4 commits intoSep 21, 2026
Merged
Conversation
Member
|
中英文rfc都需要 |
jiannnnyyyyy
force-pushed
the
docs/memory-quality-lifecycle-rfc
branch
from
September 20, 2026 06:43
9ab1779 to
7f5e280
Compare
Contributor
Author
|
@Teingi @AlexStocks fixed, PTAL |
Member
|
文档编号前缀从0000_ 改成1652_ |
Teingi
reviewed
Sep 21, 2026
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.
Which issue or RFC does this PR close?
Closes #1590
RFCs:
docs/en/rfcs/1652_memory_quality_and_lifecycle.mdanddocs/zh/rfcs/1652_memory_quality_and_lifecycle.mdRationale for this change
Issue #1590 discusses how Memory quality signals, lifecycle validity, forgetting, and maintenance should be defined before implementation begins. This PR records the agreed design boundaries and evaluation plan in synchronized English and Chinese RFCs.
What changes are included in this PR?
inactiveandsupersededentries.±2position displacement.MemoryRankingTracewithout changing public RRF scores or HTTP APIs.result.hits; quality reordering stays within that round's fixed RRF pool.This PR contains documentation only. It does not change runtime code, persisted formats, or public APIs.
Are there any user-facing changes?
No released behavior changes. The RFC is a design proposal; implementation remains subject to review and future changes.
No public API, HTTP contract, or persisted-format changes are included.
How was this change tested?
pnpm build(fromwebsite/)git diff --checkNo runtime tests were added because this PR only adds documentation.
AI usage statement
OpenAI Codex, powered by GPT-5, was used to draft and review the RFC text. The final content was checked against Issue #1590, the repository RFC guidelines, and the existing PowerContext documentation.