Skip to content

[SSoC26] [Medium] Decay Resiliency for User-Confirmed Explicit Preferences #21

Description

@keepsloading

SSoC26 Issue Proposal: Decay Resiliency for User-Confirmed Explicit Preferences

  • Component/Target Repository: $repository
  • Difficulty: Medium

Motivation

Ensure that user-approved preference fields are never completely decayed.

Detailed Technical Description

Set a minimum strength floor (0.4) for memories marked as explicit_preference or approved by the user, ensuring they remain visible in Yourself UI.

Suggested Implementation Direction

Enforce the minimum floor in the decay loop in Memory/src/engine.mjs.


Note: This issue was generated from the Memact open protocol engineering backlog. Contributor guidelines require that PRs resolving this issue must be linked to a corresponding dummy PR in the Context repository for SSoC26 tracking.


SSoC26 Contributor Notice:

Since this repository (Memact/Memory) is outside the main Context repository, and the registered project for tracking contributions is specifically Context (Memact/Context), please make sure to create a dummy PR in the Context repository linking to your actual PR or commits in this repository. This is required for your contribution to be correctly tracked and counted.

If you have already created a dummy PR in Memact/Context linking to your work here, please ignore this message!

Metadata

Metadata

Assignees

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions