This release is a pre-release and may not be stable for production use.
tigrbl-runtime
Execution bridge for compiled Tigrbl kernel plans and narrow runtime context/carrier compatibility.
What is tigrbl-runtime?
tigrbl-runtime executes compiled Tigrbl kernel plans and preserves the narrow runtime context/carrier bridge needed to run those plans. Route selection, protocol fallback policy, response shaping, transport envelopes, and operation semantics are owned by kernel, atoms, and ops packages.
Why use tigrbl-runtime?
Use it when you need this foundational Tigrbl layer directly as a small, focused dependency.
When should I install tigrbl-runtime?
Install it for extension packages, package-local tests, or internals that need this boundary without the whole facade.
Who is tigrbl-runtime for?
Framework maintainers, extension authors, and advanced users composing Tigrbl from split packages.
Where does tigrbl-runtime fit?
tigrbl-runtime lives at pkgs/50_runtime/tigrbl_runtime and serves a focused layer in the split Tigrbl framework.
How does tigrbl-runtime work?
It owns a narrow layer in the split workspace and is consumed by higher-level packages through explicit dependencies.
Install
uv add tigrbl-runtime
pip install tigrbl-runtime
Surface Coverage
| Surface | Value |
|---|---|
| PyPI package | tigrbl-runtime |
| Repository path | pkgs/50_runtime/tigrbl_runtime |
| Python import root | tigrbl_runtime |
| Console scripts | none declared |
| Entry points | none declared |
| Optional extras | none declared |
| Legal files | LICENSE, NOTICE |
| Supported Python | `3.10 |
What It Owns
tigrbl-runtime owns the compiled-plan execution boundary. It should be installed when you need the narrow bridge that runs already-planned Tigrbl work without assuming the full facade is present.
Implementation orientation:
tigrbl_runtime: compiled plan execution, runtime context compatibility, and declared carrier lifecycle bridges
Runtime authoring BCP:
- Do use this package for executing compiled kernel plans and maintaining runtime context/carrier compatibility.
- Do keep execution aligned with compiled plans.
- Do not add route matching semantics, protocol fallback policy, JSON-RPC/REST envelope policy, response rendering, chunk emission semantics, operation behavior, or new executor families.
- Do not make application route handlers, FastAPI/Starlette objects, direct SQLAlchemy session calls, or ad-hoc engine construction the runtime contract.
- Do not bypass kernel plans or lifecycle phases when adding REST, JSON-RPC, stream, SSE, WebSocket, or WebTransport behavior.
- Avoid hiding behavior in runtime wrappers that diagnostics and compiled plans cannot inspect.
Public API and Import Surface
- Import roots:
tigrbl_runtime. - Public symbols:
Runtime,RuntimeBase. - Workspace dependencies:
tigrbl-typing,tigrbl-kernel,tigrbl-atoms,tigrbl-base,tigrbl-core. - External runtime dependencies:
numba>=0.61.2.
Usage Examples
Verify the installed package
python -m pip show tigrbl-runtime
python - <<'PY'
from importlib.metadata import version
print(version("tigrbl-runtime"))
PY
Import the package boundary
import importlib
module = importlib.import_module("tigrbl_runtime")
print(module.__name__)
Import a public symbol
from tigrbl_runtime import Runtime
print(Runtime)
Use with the facade when building applications
uv add tigrbl tigrbl-runtime
python - <<'PY'
import tigrbl
print(tigrbl.__name__)
PY
How To Choose This Package
Choose tigrbl-runtime when the quick-answer table matches your use case. Choose tigrbl instead when you want the full public facade. Choose a lower-level package such as tigrbl-core, tigrbl-base, or tigrbl-runtime when you are building framework extensions or testing a specific internal boundary.
Related Packages
Documentation Links
- Workspace docs
- Package catalog
- Package layout
- Current target
- Current state
- SSOT registry
- Release workflow
Support
- Community: Discord.
- Issues: GitHub Issues.
- Repository: pkgs/50_runtime/tigrbl_runtime.
Package-local Boundary
This README is the package-local distribution entry point for tigrbl-runtime. It answers install, usage, API, ownership, and certification-orientation questions for this package. Broader architectural decisions, release status, and cross-package proof chains remain in the repository-level docs and SSOT registry.
Certification Status
- Package status: governed package in the
tigrbl/tigrblworkspace. - Governance source: SSOT registry.
- Release evidence: publish workflow validates package builds, tests, GitHub release assets, and PyPI publication for managed packages.
- Local certification guard:
pkgs/97_tests/tigrbl_tests/tests/unit/test_package_badges_and_notices.pyverifies every package README keeps the Discord badge, Apache 2.0 badge, explicit Python-version badge,LICENSE, andNOTICE. - Scope note: this README documents the package boundary. Runtime feature support remains governed by
.ssot/entities and the conformance docs linked below.
License
Licensed under the Apache License, Version 2.0. See LICENSE, NOTICE, and the official Apache 2.0 license text.
Lowering integration
lowering_services lazily exposes canonical kernel operation-view compilation and WebSocket JSON-RPC session construction to concrete integration code. It preserves the kernel function objects and keeps kernel imports out of concrete authoring modules.
Metadata
Release files for tigrbl-runtime 0.4.5.dev10
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 |
|---|---|---|---|---|
| tigrbl_runtime-0.4.5.dev10.tar.gz | 65.7 kB | Without provenance | Details for tigrbl_runtime-0.4.5.dev10.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tigrbl_runtime-0.4.5.dev10-py3-none-any.whl | Python 3 | none | any | Details for tigrbl_runtime-0.4.5.dev10-py3-none-any.whl |
Total release size: 154.3 kB
Release files / tigrbl_runtime-0.4.5.dev10.tar.gz
| Download URL | tigrbl_runtime-0.4.5.dev10.tar.gz |
|---|---|
| Size | 65.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3c334536c4b1d466e91118ebb050ddeeacefebd583ba15729374e3ac50d68caf
|
|
BLAKE2b-256 checksum How to use checksums |
6d3fc17035372e729437d7814db3261ad24a359677deebce00a9b692923da8bc
|
| 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 / tigrbl_runtime-0.4.5.dev10-py3-none-any.whl
| Download URL | tigrbl_runtime-0.4.5.dev10-py3-none-any.whl |
|---|---|
| Size | 88.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a2b1dc387b2c737c43240ed853b73f4f125bc3bb398ad886b20e7adfca76bcea
|
|
BLAKE2b-256 checksum How to use checksums |
8d883b8b64af8fac90ac08eca2aadc117d02f908577baeba325c59036db04cc1
|
| 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 tigrbl-runtime 0.4.5.dev10
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.