Meerkat Recall 0.9.1

Meerkat Recall 0.9.1 adds release containers and practical bulk-import diagnostics while retaining the exact Meerkat 0.9.0 SDK.

• Deploy the gateway and managed workers on Linux AMD64 using authenticated Compose, immutable Recall and paired SurrealDB image digests, persistent state, private credentials, and migration before startup.
• Select runtime TOML with serve --config, migrate --config or ELEPHANT_CONFIG. A missing or malformed selected file fails without falling back to checkout discovery.
• Check worker discovery and current named-space authority separately from process liveness. Detailed readiness actions require configuration-read permission; remote MCP authority remains the remote service's responsibility.
• Inspect effective daily graph and retrieval limits, reserved and reconciled usage, and remaining headroom through the authorized selected-space budget endpoint. The historical euros field names represent abstract token-accounting units, not provider invoices.
• Handle oversized documents through a new approved profile using the text-full-v2 representation and guarded reindex. text-v1 retains its immutable whole-input representation and reports actionable refusal. Extraction diagnostics distinguish safe typed causes without copying provider output into the diagnostic.
• Persist duplicate-vector bitmap membership and correct filtered HNSW selection for foreign or deleted identical vectors. The paired server includes the same engine changes; an external database server requires its corresponding repair. Existing missing index membership requires a supported recovery operation, not just a restart.
• Preserve typed budget and missing-publication wait reasons. Worker transient retries default to a bounded 10 attempts. Retry terminal failed intake with a fresh revision and key plus the current source generation; the old receipt remains unchanged.
• Fix the paired-server capability verifier for SurrealDB 2.6.5 by decoding the original key through its supported base64 function. The reference-token HMAC vectors and numeric/string record checks remain unchanged.
• Upgrade Rustls to 0.23.46 for RUSTSEC-2026-0346 through RUSTSEC-2026-0349.
• Avoid Rust rebuilds for eligible reader-prose changes while retaining protected checks, security auditing and full-history secret scanning. Code examples and embedded documentation still use full CI. The existing local-model constructor regression now receives its checksum-pinned fixture explicitly.

Install from this release's source and native archives or its exact published container digests. See the deployment guide and service setup. Configure per-space grants, worker credentials and provider approvals before requiring semantic readiness.

Asset	Purpose	Bytes
container-delivery.json	Qualified container transport manifest	1,264
LICENSE-APACHE	Apache-2.0 project license	10,292
LICENSE-MIT	MIT project license	1,078
LICENSE.paired-surreal.upstream	Paired SurrealDB BSL terms	4,565
meerkat-recall-0.9.1-aarch64-apple-darwin.provenance.json	Native artifact provenance and qualification	7,520
meerkat-recall-0.9.1-aarch64-apple-darwin.tar.gz	macOS ARM64 native archive	117,134,361
meerkat-recall-0.9.1-source-f721d2e443e0.tar.gz	Exact release source archive	11,625,567
meerkat-recall-0.9.1-x86_64-unknown-linux-gnu.provenance.json	Native artifact provenance and qualification	9,460
meerkat-recall-0.9.1-x86_64-unknown-linux-gnu.tar.gz	Linux AMD64 native archive	138,216,257
meerkat-recall.docker.tar	Linux Recall image transport	176,855,040
recall-surreal.docker.tar	Linux paired SurrealDB image transport	54,968,320
THIRD_PARTY_NOTICES.md	Third-party notices	1,250
container-digests.json	Published image digests	567
checksums.sha256	SHA256 checksums for the thirteen payloads	1,309

Linux AMD64 containers are published as 0.9.1. Both exact digests passed anonymous pull verification:

ghcr.io/lukacf/meerkat-recall@sha256:f046bfe047665a66746bf2749e70b9556d0e985575c547bfaa31de5b132b8c9c
ghcr.io/lukacf/recall-surreal@sha256:40360249fd92744a025bd9d12cbd4bc504cd787eb94c3000eeac4e4a05aa2a84

Registry packages: Recall and paired SurrealDB. Pin the digests above in deployment configuration.

