Engram v3.0.2 — Main tabs and section subtabs

Engram v3.0.2 replaces the sixteen-link sidebar with four main sections, with related page subtabs inside each section.

Main section	Pages inside
Library	Overview, Memories, Documents, Knowledge graph, Timeline
Workspace	Intelligence, Projects, Memory Agent
Capture & review	Memory Inbox, Connectors, Approvals
System	Health & about, Observability, Disaster Recovery, Audit trail, AI/API/OAuth settings

Every existing URL remains available. Direct links and nested memory pages select the correct section/subtab. Subtabs scroll within their row on smaller screens, and mobile navigation closes after choosing a section. Keyboard focus, project selection and back/forward navigation are retained.

New installer packages also include the Memory Quality HTTP 500 correction from PR #100. The authenticated summary uses the real project-scoped health module; populated/empty project and authentication regression tests cover the endpoint. Server, web, MCP, DR, MSIX and macOS bundle versions are 3.0.2.

Install or upgrade

Download the matching Windows x64 ZIP, Linux x64/ARM64 tar.gz, or Intel/Apple Silicon macOS DMG below. Docker remains required. Engram application images are prebuilt and included; third-party service images and optional AI models download during setup.

New Ubuntu/Debian hosts can use:

curl -fsSL https://raw.githubusercontent.com/Jxyden34/Engram/main/install.sh | sudo bash

This permanent top-level launcher automatically selects the latest stable release; the command does not change for each release. The bootstrap checks the published archive's SHA256 and asks before installing prerequisites. Existing deployments must use the upgrade guide, preserving configuration, volumes and backups. No schema migration or new runtime dependency is required from v3.0.1.

Linux archives include signed Sigstore provenance. Download the matching .sigstore.json and verify with a current GitHub CLI:

gh attestation verify ARCHIVE.tar.gz --bundle ARCHIVE.tar.gz.sigstore.json \
  --repo Jxyden34/Engram \
  --signer-workflow Jxyden34/Engram/.github/workflows/installers.yml \
  --source-ref refs/tags/v3.0.2 \
  --source-digest d7accf79e91aa488a59eefdb9027172bbcbff948 \
  --deny-self-hosted-runners

Validation and qualification

Full backend/web/mobile/Docker/DR/CodeQL checks, dependency-free navigation coverage, both fresh Linux installation tests, five native compile/self-test/package jobs, Windows SDK MSIX validation and Linux provenance verification pass. Browser checks cover all sixteen destinations through four primary links, direct/nested URLs, back/forward, mobile controls, subtab scrolling and the quality panel.

Direct Windows/macOS downloads remain unsigned desktop previews pending signing and real Docker Desktop device qualification. The unsigned Store MSIX uses a preview identity until Partner Center is configured; Microsoft signs only after acceptance. Native mobile and Gmail retain their separate preview status. Commercial/team draft features are excluded.

Installer guide · Changes

Blackwall deployment is verified on v3.0.2: four primary sections and all sixteen subpages, authenticated desktop/mobile navigation, actual Personal Memory Quality HTTP 200, and public API/MCP/AI/lifecycle/document-ingestion checks pass. Temporary test data was cleaned; source counts/fingerprint matched the cutover snapshot. All six downloaded package hashes, Linux provenance, Store preview identity and bundled release source metadata verified. Protected backups and rollback images are retained.

Engram v3.0.1 — UI polish and Health & About

