tigrbl-runtime 0.4.5.dev4

Execution bridge for compiled Tigrbl kernel plans and narrow runtime context/carrier compatibility.

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/core/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/core/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

• tigrbl-typing
• tigrbl-kernel
• tigrbl-atoms
• tigrbl-base
• tigrbl-core
• tigrbl

Documentation Links

• Workspace docs
• Package catalog
• Package layout
• Current target
• Current state
• SSOT registry
• Release workflow

Support

• Community: Discord.
• Issues: GitHub Issues.
• Repository: pkgs/core/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/tigrbl workspace.
• 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/core/tigrbl_tests/tests/unit/test_package_badges_and_notices.py verifies every package README keeps the Discord badge, Apache 2.0 badge, explicit Python-version badge, LICENSE, and NOTICE.
• 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.