tigrbl-concrete 0.4.0

tigrbl-concrete is a concrete implementation package for concrete implementations of Tigrbl base abstractions for reusable framework behavior.

---

Tigrbl concrete

Build concrete ASGI objects: inspect TigrblApp, routers, transports, docs, and security objects.

tigrbl-concrete is a concrete implementation package for concrete implementations of Tigrbl base abstractions for reusable framework behavior.

tigrbl-concrete is part of the Tigrbl package graph. It documents package-resident classes, concepts, extension points, and execution responsibilities while cross-linking to the facade, core specs, canonical mapping, runtime phases, concrete objects, operation packages, engine plugins, and Rust crates that complete the system.

Resident concepts

• tigrbl_concrete owns first-class native objects: concrete apps, routers, routes, tables, columns, requests, responses, middleware, security schemes, dependency wrappers, engine providers, REST transport aggregation, JSON-RPC helpers, docs builders, diagnostics, and shortcut factories.
• Hooks, deps, and secdeps are documented here when they cross into concrete routing: model/router hook binding, REST dependencies, operation-level security requirements, allow-anonymous operation exceptions, authorization dependency injection, and docs metadata emission.
• Use this package when you need the concrete objects that turn specs and canonical maps into ASGI routes, JSON-RPC methods, docs endpoints, security schemes, and execution-ready router state.

Package ecosystem cross-links

Core cross-links:

• tigrbl - Facade package
• tigrbl_core - Spec and primitive contracts
• tigrbl_canon - Canonical mapping and operation resolution
• tigrbl_runtime - Phase lifecycle and execution runtime
• tigrbl_concrete - Native objects, transports, hooks, deps, and secdeps
• tigrbl_ops_oltp - CRUD and transactional operation handlers
• tigrbl_ops_olap - Analytical operation boundary
• tigrbl_ops_realtime - Stream, transfer, datagram, and realtime ops
• tigrbl_tests - Examples, benchmark, parity, and package test surfaces Engine cross-links:
• tigrbl_engine_sqlite - SQLite local transactional engine
• tigrbl_engine_postgres - PostgreSQL SQLAlchemy engine
• tigrbl_engine_inmemory - Process-local transactional in-memory engine
• tigrbl_engine_redis - Redis cache/database engine
• tigrbl_engine_duckdb - DuckDB analytical engine
• tigrbl_engine_pandas - pandas DataFrame engine
• tigrbl_engine_pgsqli_wal - PostgreSQL and SQLite WAL engine Rust cross-links:
• tigrbl_rs_spec - Rust IR and AppSpec model
• tigrbl_rs_atoms - Rust atom catalog and phase algebra
• tigrbl_rs_kernel - Rust compiler and plan optimizer
• tigrbl_rs_runtime - Rust executor and callback fences
• tigrbl_rs_ports - Engine, session, transaction, callback, and handler ports

Install

pip install tigrbl-concrete

Package discovery

Search and AI discovery terms for tigrbl-concrete include: tigrbl, ASGI, REST, JSON-RPC, SQLAlchemy, Pydantic, asgi, api, json-rpc, rest, sqlalchemy, pydantic, concrete, implementation, framework.

Package-local entry point

This file is a package-local distribution entry point. It is not the authoritative location for repository governance, current target status, current state reporting, certification claims, or release evidence.

Canonical repository docs

• README.md
• docs/README.md
• docs/conformance/CURRENT_TARGET.md
• docs/conformance/CURRENT_STATE.md
• docs/conformance/NEXT_STEPS.md
• docs/governance/DOC_POINTERS.md
• docs/developer/PACKAGE_CATALOG.md
• docs/developer/PACKAGE_LAYOUT.md

Package identity

• canonical repository: https://github.com/tigrbl/tigrbl
• organization: https://github.com/tigrbl
• social: https://discord.gg/K4YTAPapjR
• package path: https://github.com/tigrbl/tigrbl/tree/master/pkgs/core/tigrbl_concrete
• workspace path: pkgs/core/tigrbl_concrete
• workspace class: core Python package
• implementation layout: tigrbl_concrete/

Long-form repository documentation is governed from docs/.