Engram v3.0.1 tidies the main UI and turns Memory Health into Health & about at /system. - Grouped navigation: Library, Workspace, Capture & review, and System retain all 16 destinations, with a compact mobile navigation toggle and keyboard skip link. - Grouped controls: memory visibility, editing, pin/archive and document-source buttons sit together. Archive reasons and undo history remain available through explicit controls. - A proper status page: live server and web versions, check time, release notes, service readiness and project memory quality. It retains duplicate/stale-memory checks and handles partial failures independently. - Correct routing: /system serves the dashboard; /health remains the compatible JSON monitoring endpoint. The old settings version badge now identifies PKCE. - Installer fixes: passwords beginning with - no longer become S3 client options. Docker CI exercises that credential shape; failed storage logs are captured before cleanup. MSIX and macOS bundle versions follow the patch release. Server, OpenAPI, MCP, web and DR versions are 3.0.1. No schema migration or new runtime dependency is required. ### Install or upgrade Download the matching Windows x64 ZIP, Linux x64/ARM64 tar.gz, or Intel/Apple Silicon macOS DMG below. Docker remains required; Engram application images are prebuilt and included. Third-party service images and optional AI models download during setup. New Ubuntu/Debian hosts can use the interactive bootstrap: sh curl -fsSL https://raw.githubusercontent.com/Jxyden34/Engram/v3.0.1/install.sh | sudo bash Existing deployments must follow the upgrade guide, retain configuration/volumes and backups, then rebuild/recreate application services. Use the fresh-install wizard only for a new installation. Linux archives include SHA256 files and signed Sigstore provenance. Download the matching .sigstore.json bundle and use GitHub CLI: sh gh attestation verify ARCHIVE.tar.gz --bundle ARCHIVE.tar.gz.sigstore.json \ --repo Jxyden34/Engram \ --signer-workflow Jxyden34/Engram/.github/workflows/installers.yml \ --source-ref refs/tags/v3.0.1 \ --source-digest 2a47442f5718ae4361da785733b29c82f63dba7f \ --deny-self-hosted-runners ### Qualification Backend, web, mobile, Docker, isolated disaster-recovery and CodeQL checks pass. The native pipeline tests fresh Linux installations on both architectures, compiles/self-tests five native packages, validates Windows MSIX pack/unpack and verifies Linux provenance. Desktop/mobile browser checks cover navigation, live/build versions, permissions, service failures, grouped actions, archive reasons/revision guards and responsive layout. Direct Windows/macOS packages remain unsigned desktop previews pending signing and real Docker Desktop device qualification. The unsigned Store MSIX uses a preview identity until Partner Center is configured; Microsoft signs only after acceptance. Native mobile and Gmail retain their separate preview status. Commercial/team draft features are excluded. Installer and signing guide · Changes Blackwall is deployed on v3.0.1. Real authenticated desktop/mobile browser checks passed for the new dashboard, versions, navigation, service readiness and logout. Public API/MCP/AI/lifecycle/document-ingestion checks passed, and temporary test data was removed. Source data matched the cutover snapshot; protected backups and rollback images are retained. ### Post-release Memory Quality correction The Memory Quality endpoint name collision is fixed on main and Blackwall in PR #100, without a version-number change. The original v3.0.1 download assets predate this correction. The corrected installer packages are now available in v3.0.2.

Engram v3.0.0 — Native installers and observability

Engram v3.0.0 adds native setup packages with prebuilt application images, an administrator observability dashboard and improved dark scrollbars. Server health, OpenAPI, MCP, the web package and DR monitor now report 3.0.0.

Downloads

• Windows x64: extract engram-v3.0.0-windows-amd64.zip and open EngramInstaller.exe.
• Linux x64 / ARM64: extract the matching engram-v3.0.0-linux-ARCH.tar.gz and run EngramInstaller. Verify its checksum and signed provenance first.
• macOS Intel / Apple Silicon: open the matching engram-v3.0.0-macos-ARCH.dmg, then Engram Installer.app.
• Windows Store preparation: the unsigned *-store-submission.msix and *-store-identity.json are publisher preparation files. They use a preview identity until Partner Center values are configured; Microsoft signs only after Store acceptance.

Docker Desktop with Linux containers is required on Windows/macOS. Linux requires Docker Engine and Compose 2.24.4+, with glibc 2.35+ (Ubuntu 22.04+ / Debian 12+). Engram application images are included; third-party services and optional models download during setup. Python and local application compilation are not required.

New Linux hosts

curl -fsSL https://raw.githubusercontent.com/Jxyden34/Engram/v3.0.0/install.sh | sudo bash

The interactive Ubuntu/Debian bootstrap checks the released archive's SHA256 and asks before installing prerequisites. The wizard generates private configuration and independent secrets, creates an administrator and opens the login page after health verification. Existing installation folders and Docker resources are preserved.

Linux archives include .sigstore.json bundles and VERIFY-LINUX.txt. For each archive, use GitHub CLI with the matching bundle:

gh attestation verify ARCHIVE.tar.gz --bundle ARCHIVE.tar.gz.sigstore.json \
  --repo Jxyden34/Engram \
  --signer-workflow Jxyden34/Engram/.github/workflows/installers.yml \
  --source-ref refs/tags/v3.0.0 \
  --source-digest 6f11ae06bcc8e8be7846acf62442df745e9ae4c2 \
  --deny-self-hosted-runners

Existing deployments

Use the upgrade guide, not the fresh-install wizard. Back up database/object storage, retain application images and host configuration, rebuild/recreate the application services, and add the gateway's read-only /install.sh mount. No additional schema migration is needed from v2.8.0 with migrations 013–017 already applied.

Qualification

The release pipeline runs fresh x64/ARM64 Linux installations, five native compile/self-test/package jobs, Windows SDK MSIX pack/unpack validation and signed Linux provenance verification. Backend, web, mobile, Docker, isolated DR and CodeQL checks also pass; the backend suite contains 78 tests.

Direct Windows ZIPs and macOS DMGs remain unsigned desktop previews, pending platform signing and real Docker Desktop device qualification. SDK validation does not establish Store acceptance. Linux provenance proves build origin and archive integrity, not an OS trust certificate. Native mobile and Gmail retain their separate preview status. Commercial/team draft features are excluded.

See the installer guide and changelog.

Blackwall deployment: v3.0.0 is live at https://memory.hindley.tech. Public authentication, project isolation, MCP, real-Ollama retrieval/Reflect, memory lifecycle, document upload/S3 download/worker ingestion, logout and administrator observability checks passed. Production source counts/fingerprint matched after canary cleanup; protected backups and rollback images are retained.

