Skip to content

docs: add memory quality,forgetting and lifecycle RFC - #1652

Merged
Teingi merged 4 commits into
oceanbase:masterfrom
jiannnnyyyyy:docs/memory-quality-lifecycle-rfc
Sep 21, 2026
Merged

Teingi merged 4 commits into
oceanbase:masterfrom
jiannnnyyyyy:docs/memory-quality-lifecycle-rfc

Conversation

@jiannnnyyyyy

@jiannnnyyyyy jiannnnyyyyy commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Which issue or RFC does this PR close?

Closes #1590

RFCs: docs/en/rfcs/1652_memory_quality_and_lifecycle.md and docs/zh/rfcs/1652_memory_quality_and_lifecycle.md

Rationale 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?

  • Define independent quality dimensions: provenance/verification, importance, novelty, and current-state validity.
  • Define deterministic filtering of known inactive and superseded entries.
  • Restrict quality reordering to the fixed RRF pool with a maximum ±2 position displacement.
  • Add the proposed MemoryRankingTrace without changing public RRF scores or HTTP APIs.
  • Preserve existing recall-gate semantics: every issued search round performs the optional rerank before the gate receives result.hits; quality reordering stays within that round's fixed RRF pool.
  • Define near-duplicate handling, L1 recoverable deactivation, and review-gated L2 maintenance.
  • Separate logical lifecycle management from physical deletion and compliance retention.
  • Add competitor, research, security, and evaluation references.

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 (from website/)
  • git diff --check

No 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.

@Teingi

Teingi commented Sep 18, 2026

Copy link
Copy Markdown
Member

中英文rfc都需要

@jiannnnyyyyy
jiannnnyyyyy force-pushed the docs/memory-quality-lifecycle-rfc branch from 9ab1779 to 7f5e280 Compare September 20, 2026 06:43
@jiannnnyyyyy

Copy link
Copy Markdown
Contributor Author

@Teingi @AlexStocks fixed, PTAL

@Teingi

Teingi commented Sep 21, 2026

Copy link
Copy Markdown
Member

文档编号前缀从0000_ 改成1652_

Comment thread docs/en/rfcs/1652_memory_quality_and_lifecycle.md Outdated

@Teingi Teingi left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Teingi
Teingi merged commit e99534d into oceanbase:master Sep 21, 2026
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

RFC: define quality-aware Memory retrieval, forgetting, and reversible lifecycle

3 participants