Consider restoring or surfacing superseded memories when their superseder expires

Abierto
#6 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript
Área
backend

Línea de trabajo

Read the Supersession section in DESIGN.md, then inspect newestSuperseder in src/lifecycle.ts and the default search and bootstrap filtering in src/search.ts. Compare the two documented behaviors and determine which should apply when a superseder expires or is withdrawn. Done means the chosen behavior is reflected consistently in status, supersededBy, search, and bootstrap.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Problem

When memory B supersedes memory A and B later passes its validUntil expiry, newestSuperseder still counts B as a non-withdrawn superseder (A.status === 'superseded'), while default search (includeExpired=false) and bootstrap exclude B because its validUntil is in the past. As a result, neither A nor B appears in default search or bootstrap unless the caller passes includeSuperseded=true or includeExpired=true (as currently documented in DESIGN.md under Supersession).

Options

  1. Keep the current behavior (validUntil bounds the replacement's validity window rather than reverting to the older memory) as documented in DESIGN.md.
  2. Exclude expired superseders when deriving status / supersededBy (or filter them at read time) so an unexpired predecessor becomes active again once every superseder has expired or been withdrawn.

Refs: #5 (DESIGN.md "Supersession", src/lifecycle.ts, src/search.ts).

Review-Deferral: c915480f6488d694 severity=nit category=correctness

🤖 Generated by Gemini (Antigravity); posted via @kriszyp.

Lenguaje dominante
JavaScript
Estrellas
0
Forks
0
Merge medio
20 h 29 min
PR fusionados (30 d)
28

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de HarperFast/agent-memory

Todos los issues de HarperFast/agent-memory

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.