Skip to content

Engram v2.8.0 — Memory Lifecycle & Reflection

Choose a tag to compare

@Jxyden34 Jxyden34 released this 24 Oct 19:13
· 31 commits to main since this release
b014014

Engram v2.8.0 brings source-cited reflection and reversible memory lifecycle controls to the stable release.

  • Protect important memories: pin/unpin memories to remove age-related ranking penalties while retaining relevance, validity and project access checks.
  • Undo lifecycle actions: reverse archive/restore or reviewed consolidation from recent history. Reversals require a reason, retain audit/version records, reject newer edits and are idempotent. Consolidation undo archives only the generated summary; originals remain unchanged. Available for actions recorded after upgrade, within seven days.
  • Reflect and project briefs: bounded answers across memories and optional document evidence, checked quotations, reviewed saved briefs, explicit refresh and change comparisons.
  • Deeper and historical answers: bounded follow-up retrieval, recorded point-in-time memory versions, and missing/conflicting evidence with next questions. Historical document versions are excluded.
  • Reviewed consolidation and archival: pairwise and 3–10-memory summaries with retained provenance, explainable decay and reversible searchable archival.

Upgrade

Back up PostgreSQL/object storage and retain application images and host configuration. Stop API/worker/scheduler, apply migrations 013–017 in order, then rebuild/recreate the application services. Fresh Compose installs initialize them automatically; populated volumes require explicit migration. See rollout and rollback.

Validation

67 backend tests passed against isolated PostgreSQL/Redis. Backend, web, mobile, Docker, DR and CodeQL checks passed on the release PR and its merged commit. Real local Ollama checks covered bounded retrieval, cluster consolidation, historical evidence and knowledge gaps. A production backup restored into isolated PostgreSQL and survived migrations 013–017 applied twice with unchanged source fingerprints and counts. Blackwall deployment was verified through public functional canaries; protected rollback artifacts are retained.

Native mobile distribution and Gmail retain their separate preview/qualification status. This release excludes the separate v3 commercial/team work.

Release snapshot: b014014. Recreated after README/repository cleanup; application code matches the verified Blackwall deployment at ea4cbef. PR #86.