On macOS 26.5.2 ARM64, the installed native build passed local FastEmbed inference with one document, two semantic queries, stored 384-dimensional vectors and authorization refusals. The public archive preserves the tested executable and payloads with metadata-only changes. Mac provenance records its actual build source and verified release-source mapping.

Linux native qualification covers nine installed cases and one local-model inference case. The final container pair passed authenticated Compose installation, actual Docker host-port access, readiness and grant changes, paired-server capability, restart persistence and graceful shutdown. Linux provenance records exact artifact identities and how original native results carry to the final archive. These bounded cases do not establish whole-corpus retrieval quality, paid-provider behavior, other backends or broader OS support.

The paired SurrealDB server and patched SurrealDB components retain their Business Source License 1.1 terms, separately from Recall's MIT OR Apache-2.0 project license. Preserve the bundled licenses and provenance.

Source: f721d2e443e03c0d7590fad7662c036835c4ed63. All eight required checks passed on both its exact PR tree and the final merged source: 4,070 full-suite tests and 3,811 workspace unit tests passed. The final source also passed 89 deterministic E2E tests and the checksum-pinned local-model constructor regression.

Meerkat Recall 0.9.0

Meerkat Recall v0.9.0

Meerkat Recall is a self-hosted knowledge service for applications and agents. It connects source documents, claims, entities and relationships to their evidence through HTTP and MCP.

Recall 0.9.0 uses the published Meerkat 0.9.0 SDK. The SDK now supplies the provider redirect refusal and fail-closed HTTP construction previously carried as Recall backports. Recall preserves the selected provider's output-token limit through its governed client wrapper.

This release also updates the Ammonia sanitizer to 4.1.7 and preserves both authorization envelopes in identity-merge audit records. Native and container recipes include all six active patched dependency source trees and exact upstream Meerkat license texts. The meerkat-recall command retains its elephant compatibility alias, existing configuration names and HTTP/MCP wire identifiers.

Install from the matching native archive and verify it with checksums.sha256. See the installation guide and service setup. Existing SurrealDB stores require explicit migration 045 before serving. Remote SurrealDB requires the paired Recall server capability; a stock server is not a compatible substitute.

Qualification

The native archives were built from 76167ccd9b1a2bc342734a311f5428e3d97b9745. The release candidate 76a9c4292853c0bcde1fc8136309fa21a4f467bc adds reviewed test configuration, fixtures and lint annotations; production code, dependency lockfile and native build recipes are unchanged. The Cargo manifest changes only optimization for SurrealDB and the embedded database kernel in the test profile.

Both native builds completed successfully. The Linux archive passed nine installed-command checks and the bounded native inference checks. The macOS ARM64 archive passed manifest verification, isolated installation, --help and --version on macOS 26.5.2. The linked ONNX objects establish a conservative static minimum of macOS 13.4; execution on older macOS versions and macOS inference are not claimed.

The repaired ancestry boundary and both concurrent graph-publication scenarios passed with their original workloads and deadlines. The original full Alice scenario passed in 162 seconds with its unchanged 300-second pipeline deadline after the targeted test-profile optimization. All eight required CI checks passed on this exact candidate in run 38543381926.

Final publication commit: 3706cfe90a7f87c690cb7875f8c182705ae4e53a, merged normally with a source tree identical to the tested candidate. The complete source asset contains the exact reviewed candidate above, including all 45 MDX documentation pages. Platform provenance files state the actual native build source and the reviewed test-only difference.

Qualification	Result
Linux and macOS ARM64 native builds	Passed
Linux installed command checks	9 passed
Linux bounded native inference	1 document, 2 queries, 5 cases passed
macOS archive verification, isolated installation, help and version	Passed on macOS 26.5.2
Ancestry boundary and concurrent graph publication on both backends	3 passed with original deadlines
Exact release CI	All 8 required checks passed on the exact candidate
Linux container qualification	4 cases and 45 HTTP requests passed on an isolated internal network through an owned loopback relay; Docker host-port publication unverified
Full Alice semantic scenario	Passed with original corpus, assertions and deadline
Real-provider qualification	Two original publications and four semantic/hybrid responses passed retrieval, groundedness and completion checks

