This release is a pre-release and may not be stable for production use.
tba-runtime-identity-storage
Aggregate runtime for the split layer-30 durability packages.
Table specifications use Tigrbl's public makeOp, defineTableSpec,
deriveTableSpec, provideTableSpec, and activateTableSpec functions.
Table-family operations remain in their standalone *-durability owner; this
aggregate package collects and activates them without defining factory aliases.
Layer 30 owns carrier-neutral Tigrbl operations, derived table specifications, and durability hooks. It does not own tables or migrations (layer 01), semantic contracts (layer 02), provider selection (layer 20), engine construction (layer 60), HTTP routes, or protocol wire models.
Each durability package imports its table classes directly from the corresponding layer-01 domain storage package and declares those dependencies. This aggregate additionally depends on storage-core for full composition and legacy migration discovery.
1 maintainer
Metadata
1 maintainer
Release files for tba-runtime-identity-storage 0.4.0.dev2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tba_runtime_identity_storage-0.4.0.dev2.tar.gz | 37.8 kB | Without provenance | Details for tba_runtime_identity_storage-0.4.0.dev2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tba_runtime_identity_storage-0.4.0.dev2-py3-none-any.whl | Python 3 | none | any | Details for tba_runtime_identity_storage-0.4.0.dev2-py3-none-any.whl |
Total release size: 103.8 kB
Release files / tba_runtime_identity_storage-0.4.0.dev2.tar.gz
| Download URL | tba_runtime_identity_storage-0.4.0.dev2.tar.gz |
|---|---|
| Size | 37.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5eb89628376f53cafb84c7f3551e8b6a0216d09834ddcdcd69ea32cb867132ae
|
|
BLAKE2b-256 checksum How to use checksums |
ca59239450e2573b78ba1fa6e6200b9f4373b9a91457acb05afc69ceebce4083
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / tba_runtime_identity_storage-0.4.0.dev2-py3-none-any.whl
| Download URL | tba_runtime_identity_storage-0.4.0.dev2-py3-none-any.whl |
|---|---|
| Size | 66.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d76af145fdb26c8f6da8c39fe192f7a5946f5565c14ece7fce9a001d855572bc
|
|
BLAKE2b-256 checksum How to use checksums |
495e9618bdc323b07a7228b6750ccf6d7bf1ee3e6a20a73a6d06cdc292d4676b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for tba-runtime-identity-storage 0.4.0.dev2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
