memorant 1.0.0rc1__tar.gz

memorant-1.0.0rc1/.github/workflows/tests.yml

@@ -0,0 +1,27 @@
+name: Tests
+
+on:
+  push:
+    branches: [main, master, develop]
+  pull_request:
+    branches: [main, master]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+
+    steps:
+      - uses: actions/checkout@v4
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          python -m pip install -e ".[test]"
+      - name: Run tests
+        run: python -m pytest tests/ -q

memorant-1.0.0rc1/.gitignore

@@ -0,0 +1,21 @@
+__pycache__/
+*.py[cod]
+*.db
+*.db-wal
+*.db-shm
+*.sqlite
+*.sqlite3
+.env
+.venv/
+build/
+dist/
+*.egg-info/
+*.report.md
+AUDIT_*.md
+IMPLEMENTATION_REPORT.md
+_audit_*.py
+.coverage
+.coveragerc
+memorant.dead-letter.jsonl
+kimi27fixreport.md
+deepseekreport.md

memorant-1.0.0rc1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Miguel Johnson and contributors
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

memorant-1.0.0rc1/PKG-INFO

@@ -0,0 +1,378 @@
+Metadata-Version: 2.4
+Name: memorant
+Version: 1.0.0rc1
+Summary: Local-first agent memory without a vector database — claims, provenance, trust tiers, and atomic corrections in one SQLite file.
+Project-URL: Homepage, https://github.com/tier4research/memorant
+Project-URL: Documentation, https://github.com/tier4research/memorant#readme
+Project-URL: Source, https://github.com/tier4research/memorant
+Project-URL: Changelog, https://github.com/tier4research/memorant/blob/master/RELEASE_NOTES.md
+Project-URL: Issues, https://github.com/tier4research/memorant/issues
+Author: Tier 4 Research
+License: Apache-2.0
+License-File: LICENSE
+Keywords: agent-memory,ai-agents,fts5,knowledge-base,llm,llm-memory,local-first,long-term-memory,provenance,rag,sqlite,zero-dependency
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Database :: Database Engines/Servers
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.10
+Provides-Extra: embeddings
+Requires-Dist: numpy>=1.24; extra == 'embeddings'
+Requires-Dist: sentence-transformers>=3.0; extra == 'embeddings'
+Provides-Extra: encryption
+Requires-Dist: sqlcipher3; extra == 'encryption'
+Provides-Extra: test
+Requires-Dist: pytest>=8.0; extra == 'test'
+Description-Content-Type: text/markdown
+
+# Memorant
+
+[![Tests](https://img.shields.io/badge/tests-308%20passing-brightgreen)](https://github.com/tier4research/memorant/actions/workflows/tests.yml)
+[![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue.svg)](https://www.python.org/downloads/)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](LICENSE)
+[![Status: RC](https://img.shields.io/badge/status-rc-yellow.svg)](RELEASE_NOTES.md)
+
+**Agent memory that knows where every fact came from — one SQLite file, zero dependencies.**
+
+Memorant is an open-source Python library that stores an AI agent's long-term memory as
+individual claims in a single SQLite database, each tagged with its source, a trust tier,
+and a validity window — with no vector database, embedding model, or external service
+required.
+
+Memorant stores what your agent knows as individual **claims**.
+source, how far you trust that source, and the window of time it was true. When a fact
+turns out to be wrong, you correct *that claim*: Memorant invalidates the old version,
+links the two, and flags everything derived from it for review.
+
+Memorant installs on a bare Python interpreter. No embedding model, no vector server, no GPU,
+no 400 MB dependency tree — SQLite with FTS5 and the standard library.
+
+```bash
+pip install memorant
+
+memorant init --db ./memorant.db
+memorant add "Deploys go out Thursdays." --source manual --trust verified --db ./memorant.db
+memorant search "deploy schedule" --min-trust verified --db ./memorant.db
+```
+
+## Why not just use a vector store?
+
+For pure recall, use one — Memorant isn't trying to beat a vector index at similarity
+search. It solves the problem that shows up *after* recall works: what to do when a
+stored fact is wrong, stale, or was never reliable to begin with.
+
+A vector store has one move for a bad fact: add a contradicting chunk and hope the
+embedding wins. Nothing marks the old chunk as retracted. Nothing records that three
+other memories were built on top of it. Nothing distinguishes "the user told me this"
+from "the model guessed this at 2am."
+
+Here's the same situation in Memorant:
+
+```python
+from memorant import MemorantStore
+
+store = MemorantStore("memory.db")
+store.init()
+
+# The agent infers something. It's a guess, and it's stored as one.
+guess = store.add_claim(
+    "The user deploys on Fridays.",
+    source_pointer="inferred:session-41",
+    trust_tier="derived",
+)
+
+# Later, the user says otherwise. That's operator-tier truth.
+store.correct_claim(guess, "The user deploys on Thursdays.")
+```
+
+After the correction:
+
+- the Friday claim is invalidated, not deleted — the history stays auditable
+- a `corrects` relation links old to new
+- anything with `derived_from` pointing at the old claim is flagged for review
+- background retrieval stops surfacing the retracted version immediately
+
+That's the whole pitch. Everything below is detail.
+
+---
+
+## What a claim looks like
+
+```json
+{
+  "id": "clm_7a3f",
+  "content": "Deploys go out Thursdays.",
+  "trust_tier": "operator",
+  "source_type": "manual",
+  "source_pointer": "chat:2026-03-04",
+  "valid_from": "2026-03-04",
+  "valid_until": null,
+  "reinforcement": 3,
+  "relations": [
+    {"type": "corrects", "target": "clm_2b91"}
+  ]
+}
+```
+
+## Trust tiers
+
+Four tiers, highest to lowest: `operator`, `verified`, `derived`, `untrusted`.
+
+Trust is assigned by *provenance*, not by fact-checking. You declare a policy mapping
+sources to tiers, and Memorant enforces it consistently everywhere afterward.
+
+```python
+from memorant import TrustPolicy
+
+policy = TrustPolicy(rules=[
+    {"source_type": "manual",     "tier": "verified"},
+    {"source_type": "correction", "tier": "operator"},
+])
+```
+
+That distinction matters in practice. Background context injection (*resonance* — an
+FTS5 query run against the claim store on every turn, filtered to `operator` +
+`verified`, returning the top N results) only pulls from the top two tiers. A guess
+the model made three sessions ago stays searchable if you go looking for it, but it
+never quietly reappears as though it were established fact.
+
+---
+
+## At a glance
+
+| Feature | What it does |
+|---------|-------------|
+| Trust tiers | `operator` > `verified` > `derived` > `untrusted` — resonance auto-injects only top tiers |
+| Field-aware redaction | Secret values replaced with `[REDACTED:...]` |
+| Atomic dedup | Identical claims increment a reinforcement counter instead of duplicating |
+| FTS5 scoring | Rank × log(reinforcement) — trust-filtered at query time |
+| Temporal validity | `valid_from` / `valid_until` — query "as of" any date |
+| Correction propagation | `correct_claim()` → invalidates old, creates new, records `corrects` relation — atomic |
+| Relation tracking | `supersedes`, `corrects`, `derived_from` — full audit trail |
+| Digest governance | `pending` → `promoted` / `rejected` — atomic promotion |
+| Doctor contract | `doctor --json` → exit code 0/1/2, component status, check list |
+| Hygiene reports | Stale claims, broken derivation chains, contradiction candidates |
+| SQLite steward | Vendored schema migration manager — pre-migration integrity checks, canary-based recovery |
+| Zero dependencies | Pure Python + stdlib + bundled steward |
+| Optional encryption | SQLCipher support via `pip install memorant[encryption]` |
+| Expectation Ledger | Behavioral contracts, deterministic evaluation, violation recording, fail-closed option |
+
+---
+
+## Quick start
+
+```bash
+# Install
+pip install memorant
+
+# CLI
+memorant init --db ./memorant.db
+memorant add "The user prefers concise technical summaries." --db ./memorant.db --source manual --trust verified
+memorant search "technical summaries" --db ./memorant.db --min-trust verified
+memorant resonate "How should I answer this?" --db ./memorant.db
+memorant doctor --json --db ./memorant.db
+```
+
+```python
+from memorant import MemorantStore, StoreConfig, TrustPolicy
+
+policy = TrustPolicy(rules=[
+    {"source_type": "manual", "tier": "verified"},
+    {"source_type": "correction", "tier": "operator"},
+])
+
+store = MemorantStore("memorant.db", StoreConfig(trust_policy=policy))
+store.init()
+
+# Add a claim
+cid = store.add_claim("The user prefers direct answers.", source_pointer="manual", trust_tier="operator")
+
+# Search with trust filtering
+results = store.search("user preference", min_trust="verified")
+for r in results:
+    print(f"[{r.trust_tier}] {r.score:.3f} | {r.content}")
+
+# Resonance — claims surface on their own
+context = store.resonate("What style should I use?", session_id="sess-1")
+
+# Correct a claim — atomic, propagates
+new_id = store.correct_claim(cid, "The user prefers thorough, evidence-backed answers.")
+
+# Health check
+store.doctor(json_output=True)
+```
+
+---
+
+> **v1.0.0-rc.1** ships three coordinated tools that work together or standalone:
+>
+> - **Memorant** — long-term claim store with trust tiers, provenance, corrections, and temporal validity
+> - **Context Tuner** — recoverable compression and token-budget control for long-running conversations (also [available separately](https://github.com/tier4research/hermes-context-tuner))
+> - **Expectation Ledger** — behavioral contracts, run tracking, and violation evidence for agent governance
+
+## Suite workflow
+
+The three packages work together for end-to-end agent memory governance:
+
+```python
+from memorant import MemorantStore
+from memorant.suite import MemoryCycle
+from hermes_context_tuner import ContextTunerEngine
+from expectation_ledger import ExpectationLedger
+
+cycle = MemoryCycle(
+    memory=MemorantStore("memory.db"),
+    tuner=ContextTunerEngine("context.db"),
+    ledger=ExpectationLedger("expectations.db"),
+)
+
+prepared = cycle.prepare(
+    "What should I remember before answering?",
+    messages=[{"role": "user", "content": "Long conversation..."}],
+)
+```
+
+This keeps short-term compression (Context Tuner) separate from trusted long-term memory (Memorant), with the Expectation Ledger governing both.
+
+---
+
+## Memorant-Ontology
+
+The `memorant-ontology` package adds automatic entity and relation extraction from
+claims. It runs as a background worker that processes claims through an LLM,
+extracting structured entities (people, projects, tools, concepts) and the
+relationships between them.
+
+**Important:** the core memorant store *never* calls a model. `memorant-ontology` is
+an optional background worker — it's opt-in and runs off the hot path.
+
+```bash
+pip install memorant-ontology
+memorant-ontology --db ./memorant.db init
+memorant-ontology --db ./memorant.db worker --limit 10 --rpm 30
+```
+
+Key features:
+- **Entity extraction** — identifies people, places, projects, concepts, tools, organizations, and dates from claim text
+- **Relationship discovery** — builds a knowledge graph of how entities relate
+- **Trust propagation** — entities inherit trust tiers from source claims
+- **Contradiction detection** — flags claims that conflict with existing knowledge
+- **Cost control** — per-claim cost tracking with daily hard stop ($5/day default)
+
+236 tests passing across the extraction, worker, queue, retriever, and normalizer modules.
+
+---
+
+## Comparison
+
+| | Memorant | Mem0 | Zep | pgvector / Chroma |
+|---|---|---|---|---|
+| Runs fully local | ✓ | partial | partial | ✓ |
+| Zero required dependencies | ✓ | ✗ | ✗ | ✗ |
+| Provenance per fact | ✓ | | | ✗ |
+| Trust tiering on retrieval | ✓ | | | ✗ |
+| Atomic correction + propagation | ✓ | | | ✗ |
+| Query "as of" a date | ✓ | | ✓ | ✗ |
+| No LLM call on the memory path | ✓ | ✗ | | ✓ |
+
+Trust tiering on the retrieval path is rare, and I haven't found another zero-dependency system that does it. Some cells above are empty because I haven't verified them — corrections welcome via PR.
+
+Memorant also ships as a pluggable storage backend for [MemPalace](https://github.com/MemPalace/mempalace) (v3.5+). See [MemPalace integration](#mempalace-integration) below.
+
+---
+
+## MemPalace integration
+
+As a MemPalace storage backend, every write lands in the Memorant claim store — trust-tiered, deduplicated, with full provenance:
+
+```bash
+pip install "mempalace[memorant]"
+mempalace mine ~/projects/myapp --backend memorant   # or MEMPALACE_BACKEND=memorant
+```
+
+Migrate existing palaces:
+
+```bash
+mempalace repair --mode migrate-to-memorant
+```
+
+This replaces the retired `scripts/patch_mcp_for_memorant.py` hack. See [RELEASE_NOTES.md](RELEASE_NOTES.md).
+
+---
+
+## Encryption
+
+Optional SQLCipher support:
+
+```bash
+pip install memorant[encryption]
+```
+
+```python
+from memorant import MemorantStore, StoreConfig
+store = MemorantStore("encrypted.db", StoreConfig(encryption_key="your-strong-passphrase"))
+```
+
+Fail-closed: wrong key → can't open. No key → standard SQLite. Zero overhead unless you opt in.
+
+---
+
+## Evaluation
+
+No comparative benchmark against vector-based memory systems yet — planned before v1.0.
+The project's 308 unit tests (90%+ coverage on migration, correction, trust, and
+redaction paths) verify correctness, but they say nothing about whether claim-based
+memory produces better answers than vector RAG in practice. A 50-question benchmark
+with deliberately poisoned stale facts is the next priority.
+
+Pull requests and discussion are welcome.
+
+---
+
+## Project status
+
+**Release candidate** (v1.0.0-rc.1). APIs are stable; expect minor adjustments before 1.0.
+308 tests, 90%+ coverage on the migration, correction, trust, and redaction paths.
+Not yet benchmarked against vector-based memory systems.
+Deferred to v1.1: embedding backend, advanced policy config, repair workflows.
+
+---
+
+## FAQ
+
+### What is Memorant?
+Memorant is an open-source Python library that stores AI agent memory as individual claims in a single SQLite file, each with provenance, a trust tier, and a validity window. It runs entirely locally and requires no external services.
+
+### Does Memorant need a vector database or an embedding model?
+No. Memorant uses SQLite's built-in FTS5 full-text index for retrieval. There are no required pip dependencies, no embedding model, and no GPU.
+
+### How is Memorant different from Mem0, Zep, or Letta?
+Those systems focus on storing and retrieving memory at scale, generally backed by a vector store and often a hosted service. Memorant focuses on the trustworthiness of each stored fact — where it came from, whether it's still valid, and what happens to downstream memories when it turns out to be wrong.
+
+### Can you delete or correct a wrong memory in Memorant?
+Yes. `correct_claim()` invalidates the original claim, creates the corrected version, records a `corrects` relation between them, and flags any claim derived from the original for review — atomically, in one transaction.
+
+### What are trust tiers?
+Four levels — `operator`, `verified`, `derived`, `untrusted` — assigned by provenance policy rather than by fact-checking. Background context injection draws only from the top two tiers, so a model's earlier guess stays searchable but never resurfaces as established fact.
+
+### Does Memorant work offline?
+Yes. The core library never makes a network call and never invokes an LLM. The optional `memorant-ontology` worker does call a model, but it's opt-in and runs off the hot path.
+
+### What Python versions does Memorant support?
+Python 3.10 and later. `pip install memorant` installs no transitive dependencies.
+
+### Is Memorant production-ready?
+It's a release candidate (v1.0.0-rc.1) with 308 passing tests and 90%+ coverage on the migration, correction, trust, and redaction paths. APIs are stable with minor changes expected before 1.0. It has not yet been benchmarked against vector-based memory systems.
+
+---
+
+## License
+
+Apache License 2.0. See `LICENSE` and `NOTICE.md`.