Skip to main content

registry-stack-client

One versioned Python package for the Discovery, Evidence, Base Registry Engine, Casework, Messaging, and Scheduling client APIs in Registry Stack.

The distribution installs as registry-stack-client and imports as registry_client. The two spellings differ, so import registry_stack_client raises ModuleNotFoundError.

python -m pip install "registry-stack-client==<version>"
from registry_client import breg, casework, discovery, evidence, messaging, scheduling

registry = breg.BaseRegistryClient("https://registry.example.invalid/")
inbox = casework.CaseworkClient("https://casework.example.invalid/")
messages = messaging.MessagingClient("https://messaging.example.invalid/")
appointments = scheduling.SchedulingClient("https://scheduling.example.invalid/")

Each product remains in its own module namespace, registry_client.breg, registry_client.casework, registry_client.discovery, registry_client.evidence, registry_client.messaging, and registry_client.scheduling, because each product's routing, authentication, errors, and verification rules are different. These namespaces also keep the unified distribution's files disjoint from earlier standalone client distributions, so installing or uninstalling either package cannot remove files owned by the other. The unified package is published beginning with Registry Stack v0.26.1. The casework namespace is part of the unified package beginning with Registry Stack v0.30.0. The messaging namespace is part of the unified package beginning with Registry Stack v0.38.0. The scheduling namespace is part of the unified package beginning with Registry Stack v0.40.0. Existing standalone client packages remain available for earlier versions, but later releases use this unified entry point.

Wheels cover macOS arm64, Linux arm64 with glibc, and Linux x64 with glibc, and require glibc 2.17 or newer on Linux. Install the exact client version that matches the deployment.

The Casework client supports reviewer inbox ownership filters and the separate supervisory_review_tasks discovery method. Supervisory rows carry bounded task and accountability references with a holder-free string state; a single decided-task read exposes a decisionReceipt only to the caller who recorded that decision.

The registry_client.breg namespace includes the typed retained-history page, proposal, and inert result-reference classes exposed by the maintained BReg binding. Their helpers inspect only an already loaded page and do not fetch targets or advance pagination.

The crates/registry-stack-client-py directory in the Registry Stack repository holds this public metadata and the Python facade. It is not built directly. release/scripts/assemble-registry-client-wheel.py combines the six version-matched internal native wheels with the facade and emits the only publishable Python distribution, using this file as the PyPI description.

Metadata

Release files for registry-stack-client 0.41.0

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

Built distributions (wheels)

Table of built distributions (wheels) for registry-stack-client 0.41.0
File Interpreter ABI Platform
registry_stack_client-0.41.0-cp311-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.11 abi3 Linux glibc 2.17+ x86-64 Details
registry_stack_client-0.41.0-cp311-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.11 abi3 Linux glibc 2.17+ ARM64 Details
registry_stack_client-0.41.0-cp311-abi3-macosx_11_0_arm64.whl CPython 3.11 abi3 macOS 11.0+ ARM64 Details

Total release size: 55.2 MB

Release files / registry_stack_client-0.41.0-cp311-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL registry_stack_client-0.41.0-cp311-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 19.8 MB
Tags CPython 3.11 Linux glibc 2.17+ x86-64 abi3
SHA-256 checksum
How to use checksums
511bdde0179e4b15474f68aca56a61fcd64910f18a42773c81196709b4572de5
BLAKE2b-256 checksum
How to use checksums
3af831374435ce935cf4b0d97989382014376bcf74ed6dccaf93a822d4d9c192
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 Oct 13, 2026.

Transparency log

Release files / registry_stack_client-0.41.0-cp311-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL registry_stack_client-0.41.0-cp311-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 18.3 MB
Tags CPython 3.11 Linux glibc 2.17+ ARM64 abi3
SHA-256 checksum
How to use checksums
4afdef85a96e21c776cbff28373a825e514498c8f808f7303d7595417fac46dc
BLAKE2b-256 checksum
How to use checksums
b45a68be32dc28d8a3ea33e4103cb1a9c8e0b3c7a29b3739a6e3e1dcf5322b91
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 Oct 13, 2026.

Transparency log

Release files / registry_stack_client-0.41.0-cp311-abi3-macosx_11_0_arm64.whl

Download URL registry_stack_client-0.41.0-cp311-abi3-macosx_11_0_arm64.whl
Size 17.0 MB
Tags CPython 3.11 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
c92db44845d08809aeed8d65dc2e32df8a5d8b471ee99f09d9e026fd59ffad0b
BLAKE2b-256 checksum
How to use checksums
c81a25d7c31f21a2c52c75a89fb588a3335efb7195676291a56531546a57d230
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 Oct 13, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.41.0 This release

3 release files

0.40.0

3 release files

0.37.0

3 release files

0.36.0

3 release files

0.35.0

3 release files

0.34.0

3 release files

0.33.0

3 release files

0.32.0

3 release files

0.31.0

3 release files

0.30.0

3 release files

0.29.0

3 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