Memory Layer v2.1.0

Memory Layer 2.1.0

Stable application release for Linux and macOS, with Windows x64 preview
packages. All artifacts come from the same release commit and locked dependency
graph. Installing/upgrading existing named instances is a separate operator step.

Highlights

• Private ATProto federation, reviewed collections and explicit cited expertise
  questions across independently owned knowledge areas.
• Company users/projects/devices administration, browser login and selective
  project onboarding, offline curated knowledge and recoverable contributions.
• Durable background jobs, transactional events, visible inspection/retry and
  isolated evaluation tooling. This is not a new paid R3 result or an ROI claim.
• Synchronized knowledge in the main Memories view, desktop-session watcher
  labels and memory urls for UI-first entry-point discovery.
• Dependency security fixes across Rust, Web, documentation and native PDS
  preparation, while preserving the protocol/source baselines.

Choose your package

Platform	Artifact
Linux amd64	memory-layer_2.1.0_amd64.deb
Linux arm64	memory-layer_2.1.0_arm64.deb
Mac Intel	memory-layer-2.1.0-macos-x86_64.pkg
Mac Apple Silicon	memory-layer-2.1.0-macos-aarch64.pkg
Existing bundled Mac	Matching Mac -application-update.pkg
Windows x64 preview	memory-layer-2.1.0-windows-x86_64-build.1.zip or .msi
Windows server tools preview	memory-layer-2.1.0-windows-x86_64-build.1-server-tools.msi
Source / Homebrew	memory-2.1.0.tar.gz

Standard packages require separately configured PostgreSQL/pgvector. They do not
provision a complete local stack or enable paid providers. Mac application-update
packages preserve existing bundled runtime/data; standard Mac packages refuse
to overwrite that runtime. Git credentials and provider configuration remain
your own. Windows ARM64 and 32-bit operating systems are not release targets.

Verify and upgrade

Verify the downloaded artifacts against SHA256SUMS (or their individual
.sha256 files). release-inventory.json records exact sizes, digests and source
commit; Windows additionally has a payload/installer manifest. Linux build
metadata and ABI reports accompany the packages.

Back up the selected installation's database/configuration before upgrading.
Version 2.1.0 embeds append-only migrations through 0084. Do not downgrade an
executable against an upgraded database. Once new work has been accepted,
preserve it and recover forward. Named instances keep independently pinned
executables until explicitly upgraded; do not use restart-all as an upgrade.
Check memory --version, memory doctor, memory health and a real local query
after the selected installation is upgraded.

Signing and limitations

These release packages use the existing unsigned packaging route: no Developer
ID notarization, Authenticode signature or new GPG release signature is claimed.
Mac helper ad-hoc code signatures are not publisher identity verification.
Checksums establish content consistency, not independent publisher identity.
No signing keys, trust roots or verification policies were changed for release.

Windows packages contain client/operator executables, Web assets and skills;
native_stack_bundled is false. The server-tools MSI is not a complete native
PostgreSQL/PDS/Pi installer. Full supervisor isolation, full-stack deployment,
onboarding/recovery and native parity remain unfinished, not stable guarantees.
Both ZIP and MSI variants require the separately installed
Microsoft Visual C++ v14 x64 Redistributable.
Use the latest supported x64 package; it must be at least as recent as the
MSVC build tools used for the application. The Windows manifest reports actual
direct DLL imports, but the packages do not bundle or install the CRT. Hosted
build-machine tests do not establish clean-PC runtime acceptance.

The remaining upstream RSA private-key timing advisory
RUSTSEC-2023-0071
has no patched dependency version. Memory's inspected OIDC path verifies with
public keys rather than performing the affected private-key operation. The
original audit remains visible; it is not described as clean. The lockfile also
retains a yanked spin 0.9.8 warning.

Repository PDS preparation fixes do not automatically update an existing Linux
PDS container or previously prepared Windows runtime. No existing Monolith, CA
or Mac service, dataset, credentials, sharing permission or paid-model policy
was changed by publishing this release.