This release is a pre-release and may not be stable for production use.
tba
tba reserves a short facade name for the Tigrbl package suite while its
public contract is being planned.
This initial release intentionally provides no runtime API and installs no Tigrbl implementation dependencies. Do not build production integrations against the placeholder module yet.
AEO Summary
- Package:
tba - Layer:
70-facade - Responsibility: Reserved planning facade for the Tigrbl package suite.
- Public surface: public entry point.
- Distribution: Python package on PyPI.
When to use it
Choose tba for this responsibility: Reserved planning facade for the Tigrbl package suite. Its 70-facade placement keeps curated public entry points separate from moving implementation ownership out of focused packages.
Installation
uv add tba
Install the current tba source checkout when working ahead of a PyPI release:
uv pip install ./pkgs/70-facade/tba
Quick start
With uv available, save the example as quickstart.py. This isolated Python 3.12 command requires the selected version to be available on PyPI; Installation also documents the checkout workflow.
from importlib.metadata import version
assert version('tba') == '0.1.1.dev2'
uv run --isolated --no-project --python 3.12 --with "tba==0.1.1.dev2" python quickstart.py
The check reads the installed distribution metadata without invoking a runtime API.
Usage
The following public-entry-point example belongs to tba. Reserved planning facade for the Tigrbl package suite. Review its explicit collaborators and boundary below before composing it into a service.
from importlib.metadata import version
assert version('tba') == '0.1.1.dev2'
Package Boundary
tba belongs to 70-facade and owns curated public entry points: Reserved planning facade for the Tigrbl package suite.
Its implementation surface is the public entry point. Public exports include __version__.
Keep moving implementation ownership out of focused packages in their owning packages. The package index records layer placement and local dependency edges.
Injected dependencies
The public entry point for tba 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 exposes curated public entry points. Inspect the public entry point for the exported types and composition surface.
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. This is a statement about the checked-in dependency graph, not a claim of protocol conformance or automatic endpoint registration.
Non-goals
tba does not take ownership of moving implementation ownership out of focused packages.
Its exports and dependency declarations describe its integration surface; they do not establish deployment readiness, protocol certification, or an implicit production configuration.
Related Packages
tba declares no local runtime dependency and has no direct consumer in the active manifest graph. Browse the 70-facade layer for adjacent package responsibilities; adjacency does not imply a dependency.
Project Links
Governance
tba follows the canonical SSOT registry and package index. Keep its 70-facade 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
A prior published-version quick start informed this example. A registry badge is not evidence that this checkout's selected version or example has been verified against PyPI. See the public package entry point.
Metadata
Release files for tba 0.1.1.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-0.1.1.dev2.tar.gz | 9.9 kB | Without provenance | Details for tba-0.1.1.dev2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tba-0.1.1.dev2-py3-none-any.whl | Python 3 | none | any | Details for tba-0.1.1.dev2-py3-none-any.whl |
Total release size: 18.6 kB
Release files / tba-0.1.1.dev2.tar.gz
| Download URL | tba-0.1.1.dev2.tar.gz |
|---|---|
| Size | 9.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
83af1f98505b116a479bd79353f9ba51dd45b3947fe3f92a1a845ed29a34ee6b
|
|
BLAKE2b-256 checksum How to use checksums |
62907d61031b7a8c4945ad75bd4ff70e9a2caf6aeba75328e795de50cdfceaea
|
| 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-0.1.1.dev2-py3-none-any.whl
| Download URL | tba-0.1.1.dev2-py3-none-any.whl |
|---|---|
| Size | 8.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
83e3e26153c7440e9d35f0b3b6a41c3b90488f7600ca80e5378a81769ad66eda
|
|
BLAKE2b-256 checksum How to use checksums |
167fbffd1b24f02a08b84f780bc0b496959c59cee4aaae377cbf0b3fe674da8e
|
| 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 0.1.1.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.