Skip to main content

memoriesQL catalogs and provider-neutral runtime

memoriesql is an experimental, pre-alpha package for governed contract catalogs and provider-neutral runtime mechanics. The immutable 0.0.1a1 release remains catalog-only.

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.

Published 0.0.2 introduced 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 an exact released runtime version 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. Published 0.0.3 establishes cleanup retention independently of a blocked ordinary heartbeat while retaining ownership of unfinished work.

Unreleased 0.0.4 adds schema 15 and explicit version-2 initial-authoring and correction commands. Accepted meaning, type and summary are immutable. Corrections create new beads with explicit pinned supersession; independent branches and multi-target reconciliation are supported without choosing a global winner. Occurrence replay still returns the original initial bead. Historical versions and successful version-1 receipts remain readable under current authority. Legacy attempts to revise an accepted bead fail explicitly and require an updated caller. Publication and product adoption require separate authorization.

Release files for memoriesql 0.0.4

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.4
File Size Uploaded
memoriesql-0.0.4.tar.gz 273.0 kB Details

Built distribution (wheel)

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

Total release size: 577.6 kB

Release files / memoriesql-0.0.4.tar.gz

Download URL memoriesql-0.0.4.tar.gz
Size 273.0 kB
Tags Source
SHA-256 checksum
How to use checksums
505ef59a2401813250816334f370b8ea05359b08c174f4865fe49fd8623bdf6e
BLAKE2b-256 checksum
How to use checksums
4d5941a2e573fe7202da7d413f8008a69ef5c3531ba1cffc8161c59cc3b793a1
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 10, 2026.

Transparency log

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

Download URL memoriesql-0.0.4-py3-none-any.whl
Size 304.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
928bd443e30d1d5fb70b0aa4b1c96245ad31ba67fe4bb20b2f7335d62166fa7c
BLAKE2b-256 checksum
How to use checksums
2d45ec6c472b4d51ade5bf585f1a69cc62c4a9e47214d99cfa176cfc02531ded
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 10, 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

This release

0.0.4 This release

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