Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

tba-protocol-workload-wimse-identifier

TBA · Tigrbl Auth

Checkout: 0.4.0.dev4 Python: >=3.10,<3.16 License: Apache-2.0 Notice: attribution Layer: 50 protocols PyPI version for tba-protocol-workload-wimse-identifier

Monthly PyPI downloads for tba-protocol-workload-wimse-identifier README hits for tba-protocol-workload-wimse-identifier SSOT: governed Evidence: verification

Parse and normalize native WIMSE workload identifiers.

AEO Summary

  • Package: tba-protocol-workload-wimse-identifier
  • Layer: 50-protocols
  • Responsibility: WIMSE workload identifier parsing and validation.
  • Public surface: public entry point.
  • Distribution: Python package on PyPI.

When to use it

Choose tba-protocol-workload-wimse-identifier for this responsibility: WIMSE workload identifier parsing and validation. Its 50-protocols placement keeps protocol semantics and projections separate from deployment hosting or ownership of persistence implementations.

Installation

Install the selected PyPI release of tba-protocol-workload-wimse-identifier:

uv pip install tba-protocol-workload-wimse-identifier

To work on the current checkout before a prepared release is published:

uv pip install ./pkgs/50-protocols/tba-protocol-workload-wimse-identifier

Quick start

Build the package from the repository root.

uv build --wheel pkgs/50-protocols/tba-protocol-workload-wimse-identifier

Usage

The following public-entry-point example belongs to tba-protocol-workload-wimse-identifier. WIMSE workload identifier parsing and validation. Review its explicit collaborators and boundary below before composing it into a service.

import tba_protocol_workload_wimse_identifier

print(tba_protocol_workload_wimse_identifier.__name__)

Package Boundary

tba-protocol-workload-wimse-identifier belongs to 50-protocols and owns protocol semantics and projections: WIMSE workload identifier parsing and validation.

Its implementation surface is the public entry point. Public exports include WorkloadIdentifier, SPECIFICATION_URI, SPECIFICATION_VERSION.

Keep deployment hosting or ownership of persistence implementations in their owning packages. The package index records layer placement and local dependency edges.

Injected dependencies

The public entry point for tba-protocol-workload-wimse-identifier does not declare an explicit service-constructor or keyword-only factory hook in the inspected source. Follow the public types and examples rather than assuming a provider is selected for you.

Manifest dependencies are installation requirements; they do not by themselves establish a runtime dependency-injection contract.

Operations and readiness

tba-protocol-workload-wimse-identifier exposes protocol semantics and projections. Public operations found in its source:

  • WorkloadIdentifier.parse — source.

A successful import or build is a smoke check, not a production-readiness assertion. Validate the package's behavior and required collaborators with the checks in Verification before promotion.

Protocol consumers

No active layer-50 manifest declares a direct runtime dependency on tba-protocol-workload-wimse-identifier. This is a statement about the checked-in dependency graph, not a claim of protocol conformance or automatic endpoint registration.

Other direct consumers include tba-profile-workload-authentication-wimse-mtls, tba-profile-workload-credential-wimse-wic, tba-profile-workload-credential-wimse-wit, tba-runtime-identity.

Non-goals

tba-protocol-workload-wimse-identifier does not take ownership of deployment hosting or ownership of persistence implementations.

Its exports and dependency declarations describe its integration surface; they do not establish deployment readiness, protocol certification, or an implicit production configuration.

Direct downstream consumers:

Governance

tba-protocol-workload-wimse-identifier follows the canonical SSOT registry and package index. Keep its 50-protocols ownership, public imports, declared dependencies, examples, and release metadata aligned.

Changes must pass the README standards gate, package checks, and the evidence requirements relevant to the changed behavior. Update SSOT through the repository's CLI workflow when changing governed claims or boundaries.

Verification

Check that the build produces a wheel with the package version declared in pyproject.toml.

Metadata

Release files for tba-protocol-workload-wimse-identifier 0.4.0.dev4

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

Source distribution (sdist)

Source distribution for tba-protocol-workload-wimse-identifier 0.4.0.dev4
File Size Uploaded Provenance Actions
tba_protocol_workload_wimse_identifier-0.4.0.dev4.tar.gz 8.4 kB Without provenance Details for tba_protocol_workload_wimse_identifier-0.4.0.dev4.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for tba-protocol-workload-wimse-identifier 0.4.0.dev4
File Interpreter ABI Platform Actions
tba_protocol_workload_wimse_identifier-0.4.0.dev4-py3-none-any.whl Python 3 none any Details for tba_protocol_workload_wimse_identifier-0.4.0.dev4-py3-none-any.whl

Total release size: 18.6 kB

Release files / tba_protocol_workload_wimse_identifier-0.4.0.dev4.tar.gz

Download URL tba_protocol_workload_wimse_identifier-0.4.0.dev4.tar.gz
Size 8.4 kB
Tags Source
SHA-256 checksum
How to use checksums
bdd4370ff27c3d1ec9cae03bb5ded368088bf6a938e739fbe4946db1db550346
BLAKE2b-256 checksum
How to use checksums
8dfc5076d485817df710f7d705f35cc9ae26e4643368695cc06e1c90c5fcfe48
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","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_protocol_workload_wimse_identifier-0.4.0.dev4-py3-none-any.whl

Download URL tba_protocol_workload_wimse_identifier-0.4.0.dev4-py3-none-any.whl
Size 10.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b543dd5cbb7cc732528e41760b5e40f551977ccd359d4fc38b15cd165554dbae
BLAKE2b-256 checksum
How to use checksums
63afde0b91bf96d3518e310881e5013f5704010f402cb87d0a02568c1acc3f65
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","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-protocol-workload-wimse-identifier 0.4.0.dev4

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.

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