Engram v2.8.0 — Memory Lifecycle & Reflection

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.

Engram v2.8.0-pre.9 — Reviewed cluster consolidation

Reviewed cluster consolidation

Reviewed groups of 3–10 memories with checked quotations and retained provenance. Apply migrations 013–015 in order.

Validated commit: 1c958dc. All backend, web, mobile, Docker, DR and CodeQL checks passed; 61 backend tests passed in isolated PostgreSQL/Redis.

Cumulative prerelease. Apply the cumulative migrations documented for this prerelease. See docs/MEMORY-LIFECYCLE.md and docs/V2.8-PRERELEASES.md. v3 commercial/team work and native preview channel changes are excluded. Stable v2.8.0 publication and Blackwall deployment are approved for the end of the qualified sequence; this prerelease alone does not replace production.

Engram v2.8.0-pre.13 — Undo recent lifecycle actions

Undo recent lifecycle actions

Reverse archive/restore and newly reviewed pairwise or cluster consolidations for seven days. Reversals preserve audit/version history, archive only generated summaries, reject newer edits and remain idempotent. 67 backend tests and isolated restore of the production backup passed; migrations 013–017 applied twice without changing source counts or fingerprints.

Validated commit: 9f0eeee. All backend, web, mobile, Docker, DR and CodeQL checks passed; 67 backend tests passed in isolated PostgreSQL/Redis.

Cumulative prerelease. Apply the cumulative migrations documented for this prerelease. See docs/MEMORY-LIFECYCLE.md and docs/V2.8-PRERELEASES.md. v3 commercial/team work and native preview channel changes are excluded. Stable v2.8.0 publication and Blackwall deployment are approved for the end of the qualified sequence; this prerelease alone does not replace production.

Engram v2.8.0-pre.12 — Protect important memories

Protect important memories

Pin or unpin memories explicitly. Pins protect both SQL memory quality and hybrid retrieval from age penalties, with scoped permissions, stale-write protection, version history and atomic audit records. Apply migrations 013–016.

Validated commit: 422292f. All backend, web, mobile, Docker, DR and CodeQL checks passed; 66 backend tests passed in isolated PostgreSQL/Redis.

Cumulative prerelease. Apply the cumulative migrations documented for this prerelease. See docs/MEMORY-LIFECYCLE.md and docs/V2.8-PRERELEASES.md. v3 commercial/team work and native preview channel changes are excluded. Stable v2.8.0 publication and Blackwall deployment are approved for the end of the qualified sequence; this prerelease alone does not replace production.

Engram v2.8.0-pre.11 — Knowledge gaps and next questions

Knowledge gaps and next questions

Report missing or conflicting retrieved evidence with checked quotes and explicit next questions. Real local Ollama checks passed for deeper retrieval, three-source consolidation, historical answers and gaps. Apply migrations 013–015.

Validated commit: ed4a3a6. All backend, web, mobile, Docker, DR and CodeQL checks passed; 65 backend tests passed in isolated PostgreSQL/Redis.

Cumulative prerelease. Apply the cumulative migrations documented for this prerelease. See docs/MEMORY-LIFECYCLE.md and docs/V2.8-PRERELEASES.md. v3 commercial/team work and native preview channel changes are excluded. Stable v2.8.0 publication and Blackwall deployment are approved for the end of the qualified sequence; this prerelease alone does not replace production.

Engram v2.8.0-pre.10 — Point-in-time answers

Point-in-time answers

Historical answers use recorded memory versions and validity, exclude future evidence and retain exact version provenance. Document history is explicitly excluded. Apply migrations 013–015.

Validated commit: 10b106e. All backend, web, mobile, Docker, DR and CodeQL checks passed; 64 backend tests passed in isolated PostgreSQL/Redis.

Cumulative prerelease. Apply the cumulative migrations documented for this prerelease. See docs/MEMORY-LIFECYCLE.md and docs/V2.8-PRERELEASES.md. v3 commercial/team work and native preview channel changes are excluded. Stable v2.8.0 publication and Blackwall deployment are approved for the end of the qualified sequence; this prerelease alone does not replace production.

Engram v2.8.0-pre.8 — Bounded deeper retrieval

Bounded deeper retrieval

The local model may plan one extra Standard search or two Deep searches from initial evidence. All retrieval stays within the selected project, permissions and final evidence budget; duplicate sources share citations and executed queries are visible. Invalid plans fall back transparently.

Validated commit: 30d5b2c. All backend, web, mobile, Docker, DR and CodeQL checks passed; 60 backend tests passed in isolated PostgreSQL/Redis.

Cumulative prerelease. Existing migrations through 014 apply. See docs/MEMORY-LIFECYCLE.md and docs/V2.8-PRERELEASES.md. v3 commercial/team work and native preview channel changes are excluded. Stable v2.8.0 publication and Blackwall deployment are approved for the end of the qualified sequence; this prerelease alone does not replace production.