Changelog

TypeScript single-memory writes with wait_for_index enabled now perform exactly one mutation and then poll the read-only status resource until the durable receipt is searchable and processing is complete. Abort, timeout, and terminal indexing failures preserve the original receipt and never repeat the write.

Python synchronous and asynchronous readiness deadlines now raise one typed IndexingTimeoutError across single writes, batches, updates, jobs, and inference. The exception retains durable memory, request, event, outbox, idempotency, and retry metadata so callers can resume observation safely.

The production OpenAPI endpoint now serves the exact checked-in artifact bytes with identity encoding and validates its length and SHA-256 at startup. The release endpoint publishes the same byte contract: f18a3290608ff17a5d1a2a9f3592ea4a0658e4ff7ae07b7cb33f0fb88b9da861 over 1,536,622 bytes.

Release metadata now binds each public SDK to its source repository, immutable commit and tag, registry artifact URL, byte hash, and package-manager integrity metadata. Production gates download those public artifacts and reject source, version, hash, or OpenAPI drift.

Python SDK 2.4.1 was published from commit 16fe68b2d734c5bfb08839e925f4e95a6b820bc9 at tag v2.4.1. TypeScript SDK 2.3.1 was published from commit 6a415261c3cef49c97ef573bba7e628d95857a87 at tag v2.3.1 with npm provenance.

Production build integrity-r57-20260827-b9349fe40 was deployed from API source commit b9349fe40ec2057b8c00a5e4060f144dac7358e9 and tag api-v1.1.1. The release keeps MCP at 0.5.8, applies schema migration w0x1y2z3a454, and records integrity-r56-20260827-c98e7af10 as the rollback build.

Regression verification covered 1,753 backend unit tests, 239 release/database/graph tests, 40 Python SDK tests, 22 TypeScript SDK tests, 100 deterministic forced-pending single writes without duplicate POSTs, clean public-registry installs, 18 production behavioral contracts, ECS convergence, and a clean post-deploy Sentry window.

World Model remains withdrawn from the public surface. RL training and checkpoint mutation remain admin-only, evaluation and metrics remain plan-gated, and regulated workloads still require the applicable signed agreements.

All public retrieval modes now share one safety envelope. Full, fast, advanced, reason, chat, SDK, and MCP responses expose the same grounded/degraded state, evidence memory IDs, and claim receipt instead of allowing each adapter to invent its own confidence contract.

Open-vocabulary claim grounding now verifies the requested subject, predicate, and value together. Unsupported attributes fail closed even when another fact about the same entity is nearby, while paraphrases of stored facts remain retrievable without fixture-specific aliases.

Cached and uncached retrieval use the same grounding and safety versions. Cache keys include the query normalization, retrieval, grounding, and safety contract versions so a release cannot reuse an answer evaluated under an older policy.

Reason and chat no longer turn related memories into an unsupported answer. When evidence is absent or degraded, the answer is nullable and the response carries an explicit abstention reason.

Corrections suppress superseded wording across retrieval adapters, normalize ASCII and Unicode possessives, and preserve explicit old-to-current provenance, making the corrected fact the canonical current truth without deleting audit history.

The hosted 26-tool MCP v0.5.7 adapter rejects malformed, missing, degraded, or ungrounded upstream evidence, marks returned memory text as untrusted data, and keeps pending writes separate from verified search results.

Python SDK 2.3.0 and TypeScript SDK 2.2.0 add typed scope, readiness, correction, ProofLoop, grounding, idempotency, and fail-closed safety contracts guarded against the exported OpenAPI artifact.

The production acceptance holdout passed 200/200 unseen semantic positives with recall@5 1.00 and MRR@5 1.00, plus 2,000/2,000 subject-match/attribute-mismatch abstentions with no false positives, no false negatives, no retries, and no 5xx or transport errors across eight isolated tenants.

Production build v109-415227a0b was deployed from source commit 415227a0bcc2972a761d13daf69f36844bb480c1 with immutable API and worker images. v109 makes grounding status canonical on every adapter, including compound known queries and fail-closed degraded responses.

Schema migration remains v9w0x1y2z353 with no data migration in this release. The documented rollback build is v108-02389e944.

Every public memory write now follows one truthful readiness contract. Raw, batch, Mem0-compatible, fast-ingest, memory-tool, correction, and direct-update paths return 200 or 201 only when their result is ready; a durable commit still converging returns 202 with searchable:false, Retry-After, Location, status_url, and a stable indexing event ID.

Memory-tool inserts now forward Idempotency-Key into the PostgreSQL transactional outbox and remove request-time metadata from the logical fingerprint. Identical retries replay one resource and one event; a changed body with the same key returns 409.

