Skip to main content

memoriesQL

Build memories with meaning.

memoriesQL is an open-source, local-first memory foundation for AI agents. It preserves authorized evidence in PostgreSQL and supports agent-authored structured observations with inspectable source support.

The memoriesql package provides the provider-neutral open core: canonical migrations, versioned contracts and composable Python runtime mechanics. It is not the memoriesQL desktop product or a configured background memory service.

Experimental / pre-alpha. Installed fictional tests qualify mechanics, not real-provider quality or production readiness. Applications must supply source qualification, authority, worker composition and qualified model bindings.

Install and explore

Use Python 3.13 or 3.14 (>=3.13,<3.15). This page describes the 0.0.9 distribution. Until its publication is independently verified, use the reviewed local wheel; after publication, install the exact pin below. Published 0.0.8 remains available without the new schema 25/26 capabilities.

python3.13 -m pip install memoriesql==0.0.9
memoriesql --version
memoriesql contracts --json
memoriesql contract memoriesql.capture.connector-cursor --json
from memoriesql.contracts import get_contract, load_catalog

schemas = load_catalog("json_schema")
cursor_contract = get_contract("memoriesql.capture.connector-cursor")

Catalog inspection uses bundled resources without a database, provider credentials or external service access. The CLI does not start a memory service. The historical 0.0.1a1 catalog-only preview is not a runtime fallback.

What you can build on

  • Durable authorized raw capture, receipt-backed progress and retained-fold recovery.
  • Stable qualified source identity and immutable evidence packages.
  • A durable semantic-task queue with fenced execution, cancellation and accounting.
  • Structured observations, explicit distinct-bead corrections, local entity mentions and attributable classification.
  • Authorized source revisiting and stored-memory/evidence inspection without inference on reads.

A bead is a source-anchored observation whose statements carry meaning, attribution, conditions and uncertainty. Its short title and summary are human navigation, not replacement evidence. Meaning is authored by an agent or human; deterministic code validates and persists it.

Version 0.0.9 combines declared evidence scopes (schema 25), explicit supervised managed dispatch (schema 26), and terminal-failure cleanup that retains errors without claiming a failed write persisted. Hard-bounded model admission remains the default; supervised managed dispatch requires separate exact approval and records its allowances and reported or unavailable usage truthfully. The package supplies no provider adapter or live-call permission. No live-provider semantic quality, production recall or complete-input correction/reauthoring is claimed.

Explicit composition, not automatic setup

Installation does not migrate PostgreSQL, grant access, provision trusted producers, activate tasks, start workers or configure a provider. Consumers must explicitly compose those operations and authorize any disclosure to a model. Core dependencies do not include provider extras.

Required target evidence must be supplied through the trusted execution path; mechanical exposure does not prove comprehension or whole-source completeness. Incomplete work stays incomplete. Hosts retain the worker/event loop through wait_for_cleanup(); cancellation is not proof of remote termination, rollback or reconciled usage.

Start with the repository guide, migration operations, caller composition and model admission. Development documentation may describe changes not yet published; check its release status before adopting them.

Compatibility and license

All 0.x APIs are experimental, with no general compatibility guarantee. Published contract payloads remain immutable; breaking payload changes require a new contract version, and changed published artifacts require a new distribution version. Pin releases and apply migrations explicitly.

Public core owns the canonical schema and provider-neutral runtime. Desktop surfaces, source-specific acquisition/parsing, installers, provider bindings, hosted services and sync are outside this package.

Source is Apache-2.0 licensed. The memoriesQL name and artwork remain John Inniger's trademarks under the trademark policy. Contributions use the Developer Certificate of Origin.

Release files for memoriesql 0.0.9

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for memoriesql 0.0.9
File Size Uploaded
memoriesql-0.0.9.tar.gz 487.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for memoriesql 0.0.9
File Interpreter ABI Platform
memoriesql-0.0.9-py3-none-any.whl Python 3 none any Details

Total release size: 1.0 MB

Release files / memoriesql-0.0.9.tar.gz

Download URL memoriesql-0.0.9.tar.gz
Size 487.4 kB
Tags Source
SHA-256 checksum
How to use checksums
d2fe62d61bd583cc91c3cff75768c87bb5bf5be54f2ae6aa9e0822d0df04f4b0
BLAKE2b-256 checksum
How to use checksums
b3b6fe27b46d7d0fdac73863dae907f6334853dd5f0fb12aa998cb377fcf05f7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.

Transparency log

Release files / memoriesql-0.0.9-py3-none-any.whl

Download URL memoriesql-0.0.9-py3-none-any.whl
Size 546.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
76cb16c86418696d3eaaf3f00f01b58bac037711115b1607408f15b9f463c52d
BLAKE2b-256 checksum
How to use checksums
89090ce81e478b698b9f1c4e179991583abb3e73d86c8bf6555f7b4f3781af1b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.

Transparency log

Release history Release notifications | RSS feed

0.0.12

2 release files

0.0.11

2 release files

0.0.10

2 release files

This release

0.0.9 This release

2 release files

0.0.8

2 release files

0.0.7

2 release files

0.0.6

2 release files

0.0.5

2 release files

0.0.4

2 release files

0.0.3

2 release files

0.0.2

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page