Skip to main content
Pre-release

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

tigrbl-concrete

Tigrbl logo

Concrete Tigrbl implementations for reusable framework behavior, sessions, routes, responses, and base abstraction adapters.

PyPI version for tigrbl-concrete Downloads for tigrbl-concrete Discord community for tigrbl-concrete Repository hits for tigrbl-concrete README Apache 2.0 license Python versions 3.10 | 3.11 | 3.12 | 3.13 | 3.14 for tigrbl-concrete Workspace group for tigrbl-concrete

What is tigrbl-concrete?

Concrete Tigrbl implementations for reusable framework behavior, sessions, routes, responses, and base abstraction adapters.

Why use tigrbl-concrete?

Use it when you need this foundational Tigrbl layer directly as a small, focused dependency.

When should I install tigrbl-concrete?

Install it for extension packages, package-local tests, or internals that need this boundary without the whole facade.

Who is tigrbl-concrete for?

Framework maintainers, extension authors, and advanced users composing Tigrbl from split packages.

Where does tigrbl-concrete fit?

tigrbl-concrete lives at pkgs/70_concrete/tigrbl_concrete and serves a focused layer in the split Tigrbl framework.

How does tigrbl-concrete work?

It owns a narrow layer in the split workspace and is consumed by higher-level packages through explicit dependencies.

Install

uv add tigrbl-concrete
pip install tigrbl-concrete

Surface Coverage

Surface Value
PyPI package tigrbl-concrete
Repository path pkgs/70_concrete/tigrbl_concrete
Python import root tigrbl_concrete
Console scripts none declared
Entry points tigrbl.engine_plugins
Optional extras none declared
Legal files LICENSE, NOTICE
Supported Python 3.10, 3.11, 3.12, 3.13, 3.14

What It Owns

tigrbl-concrete owns the foundational framework package boundary. It should be installed when you need this package's focused responsibility without assuming every other Tigrbl workspace package is present.

Implementation orientation:

  • tigrbl_concrete: _concrete/, _decorators/, _mapping/, ddl/, decorators, engine/, factories/, resolve/, security/, shortcuts/, system/, transport/

Package catalog:

  • tigrbl_concrete/_concrete/: concrete app, router, route, table, column, operation, schema, request, response, headers, body, middleware, background, storage, session, binding, engine, and security classes/adapters.
  • tigrbl_concrete/_concrete/_security/: API key, HTTP Basic, HTTP Bearer, mutual TLS, OAuth2, and OpenID Connect security primitives.
  • tigrbl_concrete/_decorators/ and tigrbl_concrete/decorators.py: concrete decorator implementations that attach engine, hook, op, response, schema, session, middleware, allow-anon, and related metadata.
  • tigrbl_concrete/_mapping/: app, router, model, column, operation, core, and app-spec lowering helpers that turn specs and model metadata into concrete registrations.
  • tigrbl_concrete/engine/: engine builders, binding, capability declarations, plugin discovery, registry, resolver, and collection helpers.
  • tigrbl_concrete/factories/ and tigrbl_concrete/shortcuts/: concrete app and REST shortcut helpers consumed by the facade.
  • tigrbl_concrete/resolve/: handler resolution helpers.
  • tigrbl_concrete/security/: concrete security dependency helpers.
  • tigrbl_concrete/system/diagnostics: /system/healthz, /system/hookz, /system/kernelz, /system/methodz, and diagnostic router helpers.
  • tigrbl_concrete/system/docs: OpenAPI, OpenRPC, JSON Schema, Swagger, lens, runtime-ops, and surface documentation helpers.
  • tigrbl_concrete/transport/rest and tigrbl_concrete/transport/jsonrpc: REST route aggregation and JSON-RPC helper/model utilities.
  • tigrbl_concrete/ddl/ and tigrbl_concrete/system/static/favicon: DDL and static/docs support surfaces.

Public API and Import Surface

Concrete Implementation Semantics

tigrbl-concrete is where abstract specs and base contracts become usable Python framework objects. It is intentionally below the tigrbl facade and above the atom/kernel/runtime internals. Application developers normally import through tigrbl; extension authors import this package when they need concrete classes, decorators, engine resolution, docs mounting, or diagnostics without taking the facade dependency.

The package performs four broad jobs:

  • Lower core specs and base contracts into concrete app/router/table/operation objects.
  • Register REST and JSON-RPC projections for model operations.
  • Resolve engines, handlers, schemas, responses, security dependencies, middleware, and docs surfaces.
  • Expose operational introspection through system routes.

REST and JSON-RPC Surfaces

Concrete routing keeps REST and JSON-RPC projections tied to the same operation inventory:

Surface Concrete responsibility
REST Aggregate route metadata, attach handlers, apply path/method mapping, shape request/response objects, and expose OpenAPI-compatible docs.
JSON-RPC Resolve method names, validate JSON-RPC request/response models, dispatch through the same operation handlers, and expose OpenRPC-compatible docs.
Docs Publish OpenAPI, OpenRPC, JSON Schema, Swagger, runtime operation views, and surface/lens outputs from the same concrete registration data.
Diagnostics Expose healthz, hookz, kernelz, and methodz so users can inspect runtime health, hook order, kernel plans, and method inventory.

