[SSoC26] [Medium] Category-Specific Decay Coefficients

[keepsloading]

SSoC26 Issue Proposal: Category-Specific Decay Coefficients

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

Motivation

Allow volatile observations (like recent searches) to decay rapidly while keeping stable context (like name or food allergies) intact.

Detailed Technical Description

Import decay parameters declared in category schemas (e.g. news has a high decay rate, health has a near-zero decay rate) and apply them during memory pruning passes.

Suggested Implementation Direction

Read custom decay settings during the decay phase 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!

[prasiddhi-105]

Hiii please assign this issue to me

[Boundier]

Hey, thanks for engaging with this issue.

We recently shifted the Memact architecture. Memact used to be a memory engine that inferred and acted on user data. It is now becoming open identity infrastructure where users own their data address and apps interact through open protocols.

Because of this shift, many of the older issues no longer fit the new direction, so we are closing them to keep the tracker clean.

If you had already written code for this issue, let us know and we will reopen it for review. A merged PR is not guaranteed but we will take a look.

Check out the new open issues at https://github.com/Memact for what is active now.

[keepsloading]

Hey, thanks for engaging with this issue.

We recently shifted the Memact architecture. Memact used to be a memory engine that inferred and acted on user data. It is now becoming open identity infrastructure where users own their data address and apps interact through open protocols.

Because of this shift, many of the older issues no longer fit the new direction, so we are closing them to keep the tracker clean.

If you had already written code for this issue, let us know and we will reopen it for review. A merged PR is not guaranteed but we will take a look.

Check out the new open issues at https://github.com/Memact for what is active now.