WARM MCP mcp-v0.1.5

MCP binaries and checksum-verified npm and PyPI launchers.

v0.6.4

This patch release packages the current engine, tightens optional provenance verification, and reorganizes the Rust source tree.

• Check credential semantics, issuer authorization, signed status-list publication, and cached expiry separately from signature validity. Applications using provenance should review the updated profile and compatibility notes.
• Reduce the crate and Python source archives, and check all npm platform packages during release verification.
• Separate language bindings, crate tests, experimental modules, and research executables while keeping existing public imports and executable names.
• Clarify MCP tool behavior and preserve benchmark recovery, completion, and budget accounting checks.

The release covers the Rust crate, the npm package and its eight native platform packages, and holographic-memory-py. The MCP launcher, HTTP SDK, and embedding-model pack retain their separate versions.

See the changelog and changes since 0.6.3. Downloaded artifacts include checksums, SBOMs, and build provenance.

v0.6.3

Holographic Memory v0.6.3

This engine release publishes the maintained holographic-memory package for Node.js, with native bindings for supported macOS, Linux, and Windows targets. It corrects the npm listing and keeps the separate holographic-memory-mcp launcher clearly identified.

npm install holographic-memory

The Go, .NET, Java, Kotlin, Swift, and WebAssembly bindings are available in this repository as source. They require local builds; no corresponding prebuilt or registry packages are published in this release. See the runtime guides for Go, .NET, Java, Kotlin, Swift, and WebAssembly.

See the full changelog and v0.6.3 migration and integrity notes.

crates.io recovery

The .crate asset attached when this immutable GitHub release was published was too large for crates.io and was never uploaded there. Version 0.6.3 was subsequently published from recovery commit 23402e59 by the protected crate-only workflow. Its Rust implementation and README match the signed v0.6.3 tag; the Cargo package file selection was narrowed.

The published crate archive has SHA-256 08e3566c421f0ada43448747f8fa0da1ba8f21e18ff62b6a74e8ddab6ff80650. The recovery workflow attested that archive and its SBOM. Download the archive and run gh attestation verify holographic-memory-0.6.3.crate --repo writerslogic/holographic-memory to verify it.

GitHub locks assets and checksums on published immutable releases. The .crate asset, its SBOM, and SHA256SUMS attached here remain the original oversized build and do not match the crate on crates.io. Use the registry archive and recovery attestation for the published Rust package.

Holographic Memory MCP mcp-v0.1.2

MCP binaries and checksum-verified npm and PyPI launchers.

Holographic Memory MCP mcp-v0.1.1

MCP binaries and checksum-verified npm and PyPI launchers.

Holographic Memory MCP mcp-v0.1.0

MCP binaries and checksum-verified npm and PyPI launchers.

Benchmark evidence archives (data release, not a package)

Untracked benchmark evidence too large for git, archived as split tar.zst parts. Restore with scripts/fetch_evidence.py using benchmarks/evidence/MANIFEST.json (sha256 of every asset and per-file index). This prerelease carries data only; it is not a package release.