verilore 0.11.0__tar.gz

verilore-0.11.0/LICENSE

@@ -0,0 +1,51 @@
+                                 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 acting 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 rights 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 licensor's work, whether in Source or Object
+      form, made available to the public under the terms of this License.
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on the Work and for which the copyright
+      ownership is exercisable by at least one of the authors of the Work.
+      For the purposes of this definition, "Derivative Works" shall not
+      include any work that is a copy of the Work.
+
+      "Notices" shall mean any document that is included with the Work
+      to the extent required by applicable law or in accordance with
+      the terms of this License, for the purpose of informing recipients
+      of the existence and location of specific licenses, notices, and
+      warranties required by law or in accordance with the terms of this
+      License.
+
+      "Annual

verilore-0.11.0/NOTICE

@@ -0,0 +1,4 @@
+Verilore (formerly Mind Palace)
+Copyright 2026 Raunak Dey
+
+Licensed under the Apache License, Version 2.0.

verilore-0.11.0/PKG-INFO

@@ -0,0 +1,118 @@
+Metadata-Version: 2.4
+Name: verilore
+Version: 0.11.0
+Summary: Versioned, evidence-backed memory for AI apps: every answer cites its source and the time it was true.
+Author: Raunak Dey
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/raunakdey-07/verilore
+Project-URL: Repository, https://github.com/raunakdey-07/verilore
+Project-URL: Documentation, https://github.com/raunakdey-07/verilore/blob/main/docs/integration/guide.md
+Project-URL: Changelog, https://github.com/raunakdey-07/verilore/blob/main/CHANGELOG.md
+Project-URL: Issues, https://github.com/raunakdey-07/verilore/issues
+Keywords: memory,rag,llm,provenance,pgvector,mcp,ai-agents
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Framework :: FastAPI
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Libraries
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Operating System :: MacOS
+Requires-Python: <3.15,>=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: fastapi>=0.110.0
+Requires-Dist: uvicorn>=0.27.0
+Requires-Dist: sqlalchemy[asyncio]>=2.0.0
+Requires-Dist: asyncpg>=0.30.0
+Requires-Dist: pydantic>=2.0.0
+Requires-Dist: python-frontmatter>=1.1.0
+Requires-Dist: alembic>=1.13.0
+Requires-Dist: onnxruntime>=1.17.0
+Requires-Dist: tokenizers>=0.15.0
+Requires-Dist: huggingface-hub>=0.23.0
+Requires-Dist: httpx>=0.27.0
+Requires-Dist: prometheus-fastapi-instrumentator>=7.0.0
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: langchain-text-splitters>=1.0.0
+Requires-Dist: typer>=0.9.0
+Requires-Dist: psycopg2-binary>=2.9.0
+Requires-Dist: pgvector>=0.3.0
+Requires-Dist: mcp>=2.1.0
+Provides-Extra: cli
+Provides-Extra: mcp
+Requires-Dist: mcp>=2.1.0; extra == "mcp"
+Provides-Extra: migrations
+Requires-Dist: alembic>=1.13.0; extra == "migrations"
+Requires-Dist: psycopg2-binary>=2.9.0; extra == "migrations"
+Requires-Dist: pgvector>=0.3.0; extra == "migrations"
+Provides-Extra: torch
+Requires-Dist: sentence-transformers>=2.5.0; extra == "torch"
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0.0; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.23.0; extra == "dev"
+Requires-Dist: black>=24.0.0; extra == "dev"
+Requires-Dist: flake8>=7.0.0; extra == "dev"
+Dynamic: license-file
+
+# Verilore
+
+Memory for AI applications that remembers what changed, what was true when, and
+why to believe the recorded state. Add Verilore to an application, record a fact,
+and get back an answer with its source, the time it was true, and the exact
+characters that support it. Export a receipt and verify it on a machine that has
+never heard of Verilore.
+
+## Install
+
+```bash
+uv tool install --python 3.13 verilore
+# or, with a Python from 3.11 to 3.14:
+pipx install verilore
+```
+
+Verilore runs on macOS and Linux, and on Windows through WSL 2, with Python 3.11
+to 3.14 (3.13 at most on an Intel Mac). uv downloads 3.13 if you do not have it,
+which also covers a system whose own Python is newer, such as Fedora 45's 3.15
+(Fedora's uv downloads only when asked: run `uv python install 3.13` first).
+It needs PostgreSQL 15 or newer with pgvector: with Podman or Docker installed,
+`verilore init` starts one for you, and to use one you already run, pass
+`verilore init --database-url ...`.
+[Your system](https://github.com/raunakdey-07/verilore/blob/main/docs/quickstart.md#your-system)
+says how to get uv and Podman on each.
+
+## Quickstart
+
+```bash
+verilore init
+verilore ingest-repo ./docs --corpus project
+verilore recall "What is the primary datastore?" --corpus project
+verilore explain "What is the primary datastore?" --corpus project
+```
+
+`init` sets up the database and records it for every later command, so nothing
+needs exporting. Something wrong? Run `verilore doctor`.
+
+From Python:
+
+```python
+from verilore import Verilore
+
+client = Verilore("default")
+client.remember("Support answers within one business day.", key="support.sla")
+memory = client.recall("What is the support SLA?").current_memories[0]
+print(f"{memory.claim}  [{memory.status}]")
+```
+
+## Links
+
+- [README](https://github.com/raunakdey-07/verilore#readme): what it is, and what it refuses to do
+- [Integration guide](https://github.com/raunakdey-07/verilore/blob/main/docs/integration/guide.md): wiring it into an app
+- [Changelog](https://github.com/raunakdey-07/verilore/blob/main/CHANGELOG.md)
+- [License: Apache-2.0](https://github.com/raunakdey-07/verilore/blob/main/LICENSE)

verilore-0.11.0/README.md

@@ -0,0 +1,351 @@
+# Verilore
+
+[![Release](https://img.shields.io/github/v/release/raunakdey-07/verilore)](https://github.com/raunakdey-07/verilore/releases)
+[![CI](https://img.shields.io/github/actions/workflow/status/raunakdey-07/verilore/ci.yml?branch=main&label=CI)](https://github.com/raunakdey-07/verilore/actions/workflows/ci.yml)
+[![License](https://img.shields.io/badge/license-Apache%202.0-blue)](LICENSE)
+
+Verilore was called Mind Palace until v0.10.0.
+
+[Current release: v0.11.0](docs/release-map.md) · [Changelog](CHANGELOG.md)
+
+
+**Memory for AI applications that remembers what changed, what was true when, and
+why to believe the recorded state.**
+
+Add Verilore to an application, record a fact, and get back an answer with its
+source, the time it was true, and the exact characters that support it. Export a
+receipt and verify it on a machine that has never heard of Verilore.
+
+```text
+remember   a statement becomes memory, with evidence
+recall     an answer, its source, and the time it was true
+explain    the characters that support it, and what replaced it
+history    the supersession chain, oldest first
+receipt    what was returned, plus the digest of the whole response
+verify     offline: no database, no model, no network
+```
+
+Run `verilore` with no arguments and it prints the first three commands, in
+the order a newcomer needs them.
+
+---
+
+## Quickstart
+
+For wiring Verilore into a coding agent so it tracks your project's decisions and
+runbooks. CI runs these commands against a built wheel (`scripts/cleanroom_quickstart.py`),
+and its `Laptop path on Podman` job runs the first three on a machine with no
+database and nothing exported.
+
+Lines starting with `$ ` are the commands CI runs; type them without the `$ `.
+
+```bash
+# Install the command from PyPI. Verilore runs on Python 3.11 to 3.14; uv downloads
+# 3.13 if you do not have it (Fedora's uv downloads only when asked: run
+# `uv python install 3.13` first). macOS, Ubuntu, WSL, Debian, Fedora, Arch:
+# docs/quickstart.md#your-system says how to get uv and Podman on each.
+uv tool install --python 3.13 verilore
+# or, with a Python from 3.11 to 3.14: pipx install verilore
+
+# The whole local setup. With Podman or Docker installed, init starts a local
+# PostgreSQL (the first run downloads its image once), applies the schema,
+# creates your first corpus and records the database for every later command.
+# Run it again any time; it changes nothing.
+$ verilore init
+
+# Ingest a plain ADR. No frontmatter, no `claims:` block: headings, list items and
+# `Key: Value` lines become claims, each quoted from the file it came from.
+# docs/adr/001-datastore.md is the worked example; point this at your own.
+$ verilore ingest-repo ./docs/adr --corpus project
+
+# Recall. An ambiguous answer prints the claims it could not separate, with ids.
+$ verilore recall "What is the primary datastore?" --corpus project
+
+# Record what replaces it. `--topic-key` retires what is live under that key, across
+# files: the new statement is a different document from the old one.
+$ verilore remember "The primary datastore is PostgreSQL 16." \
+  --corpus project --key architecture.datastore --topic-key architecture.datastore
+
+# What is true now, and what it displaced.
+$ verilore recall "What is the primary datastore?" --corpus project
+$ verilore history "" --corpus project
+
+# Verify the answer offline: no database, no model, no network.
+$ verilore receipt "What is the primary datastore?" --corpus project -o receipt.json
+$ verilore verify receipt.json
+```
+
+Nothing needs exporting. `init` records the database in `~/.verilore/config.toml`
+(mode 0600), and every command and `verilore-mcp` read it; an exported
+`DATABASE_URL` still wins. The container it creates is `verilore-postgres`,
+listening on 127.0.0.1:5432 only, with its data in the `verilore-pgdata` volume,
+so removing the container loses no memory. To use a PostgreSQL you already run,
+`verilore init --database-url ...` once; see
+[Running against your own PostgreSQL](docs/deployment.md#running-against-your-own-postgresql).
+Local mode needs no secrets; a server deployment still takes them from the
+environment.
+
+Working on Verilore itself? Install from a clone instead, then run the same commands:
+
+```bash
+git clone https://github.com/raunakdey-07/verilore.git && cd verilore
+uv venv --python 3.13 && . .venv/bin/activate && uv pip install -e '.[cli,mcp]'
+```
+
+The first `recall` builds an ONNX session: about 1.4 s, then 0.3 s. A background
+runtime holds it and the connection pool warm after that;
+`verilore runtime status` says whether one is up. `VERILORE_RUNTIME=0` turns
+it off, and `VERILORE_LEXICAL=1` turns the model off.
+
+Something wrong? Run `verilore doctor`.
+
+`pip install -e '.[cli,mcp]'` resolved 79 distributions totalling 216 MB, of which
+the three embedding packages are 79 MB (measured before `psycopg2-binary` and
+`pgvector`, two small packages, became core dependencies so `init` can migrate). `sentence-transformers` and torch are the
+`[torch]` extra and add about 1.35 GB. The extra is not needed for recall, and the
+two backends return the same vectors -- measured minimum cosine 0.99999833 -- so it
+buys a different import time and nothing else. The one thing that does need it is
+`rerank=true` on the REST search endpoint, which asks for the cross-encoder
+reranker; on the default stack that raises, because returning unreranked results
+under a rerank request would be a lie. `verilore search` and every other command
+leave it off.
+
+Your agent gets the same commands over MCP, with the same `match_status` and
+`candidates` on the answer and the same `supersedes_claim_id` on the write, which
+takes an id prefix or a phrase from the claim's own text. A document can say so
+itself: `supersedes: 0001.md` in its frontmatter. Point the client at
+`verilore-mcp`: it uses the database `init` recorded unless the client's config
+sets `DATABASE_URL`, and `VERILORE_INGEST_ROOTS` limits the directories it may
+read. The JSON for OpenCode, Zed and Claude Code is in [connecting an agent](docs/mcp.md).
+
+`recall` and `remember` also report a `query_id`. Grade a wrong answer; it appends
+to `~/.verilore/logs/queries.jsonl` and changes nothing else.
+
+```bash
+verilore feedback <query_id> --verdict wrong --note "meant the cache"
+verilore feedback-summary
+```
+
+## Managing corpora and credentials
+
+- `verilore ingest-repo <path> --delete-removed` retires documents whose source file is gone.
+- `verilore corpus reset <name> --yes` erases and re-initialises one corpus, with its grants intact.
+- `verilore corpus delete <name> --yes` removes a corpus entirely.
+- `verilore posture` reports whether the database role actually enforces row-level security.
+- `verilore credential issue|list|grant|ungrant|revoke` manages access without changing a secret.
+
+## Out-of-the-box Linux and WSL2
+
+On Linux and WSL2, `verilore init` starts a stopped container of ours, or creates
+`verilore-postgres` when nothing is running, with Podman or Docker; a remote
+database is never touched. When it cannot, it says why and what to do instead of
+a generic error: the install command for your distribution when there is no
+container engine, the engine's own error when the container will not start, and
+`--database-url` when port 5432 belongs to a program that is not PostgreSQL.
+Connection and authentication failures print the specific remediation (start the
+service, fix the password) instead of a traceback. `pytest` auto-detects a local
+development Postgres, so the suite runs with no `DATABASE_URL`.
+
+## Documents and claims
+
+`remember` is for facts you have in hand. A directory of Markdown you already have
+goes through `verilore ingest-repo ./docs`, and there are two ways for a document
+to become memory.
+
+**Plain Markdown needs no annotation.** A heading path scopes what follows it, and
+the claims under it are its list items, its numbered entries and its `Key: Value`
+lines. Every one is quoted back from the file it came from, so the evidence is the
+document's own bytes:
+
+```markdown
+# ADR 001: primary datastore
+
+- The primary datastore is PostgreSQL 15.
+- Writes go through the repository layer.
+
+## Status
+
+Status: Accepted
+```
+
+**A `claims:` block is the authoring interface** when you want to name the keys
+yourself. It says what to remember, and the evidence quote must appear **verbatim**
+in the body:
+
+```markdown
+---
+title: Deployment architecture
+claims:
+  - key: architecture.datastore
+    value: PostgreSQL
+    claim: The primary datastore is PostgreSQL.
+    evidence: The primary datastore is PostgreSQL.
+---
+
+# Deployment architecture
+
+The primary datastore is PostgreSQL. It runs in three availability zones.
+```
+
+A `claims:` block wins outright: if a document has one, the structural reader does
+not run on it. An author's key is a decision, and the tool does not second-guess it.
+
+What is extracted is never inferred. Nothing is summarised, reworded or merged; a
+claim is a line that was in the file, and its evidence is a character range of the
+archived chunk. See [docs/authoring.md](docs/authoring.md) for the exact-quote rule
+and both rejections with their messages.
+
+From Python, with no server and no subprocess:
+
+```python
+from verilore import Verilore
+
+client = Verilore("default")
+client.remember("Support answers within one business day.", key="support.sla")
+memory = client.recall("What is the support SLA?").current_memories[0]
+print(f"{memory.claim}  [{memory.status}]")
+```
+
+## What it does not do
+
+- **It does not decide what is true.** It records what was written, attributed.
+  Correctness of the original source is never established — only its provenance.
+- **It does not infer claims.** Every claim is a line from a document (a list
+  item, a `Key: Value` line, or, in a document with no list items, a rule-like
+  sentence) or a statement you gave it, quoted back unchanged.
+- **It is not a vector store.** Retrieval is one stage of a pipeline that ends in
+  provenance, not the product.
+- **It does not authenticate its own history.** A receipt proves internal
+  consistency. Trust requires an anchor you pinned yourself, outside this system.
+- **A draft section of an approved document is searchable.** Search and the
+  other chunk routes skip draft, rejected and superseded documents, but not a
+  `## Brainstorm` section inside an approved one (#138).
+- **No token budgets.** The `budget` argument is a character count of the JSON
+  response, not a token count.
+- **No metadata filters.** Scoping is by corpus and `path_prefix`.
+- **No single-claim deletion.** Withdrawal is a new `rejected` version of the
+  same key; the archive is append-only.
+- **No comparative benchmark result.** No number in this repository is evidence
+  of generalisation.
+- **Prose without rule-like sentences produces no claims.** A document with no
+  list items and no must/never/always/should sentences is stored as text only,
+  and the ingest warns `prose_not_extracted` (#158).
+- **Without the model, a text-only document is found by keyword only.** Under
+  `VERILORE_LEXICAL=1`, or when the model is not installed (the ingest then warns
+  `embedding_unavailable`), its text is stored without a vector until
+  `verilore reindex` adds one (#173).
+- **A supersession retires one claim.** `--supersedes` names it, or `--topic-key`
+  retires whatever is live under that key, and either works across files. Where two
+  documents disagree under one key and neither is retired, recall reports the
+  disagreement rather than picking one.
+- **A `claims:` block is YAML, and YAML is strict.** A backtick, a colon-space or
+  a leading `@` in an evidence quote discards the whole block. Quote the value.
+  The ingest now says `frontmatter_unparseable` instead of `no_claims_declared`.
+- **An agent can write memory, and that is a risk.** `memory_remember` is one
+  of 17 MCP tools and the first that writes. Without `file=` the evidence for the
+  claim is the statement itself, so it proves what the agent was told and not that
+  it is true ([why, and the review it needs](docs/authoring.md#memory_remember)).
+- **The install is 216 MB, not gigabytes**, unless you ask. Every latency and size
+  figure recorded up to v0.9.1 measured a `sentence-transformers` import, because
+  that was the default then; those figures describe the opt-in `[torch]` stack, not
+  what you get now. See [the install](#quickstart) for both sizes and what the extra
+  is for.
+- **`--as-of` queries need a timestamp you actually wrote at.** Memory is stamped
+  when it is recorded, so a time-travel query dated before the write returns
+  nothing. There is no backdating.
+- **Retrieval quality is measured on small frozen sets**, not on your corpus.
+  See [evaluation](docs/evaluation/) for what was actually measured, including
+  the questions the current system gets wrong.
+
+## What is measured
+
+Two held-out numbers, and neither is superseded by the other:
+
+| benchmark | result | what it is |
+|---|---|---|
+| M006.75 frozen held-out | **45/60 (75.0%)** exact on current source | the frozen benchmark, safety invariants at 60/60 |
+| independently authored, 157 questions | **131/157 (83.4%)** | a generalisation figure, and a known limitation |
+
+Both are reported because reporting only the better one would be the dishonest
+choice. v0.9.0 changed no benchmark input, policy, evaluator semantic,
+tokenizer or threshold, and that is measured: all 60 canonical per-question
+decisions are identical to `v0.8.0`. [The reproducibility report](docs/evaluation/m00675-reproducibility.md)
+records one discrepancy that release found and did not paper over.
+
+## Head-to-head stale-fact benchmark
+
+A reproducible comparison between Verilore and a plain top-k chunk RAG baseline
+using the same ONNX embedding model. Run with:
+
+```
+DATABASE_URL=postgresql://mpadmin:secret@localhost:5432/verilore python scripts/benchmark_stale_facts.py
+```
+
+The script ingests a multi-evolution ADR and spec corpus, runs Verilore and
+three RAG baselines (plain top-k, recency-reranked, metadata-filtered) over
+33 questions across supersession, spec updates, half-absent compounds, and cached
+answer revalidation, and prints a comparison table.
+
+Latest run (illustrative; re-run to reproduce):
+
+| metric | verilore | plain_rag | rag_recency | rag_metadata |
+|---|---:|---:|---:|---:|
+| authoritative_top1_accuracy | 0.939 | 0.303 | 0.424 | 0.939 |
+| stale_contamination_rate | 0.000 | 0.970 | 0.758 | 0.000 |
+| compound_completeness | 1.000 | 0.000 | 0.167 | 1.000 |
+| abstention_accuracy | 1.000 | 0.500 | 0.500 | 0.500 |
+| cached_revalidation_accuracy | 1.000 | 0.000 | 0.000 | 0.000 |
+
+The corpus and questions were written by this project's author, so the table
+is a regression check, not evidence of comparative quality.
+
+## Reading order
+
+Four documents, and then stop.
+
+| | | |
+|---|---|---|
+| 1 | This file | what it is, and what it refuses to do |
+| 2 | [Quickstart](docs/quickstart.md) | the commands, expanded; every `$ ` line in it runs in CI |
+| 3 | [Integration guide](docs/integration/guide.md) | wiring Verilore into an app |
+| 4 | [Authoring memory](docs/authoring.md) | how to write a document that answers |
+
+## Everything else — later
+
+| | |
+|---|---|
+| [Local runtime and model-free mode](docs/runtime.md) | the warm process, and running with no model |
+| [Deployment and authentication](docs/deployment.md) | health, observability, credentials, multi-tenancy |
+| [Security](docs/security.md) | threat model, credential handling, what is logged |
+| [Errors](docs/errors.md) | every code the CLI and API return |
+| [Deletion and erasure](docs/deletion-and-erasure.md) | removing a person's data |
+| [Operational memory feed](docs/feed.md) | ordering, cursors, consistency |
+| [Providers](docs/providers.md) | LLM and embedding providers |
+| [Architecture and the memory model](docs/architecture/) | how the layers fit; why memory beyond RAG |
+| [Surfaces](docs/quickstart.md#the-full-walkthrough) | CLI, SDK, REST, MCP, and what each can reach |
+| [Status](docs/STATUS.md) | what is measured, what is outstanding |
+| [Changelog](CHANGELOG.md) | every release, and every fix |
+| [Release map](docs/release-map.md) | milestone to version |
+| [Evaluation](docs/evaluation/) | the frozen benchmarks, and their results |
+| [Progress](docs/archive/PROGRESS.md) | one line per phase; [full history](docs/archive/internal/progress-history.md) |
+| [Examples](examples/) | the product in one file: [decision memory](examples/decision-memory/), [project log](examples/project-log/) |
+| [Withdrawn](docs/archive/withdrawn/README.md) | material deliberately removed, and why |
+
+## Contributing
+
+```bash
+uv venv --python 3.13 && . .venv/bin/activate
+uv pip install -e '.[cli,mcp,dev]'
+pytest -q
+```
+
+The suite needs PostgreSQL with pgvector: `verilore init` starts one, or from the
+checkout `docker compose up -d postgresql` starts the one in `docker-compose.yml`.
+It will not run against an unreachable database — it fails instead of skipping
+everything.
+[CONTRIBUTING.md](CONTRIBUTING.md) has the rest, and [SECURITY.md](SECURITY.md)
+says how to report a vulnerability privately.
+
+## License
+
+Apache 2.0. See [LICENSE](LICENSE).

verilore-0.11.0/docs/pypi.md

@@ -0,0 +1,55 @@
+# Verilore
+
+Memory for AI applications that remembers what changed, what was true when, and
+why to believe the recorded state. Add Verilore to an application, record a fact,
+and get back an answer with its source, the time it was true, and the exact
+characters that support it. Export a receipt and verify it on a machine that has
+never heard of Verilore.
+
+## Install
+
+```bash
+uv tool install --python 3.13 verilore
+# or, with a Python from 3.11 to 3.14:
+pipx install verilore
+```
+
+Verilore runs on macOS and Linux, and on Windows through WSL 2, with Python 3.11
+to 3.14 (3.13 at most on an Intel Mac). uv downloads 3.13 if you do not have it,
+which also covers a system whose own Python is newer, such as Fedora 45's 3.15
+(Fedora's uv downloads only when asked: run `uv python install 3.13` first).
+It needs PostgreSQL 15 or newer with pgvector: with Podman or Docker installed,
+`verilore init` starts one for you, and to use one you already run, pass
+`verilore init --database-url ...`.
+[Your system](https://github.com/raunakdey-07/verilore/blob/main/docs/quickstart.md#your-system)
+says how to get uv and Podman on each.
+
+## Quickstart
+
+```bash
+verilore init
+verilore ingest-repo ./docs --corpus project
+verilore recall "What is the primary datastore?" --corpus project
+verilore explain "What is the primary datastore?" --corpus project
+```
+
+`init` sets up the database and records it for every later command, so nothing
+needs exporting. Something wrong? Run `verilore doctor`.
+
+From Python:
+
+```python
+from verilore import Verilore
+
+client = Verilore("default")
+client.remember("Support answers within one business day.", key="support.sla")
+memory = client.recall("What is the support SLA?").current_memories[0]
+print(f"{memory.claim}  [{memory.status}]")
+```
+
+## Links
+
+- [README](https://github.com/raunakdey-07/verilore#readme): what it is, and what it refuses to do
+- [Integration guide](https://github.com/raunakdey-07/verilore/blob/main/docs/integration/guide.md): wiring it into an app
+- [Changelog](https://github.com/raunakdey-07/verilore/blob/main/CHANGELOG.md)
+- [License: Apache-2.0](https://github.com/raunakdey-07/verilore/blob/main/LICENSE)