Corrections now persist their resolved collection scope, expose GET /v1/corrections/{id} as a real status endpoint, and report canonical search-delivery state from the backing correction memory. Default-collection corrections are discoverable through relevant-search instead of being hidden by a nullable request alias.

Search thresholds are now terminal views over one cached, calibrated score vector. Numeric thresholds no longer create separate retrieval or reranking executions, so raising a threshold can only remove results and cannot introduce a new result.

Open-vocabulary claim grounding now combines deterministic subject binding with strongly calibrated semantic support for label-free paraphrases such as editor transitions, pet breeds, rollback commands, time zones, retry limits, and SLO values, while weak same-entity attribute noise still abstains.

Direct memory edits now preserve immutable history and use the same pollable asynchronous contract when re-indexing is pending, eliminating the previous window in which PATCH returned 200 before search could observe the corrected value.

The generated OpenAPI 3.1 artifact documents every asynchronous 202 response and readiness header, includes correction status GET, and points release traceability to this public changelog instead of a private repository URL.

Compatibility and fast-ingest paths no longer convert bounded post-commit indexing observation into 503 errors. Durable identities remain stable and the outbox reconciler continues delivery without encouraging duplicate client work.

Retrieval now preserves full semantic verification for ambiguous entity and facet queries while safely abstaining before reranking only when dense similarity is below the calibrated unrelated-tail boundary and neither sparse nor exact evidence exists.

Fresh production regression gates cover direct facts, paraphrases, multi-hop questions, distractors, superseded facts, unknown questions, concurrency, idempotent retries, correction readiness, derivative deletion, and OpenAPI/runtime agreement.

Hebbrix MCP 0.5.6 remains the compatible 26-tool public adapter for API v64.

Introduced infer:true mode for automatic fact extraction from conversations. Send raw conversation turns and Hebbrix extracts clean, atomic facts using a 3 tier pipeline: embedding classifier, LLM extraction, and content deduplication.

Added memory worthiness classifier that rejects queries, greetings, and noise before they reach the LLM. Saves token costs and keeps your memory index clean.

Fact extraction now runs on gpt-5-nano for faster, cheaper inference compared to the default model.

New SEARCH_MIN_SCORE setting lets you configure a minimum relevance threshold. Results below this score are automatically filtered out, reducing noise in search responses.

Upgraded the search engine to combine five retrieval layers: semantic vectors, BM25 keyword matching, knowledge graph traversal, importance scoring, and recency boosting.

Added cross encoder reranking option for production workloads that need maximum precision.

Search results now include score explanations showing which layers contributed to each result's ranking.

Improved proper noun and keyword matching through tuned BM25 integration. Queries like 'Sarah from TechCorp' now correctly prioritize exact entity matches.

Entity extraction now runs asynchronously in the background, removing it from the critical path of memory storage. Write latency significantly reduced.

Knowledge graph indexing can be toggled per environment using the ENABLE_KNOWLEDGE_GRAPH_INDEXING setting.

Fixed a timeout issue where Neo4j connection failures would block the entire memory ingestion pipeline.

New /v1/chat/completions endpoint that follows the OpenAI API format. Drop Hebbrix into any existing OpenAI integration by changing the base URL and API key.

Automatic memory retrieval during chat: the system searches relevant memories and injects them into the conversation context before generating a response.

Support for streaming responses with memory augmented context.

Added webhook support for memory lifecycle events: created, updated, deleted, and searched.

Configurable webhook endpoints per collection, with automatic retry and failure logging.

Webhook payloads include full memory content, metadata, and event context.

Added TrustedHostMiddleware to reject requests from unauthorized origins.

Improved API key rotation with zero downtime key swapping.

Added rate limiting per API key with configurable burst and sustained limits.

All memory content is now encrypted at rest using AES-256.

Complete rewrite of the memory storage engine. Memories now flow through three tiers: short term for recent context, medium term for ongoing relationships, and long term for permanent knowledge.

Automatic memory promotion and decay based on access patterns, importance, and recency. Memories that matter get strengthened. Noise fades naturally.

New collection system for organizing memories by application, namespace, or user. Full multi-tenant isolation by default.

Bulk memory operations: import, export, and delete across collections.

New dashboard for managing memories, viewing knowledge graphs, and monitoring usage.

Automatic entity and relationship extraction from stored memories. Store a sentence like 'Alex joined the product team and reports to Jordan' and Hebbrix maps the entities and connections automatically.

Graph traversal during search: ask about Jordan's team and Hebbrix finds Alex through the relationship graph, even without a direct mention in the query.

Visual knowledge graph explorer in the dashboard.