Real-provider qualification used the embedded backend and the original bounded synthetic corpus. Thirteen provider dispatches completed; two earlier failed-attempt embedding calls remain accounted for separately. Extraction and support-verification output limits were checked against actual terminal usage. An independently reviewed offline checker correction recognizes narrower immutable citation spans for grounding. The captured responses, corpus, ranking credit, required facts and thresholds stayed unchanged; the original checker failure was retained, and no provider call was replayed for scoring.

The macOS public archive normalizes build-local paths in its provenance metadata. Its executable and all other packaged file contents match the verified native build. These operator-built binaries do not carry a GitHub Actions build attestation.

Known limits

An accepted source may still be processing; use its operation ID to check publication completion. Physical erasure is refused when required connector or server capabilities are unavailable, and Recall cannot erase copies retained by external providers. Container recipes do not establish acceptance of a separately built image. Migration of generic legacy data, production cutover and consumer field adoption remain separate.

Matching SDK versions do not establish compatibility with a separately installed Meta or HomeCore runtime. Structured date recall, full-graph wiki planning, general relevance and hallucination rates remain outside the established guarantees. The documented unsafe-libyaml unmaintained-dependency exception remains because Meerkat 0.9 still uses it; other dependency advisories remain enforced.

Files

Asset	Contents
LICENSE-APACHE	Project license text
LICENSE-MIT	Project license text
THIRD_PARTY_NOTICES.md	Bundled component notices
meerkat-recall-0.9.0-aarch64-apple-darwin.provenance.json	Source, build and compatibility provenance
meerkat-recall-0.9.0-aarch64-apple-darwin.tar.gz	Native command, service files, licenses and patched dependency sources
meerkat-recall-0.9.0-source-76a9c4292853.tar.gz	Complete source and documentation
meerkat-recall-0.9.0-x86_64-unknown-linux-gnu.provenance.json	Source, build and compatibility provenance
meerkat-recall-0.9.0-x86_64-unknown-linux-gnu.tar.gz	Native command, service files, licenses and patched dependency sources
checksums.sha256	SHA-256 checksums for the eight payloads

Download checksums.sha256 and the desired archive into the same directory. On Linux, run sha256sum --ignore-missing --check checksums.sha256; on macOS, compare the output of shasum -a 256 ARCHIVE.tar.gz with its entry in the checksum file. Follow the installation guide to verify and install the archive.

Meerkat Recall v0.1.0

Meerkat Recall v0.1.0

Source repository: lukacf/meerkat-recall. The distribution source snapshot is fac86288bd17d131d86f5065e490cc41faf0bc7b. Its functional build source is 551ad1a7b9e47a0597acdbe2a4f2f1b16f67d2e9 (tree dc0c1246487201a068d91171da981b54a5949feb). The snapshot includes the test-only correction from 4248124aca879f917cb672bd507cc0581128071e; this changes test fixture ownership without changing production code or test assertions. Artifact provenance keeps these identities separate.

Meerkat Recall is a self-hosted knowledge service connecting source documents, claims, entities and relationships to their evidence. Use it independently through HTTP or MCP, with separate named spaces and ElephantDB or SurrealDB. Retrieval, Living Wiki, truth maintenance and existing lifecycle operations remain available; integration with consumer applications is optional.

This release adds source revision and operation tracking, idempotent acceptance, atomic publication, per-space provider approvals and recovery of interrupted work. Concurrent source admission retries known-aborted transactions while preserving original inputs, authorization, generation checks and receipt identity. Bounded retries handle recognized receipt-progress and embedding-publication conflicts; finalization replans when canonical inputs change. Readiness nonce updates do not invalidate unchanged canonical plans, while semantic changes and erasure reservations remain fenced.

The current repair retries completion bookkeeping for the captured original outcome within its existing lease and deadline. It does not repeat provider work. Metadata retries can reuse an original validated result only when its immutable evidence, publication context and provenance match. They retain the original candidate and commit handoff while continuing to enforce current configuration, generation, attempt and erasure checks. An accepted source can still be pending: use its operation ID to check publication completion.

