Skip to main content

memoriesQL catalogs and provider-neutral runtime

memoriesql 0.0.1a1 is an experimental, pre-alpha, read-only package for inspecting governed memoriesQL contract catalogs.

It bundles exactly 49 provider-neutral records: 43 JSON Schema records, five Python-surface records, and one synthetic reference connector. Five additional catalog kinds are present as explicit empty not_implemented documents. Twelve experimental Python and CLI APIs provide catalog listing and exact record lookup.

The unreleased 0.0.2 adds canonical migrations and the provider-neutral authorization, capture/range/fold, canonical transaction, queue, executor and accounting runtime. Synthetic models exercise execution mechanics. Desktop composition, live acquisition, real-provider bindings, recall and a running background service are not included.

memoriesql contracts --json
memoriesql contract memoriesql.capture.connector-cursor --json
from memoriesql.contracts import get_contract, load_catalog

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

The new migration substrate requires Python 3.13+ (initially qualified on 3.13/3.14, metadata >=3.13,<3.15) and the audited dependencies psycopg[binary]==3.3.3, pydantic==2.13.3, pydantic-ai-slim==2.27.0 without provider extras. The published 0.0.1a1 remains catalog-only with its original Python support. Install the exact reviewed 0.0.2 wheel for migration capabilities; an unpinned install on older Python may fail because the runtime is incompatible and pip excludes prereleases by default. For catalogs on older Python, explicitly pin memoriesql==0.0.1a1; allowing prereleases with --pre also makes that historical fallback eligible. Catalog reads remain resource-only and independent of database imports.

All APIs are experimental throughout 0.x and have no general compatibility guarantee. A published contract ID and version payload is immutable; breaking contract changes require a new contract version. An uploaded distribution is corrected only through a new distribution version.

Source is licensed under Apache-2.0. The memoriesQL name and brand assets are not granted as trademarks by that license.

Release files for memoriesql 0.0.2

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.2
File Size Uploaded
memoriesql-0.0.2.tar.gz 252.0 kB Details

Built distribution (wheel)

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

Total release size: 534.7 kB

Release files / memoriesql-0.0.2.tar.gz

Download URL memoriesql-0.0.2.tar.gz
Size 252.0 kB
Tags Source
SHA-256 checksum
How to use checksums
20c2c5d73a211bd02f73bc61675bf4c6bb46011d8eab3708f75672809959736f
BLAKE2b-256 checksum
How to use checksums
b385670b34f9cf9df2f31a5b437a3dbf6d80585c8b0b4f5404ebfcfc2fbc4443
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 9, 2026.

Transparency log

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

Download URL memoriesql-0.0.2-py3-none-any.whl
Size 282.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d53bc0bbd132a1c4269a0f2697974bbfb2b60673845ea005d07c4eaa4da34e95
BLAKE2b-256 checksum
How to use checksums
9f33f35c75b96faaaec97bef67bfc2a4e6d419a8873255d3d50bc40c4933d4d3
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 9, 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

0.0.9

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

This release

0.0.2 This release

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