Avoid adding one-off framework routes for model behavior when an operation spec can represent the behavior. Ops keep REST, JSON-RPC, docs, hooks, and diagnostics unified.

Engine and Provider Behavior

The engine subpackage owns concrete engine resolution and plugin discovery. It can build and bind engines from specs, providers, mappings, or decorator metadata, then expose capability information for runtime and tests.

Resolution follows the framework's specificity rule:

operation > table/model > router > app > defaults

Best practices:

  • Declare engine intent through specs or decorators instead of constructing SQLAlchemy engines inside handlers.
  • Keep engine plugins explicit and capability-aware.
  • Test resolver behavior when adding a new engine package or new engine context shape.
  • Preserve separation between engine resolution and transaction lifecycle; atoms/runtime own transaction phase progression.

System and Operational Endpoints

Concrete apps can mount system endpoints:

  • /system/healthz for basic process health.
  • /system/hookz for model/operation/phase hook order.
  • /system/kernelz for compiled kernel phase plans.
  • /system/methodz for exposed method inventory.
  • docs endpoints for OpenAPI, OpenRPC, JSON Schema, Swagger, and runtime operation surfaces.

These endpoints are operational tools. They should reflect registered framework state and compiled plans; do not hard-code documentation that can drift away from actual registrations.

Security and Middleware

Security primitives include API key, HTTP Basic, HTTP Bearer, mutual TLS, OAuth2, and OpenID Connect helpers. Use them as dependencies or framework-level security specs so security behavior participates in lifecycle ordering and diagnostics. Middleware should be declared through concrete middleware helpers or specs rather than wrapping generated routes in ways the kernel cannot see.

Extension Guidance

  • Use concrete decorators and factories when building public conveniences for the facade.
  • Keep compatibility imports in tigrbl thin; implement reusable behavior here or in lower packages.
  • Do not bypass kernel/runtime plans when wiring REST or JSON-RPC handlers.
  • Keep docs, diagnostics, and transport helpers generated from actual registration state.
  • Treat _concrete classes as framework implementation surfaces; public application documentation should continue to prefer facade imports.

Authoring BCP for this boundary:

  • Do use tigrbl-concrete to lower specs and base contracts into concrete app, router, table, operation, schema, request, response, engine, security, docs, diagnostics, and transport implementations.
  • Do keep REST and JSON-RPC projections tied to the same operation inventory and handler resolution path.
  • Do keep framework-internal ASGI, Starlette-compatible, SQLAlchemy, and engine mechanics behind concrete Tigrbl adapters.
  • Do not teach application users to bypass the tigrbl facade and import _concrete classes for normal service code.
  • Do not wire one-off handlers around kernel/runtime plans, diagnostics, generated docs, or operation specs.
  • Avoid hard-coded documentation and diagnostics that can drift away from actual registrations.

Usage Examples

Verify the installed package

python -m pip show tigrbl-concrete
python - <<'PY'
from importlib.metadata import version
print(version("tigrbl-concrete"))
PY

Import the package boundary

import importlib

module = importlib.import_module("tigrbl_concrete")
print(module.__name__)

Inspect available modules

import importlib
import pkgutil

module = importlib.import_module("tigrbl_concrete")
for info in pkgutil.iter_modules(getattr(module, "__path__", [])):
    print(info.name)

Use with the facade when building applications

uv add tigrbl tigrbl-concrete
python - <<'PY'
import tigrbl
print(tigrbl.__name__)
PY

How To Choose This Package

Choose tigrbl-concrete 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.

Support

Package-local Boundary

This file is a package-local distribution entry point. This README is the package-local distribution entry point for tigrbl-concrete. 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/97_tests/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.

Metadata

Release files for tigrbl-concrete 0.4.5.dev6

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

Source distribution (sdist)

Source distribution for tigrbl-concrete 0.4.5.dev6
File Size Uploaded Provenance Actions
tigrbl_concrete-0.4.5.dev6.tar.gz 145.5 kB Without provenance Details for tigrbl_concrete-0.4.5.dev6.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for tigrbl-concrete 0.4.5.dev6
File Interpreter ABI Platform Actions
tigrbl_concrete-0.4.5.dev6-py3-none-any.whl Python 3 none any Details for tigrbl_concrete-0.4.5.dev6-py3-none-any.whl

Total release size: 346.3 kB

Release files / tigrbl_concrete-0.4.5.dev6.tar.gz

Download URL tigrbl_concrete-0.4.5.dev6.tar.gz
Size 145.5 kB
Tags Source
SHA-256 checksum
How to use checksums
c4684196ffb12380a3a18d81ddd587d06fbcede75b99ef8b00c0f69432ebb9c2
BLAKE2b-256 checksum
How to use checksums
d571559dbe8381de6c940153022b9cbd16c7653cf958da78d5aec000c09571a6
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_concrete-0.4.5.dev6-py3-none-any.whl

Download URL tigrbl_concrete-0.4.5.dev6-py3-none-any.whl
Size 200.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bbcd1bac061159d45404e5ff65447933e951e75eb8e397f8d405ecd664b23352
BLAKE2b-256 checksum
How to use checksums
7c6fdf060d43fa8f64da092c4571fbc2af35ee74025a341091d0475013d84514
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-concrete 0.4.5.dev6

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.

Release history Release notifications | RSS feed

This release
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