For setup, initialize the store and configure authentication, named-space grants and approved provider bindings. Existing SurrealDB stores require explicit migration045 before serving. Embedded ElephantDB initializes through its documented serve path. Include an RFC3339 observed_at timestamp in source writes; it does not order revisions or change the original receipt on an identical retry. Set PIPELINE_SKILLS_DIR to the complete skills catalog root, including bundled and custom skills.

Source erasure includes physical deletion, bounded retention of managed backups and a durable erasure journal applied before restored readiness. Remote SurrealDB requires the paired Recall server capability; a stock server is not a compatible substitute. Remote physical erasure is refused when required connector or server capabilities are unavailable. Recall cannot erase copies retained by external model providers. Container and single-replica persistent-volume recipes are included; native artifact validation does not qualify a separate container image.

The current selected native run passed one compilation stage and all nineteen tests: ten outcome-settlement controls, seven metadata-replay controls, and both backend fourteen-source finalization controls. The preceding compilation failed in a test fixture and ran no tests; the separate test-only correction clones the fixture's candidate ID before moving its candidate. That failed compilation remains recorded. Earlier native evidence also retains its original failed erasure-reservation test and later focused correction. The composed native record contains 223 distinct obligations and 245 successful source-scoped observations, plus the retained failed test and separate failed compilation. Reused observations do not count as new executions. These are scoped results, not a clean full-suite result.

Both current platform builds and offline public package derivations passed, preserving each original executable. All nine selected Linux installed checks passed; the run used twelve processes and thirty HTTP requests and finished in 13.42 seconds. The separate Darwin check passed offline archive verification and fresh installation, retaining the selected executable and all 1,293 package manifest entries. Earlier packages retain their earlier source scope. The selected Linux installed checks concern binary identity, startup and authentication, initialization, two named spaces, idempotent source acceptance, pending-state reporting and graceful restart using RocksDB. They concern acknowledged metadata and do not establish completed graph publication or concurrent consumer success. Earlier consumer checks completed eleven, ten, and thirteen of fourteen accepted sources; all three failed. The current consumer run completed all fourteen sources in 321.82 seconds within the original fifteen-minute bound. It accepted fourteen single submissions in 0.159 seconds with no caller retries; eight sources encountered retryable failures and recovered. No source ended in terminal failure or exceeded the time limit. The existing caller checks and an exercised voice search also passed. Background conflict detection recorded one failed action after canonical inputs changed. Source completion does not establish complete maintenance or full-graph wiki coverage.

Retained real-provider evidence from earlier source versions covers ElephantDB in two named spaces: 28 published revisions, 48 semantic/hybrid queries with the required source among the first three results, no unsupported claims in 144 reviewed returned texts, eight canonical negative checks, two completed maintenance jobs and two scoped wiki articles. Retrieval, groundedness and completion remain separate observations. Earlier SurrealDB completion, retrieval and grounding results retain their limited component scope; its original overall verdict remains NOT_QUALIFIED. There is no fresh same-source two-backend provider verdict. Structured temporal/date recall remains limited. Full-graph wiki planning and organization, summary relevance, truth-maintenance adjudication without an observed model dispatch, and positive identity resolution beyond the tested prohibited-merge counterexample remain unqualified. Provider spies and fake-vector rejection are separate controls.

The original full-suite run recorded 3,824 passes and eight failures. All eight failed test identities have later focused repair passes; this does not establish a clean full-suite pass. No general relevance or hallucination-rate guarantee follows from the finite corpus.

The release contains nine files: a source archive, Linux x86_64 and Darwin ARM64 native archives, their provenance, notices/licenses and checksums. The eight payloads passed local checksum verification. Use checksums.sha256 to verify downloaded files. Production cutover and consumer application field adoption remain separate; no generic legacy migration is included.

Release files:

• meerkat-recall-0.1.0-source-fac86288bd17.tar.gz
• meerkat-recall-0.1.0-x86_64-unknown-linux-gnu.tar.gz
• meerkat-recall-0.1.0-aarch64-apple-darwin.tar.gz
• meerkat-recall-0.1.0-x86_64-unknown-linux-gnu.provenance.json
• meerkat-recall-0.1.0-aarch64-apple-darwin.provenance.json
• THIRD_PARTY_NOTICES.md
• LICENSE-MIT
• LICENSE-APACHE
• checksums.sha256