tigrbl-base 0.4.2.dev3__tar.gz → 0.4.3.dev4__tar.gz

tigrbl_base-0.4.3.dev4/NOTICE

@@ -0,0 +1,7 @@
+Tigrbl
+Copyright 2026 Swarmauri
+
+This product includes software developed by Swarmauri.
+
+Tigrbl is licensed under the Apache License, Version 2.0.
+See the LICENSE file distributed with this work for the full license text.

{tigrbl_base-0.4.2.dev3 → tigrbl_base-0.4.3.dev4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tigrbl-base
-Version: 0.4.2.dev3
+Version: 0.4.3.dev4
 Summary: Base contract package for Tigrbl apps, routers, tables, sessions, middleware, requests, responses, bindings, and engine interfaces.
 License: Apache License
                                     Version 2.0, January 2004
@@ -204,6 +204,7 @@ License: Apache License
             See the License for the specific language governing permissions and
             limitations under the License.
 License-File: LICENSE
+License-File: NOTICE
 Keywords: tigrbl,asgi,api,abstract base classes,api contracts,base contracts,engine interfaces,framework internals,json-rpc,base,base-classes,interfaces,abstractions,openapi,openrpc,request response,rest,schema-first,session interfaces,sqlalchemy,table base
 Author: Jacob Stewart
 Author-email: jacob@swarmauri.com
@@ -246,12 +247,45 @@ Description-Content-Type: text/markdown
 <p><strong>Base contract package for Tigrbl apps, routers, tables, sessions, middleware, requests, responses, bindings, and engine interfaces.</strong></p>
 <a href="https://pypi.org/project/tigrbl-base/"><img src="https://img.shields.io/pypi/v/tigrbl-base?label=PyPI" alt="PyPI version for tigrbl-base"/></a>
 <a href="https://pypi.org/project/tigrbl-base/"><img src="https://static.pepy.tech/badge/tigrbl-base" alt="Downloads for tigrbl-base"/></a>
+<a href="https://discord.gg/K4YTAPapjR"><img src="https://img.shields.io/badge/Discord-Join%20chat-5865F2?logo=discord&logoColor=white" alt="Discord community for tigrbl-base"/></a>
 <a href="https://github.com/tigrbl/tigrbl/blob/master/pkgs/core/tigrbl_base/README.md"><img src="https://hits.sh/github.com/tigrbl/tigrbl/blob/master/pkgs/core/tigrbl_base/README.md.svg?label=hits" alt="Repository hits for tigrbl-base README"/></a>
 <a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache%202.0-525252" alt="Apache 2.0 license"/></a>
-<a href="pyproject.toml"><img src="https://img.shields.io/badge/python-3.10%20to%203.15-3776ab" alt="Python requirement for tigrbl-base"/></a>
+<a href="pyproject.toml"><img src="https://img.shields.io/badge/python-3.10%2C%203.11%2C%203.12%2C%203.13%2C%203.14-3776ab" alt="Python versions 3.10 | 3.11 | 3.12 | 3.13 | 3.14 for tigrbl-base"/></a>
 <a href="https://github.com/tigrbl/tigrbl/blob/master/docs/README.md"><img src="https://img.shields.io/badge/workspace-core-1f6feb" alt="Workspace group for tigrbl-base"/></a>
 </div>
 
+## What is tigrbl-base?
+
+Base contract package for Tigrbl apps, routers, tables, sessions, middleware, requests, responses, bindings, and engine interfaces.
+
+## Why use tigrbl-base?
+
+Use it when you need this foundational Tigrbl layer directly as a small, focused dependency.
+
+## When should I install tigrbl-base?
+
+Install it for extension packages, package-local tests, or internals that need this boundary without the whole facade.
+
+## Who is tigrbl-base for?
+
+Framework maintainers, extension authors, and advanced users composing Tigrbl from split packages.
+
+## Where does tigrbl-base fit?
+
+`tigrbl-base` lives at `pkgs/core/tigrbl_base` and serves a focused layer in the split Tigrbl framework.
+
+## How does tigrbl-base work?
+
+It owns a narrow layer in the split workspace and is consumed by higher-level packages through explicit dependencies.
+
+## Certification Status
+
+- Package status: governed package in the `tigrbl/tigrbl` workspace.
+- Governance source: [SSOT registry](https://github.com/tigrbl/tigrbl/blob/master/.ssot/registry.json).
+- Release evidence: [publish workflow](https://github.com/tigrbl/tigrbl/actions/workflows/publish.yml) 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.
+
 ## Install
 
 ```bash
@@ -262,52 +296,167 @@ uv add tigrbl-base
 pip install tigrbl-base
 ```
 
+## Surface Coverage
+
+| Surface | Value |
+|---|---|
+| PyPI package | [`tigrbl-base`](https://pypi.org/project/tigrbl-base/) |
+| Repository path | [`pkgs/core/tigrbl_base`](https://github.com/tigrbl/tigrbl/tree/master/pkgs/core/tigrbl_base) |
+| Python import root | `tigrbl_base` |
+| Console scripts | none declared |
+| Entry points | none declared |
+| Optional extras | none declared |
+| Legal files | `LICENSE`, `NOTICE` |
+| Supported Python | `3.10, 3.11, 3.12, 3.13, 3.14` |
+
 ## What It Owns
 
-`tigrbl-base` owns the base boundary inside the split Python workspace.
+`tigrbl-base` 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.
 
-## Use It When
+Implementation orientation:
+- `tigrbl_base`: _base/, column/
 
-Use `tigrbl-base` when you want this subsystem directly as a package boundary instead of consuming it only through the top-level `tigrbl` facade.
+Package catalog:
+- `_base/_app_base.py`, `_router_base.py`, and `_table_base.py`: abstract app, router, and table behavior used by concrete framework classes.
+- `_base/_op_base.py`, `_binding_base.py`, `_rest_map.py`, and `_rpc_map.py`: operation, binding, REST mapping, and JSON-RPC mapping contracts.
+- `_base/_schema_base.py`, `_request_base.py`, `_response_base.py`, `_headers_base.py`, and `_middleware_base.py`: request/response/schema/header/middleware abstractions.
+- `_base/_engine_base.py`, `_engine_provider_base.py`, `_session_abc.py`, `_session_base.py`, and `_storage.py`: engine, provider, session, and storage interfaces.
+- `_base/_column_base.py`, `_table_registry_base.py`, `_alias_base.py`, `_hook_base.py`, `_security_base.py`, and `_datatype_lowering.py`: table metadata, aliasing, hook/security contracts, and data-type lowering hooks.
+- `_base/_assembly.py` and `_mapping_access.py`: assembly and mapping helpers for concrete implementations.
+- `column/infer`: column inference planning, JSON hint handling, type interpretation, and utility helpers.
 
-## Public Surface
+## Public API and Import Surface
 
-- Package-local implementation lives under `pkgs/core/tigrbl_base` and is consumed as a distribution boundary rather than a single broad root re-export.
+- Import roots: `tigrbl_base`.
+- Public symbols: public surface is module-oriented; import the package boundary and inspect submodules as needed.
+- Workspace dependencies: [`tigrbl-core`](https://pypi.org/project/tigrbl-core/), [`tigrbl-atoms`](https://pypi.org/project/tigrbl-atoms/).
+- External runtime dependencies: `sqlalchemy>=2.0`, `pydantic>=2.0`.
 
-## Internal Layout
+## Abstraction Semantics
 
-- Workspace path: `pkgs/core/tigrbl_base`.
-- Package class: `core framework package`.
-- Python requirement: `>=3.10,<3.15`.
+`tigrbl-base` is the abstract contract layer between core specs and concrete implementations. It is useful when you need interface behavior without importing the facade or concrete ASGI/application classes.
 
-## Dependency Surface
+The package answers questions such as:
 
-- Workspace package dependencies: [`tigrbl-core`](https://pypi.org/project/tigrbl-core/), [`tigrbl-atoms`](https://pypi.org/project/tigrbl-atoms/).
-- External runtime dependencies: `sqlalchemy>=2.0`, `pydantic>=2.0`.
-- Optional extras: none declared.
+- What must an app/router/table expose for assembly?
+- How do REST and JSON-RPC maps represent operation bindings?
+- What does a request, response, middleware, hook, session, engine provider, or storage adapter need to provide?
+- How should column metadata be inferred before a concrete table class lowers it into ORM/schema/runtime behavior?
+
+It should not own route registration side effects, transport IO, database engine construction, or runtime execution. Those belong in `tigrbl-concrete`, engine packages, kernel/runtime packages, or the facade.
+
+## Base Contracts by Area
+
+| Area | Base responsibility |
+|---|---|
+| App/router/table | Provide shared assembly, inclusion, registration, and metadata contracts. |
+| Operations and bindings | Represent operation maps, REST maps, RPC maps, alias behavior, and binding access. |
+| Schema and IO | Provide base shape for request/response/schema objects without deciding concrete rendering. |
+| Engine/session/storage | Define provider/session/storage contracts so concrete engines can plug in consistently. |
+| Hooks/security/middleware | Provide registration and interface surfaces for lifecycle customization and request policy. |
+| Columns | Infer and lower type information while keeping spec-level intent separate from concrete ORM wiring. |
+
+## Column Inference
+
+`tigrbl_base.column.infer` supports the framework's schema-first and table-first workflows. It helps interpret Python typing, JSON hints, planning metadata, and column options before concrete packages lower them into SQLAlchemy/Pydantic/runtime representations.
+
+Best practices for column inference:
+- Keep inference deterministic; the same type hints and config should produce the same plan.
+- Keep storage intent separate from wire-schema intent.
+- Preserve explicit user configuration over inferred defaults.
+- Add tests for ambiguous type handling instead of silently guessing.
+
+## Extension Guidance
+
+- Depend on `tigrbl-base` when you are writing concrete adapters, engine adapters, or framework tests that need abstract contracts.
+- Do not import `tigrbl` facade classes here; base should remain lower than the public facade.
+- Keep methods small and contract-oriented. Put operational side effects in concrete implementations or atoms.
+- Treat base classes as compatibility surfaces. Renaming or tightening a method affects all concrete packages.
+- Prefer composition with `tigrbl-core` specs rather than duplicating spec fields in base classes.
+
+Authoring BCP for this boundary:
+- Do use `tigrbl-base` for abstract app/router/table/session/request/response/binding/security/middleware/storage contracts and column inference behavior.
+- Do keep column inference deterministic and spec-driven before concrete packages lower intent into ORM, schema, runtime, or docs behavior.
+- Do not make `tigrbl-base` the public application import path for normal service code.
+- Do not put route registration side effects, direct database transaction calls, concrete engine construction, FastAPI/Starlette route objects, or runtime execution into this package.
+- Avoid treating SQLAlchemy materialization as the source of truth here. Base may prepare and validate metadata, but reusable field behavior should remain represented by Tigrbl specs.
+
+## Usage Examples
+
+### Verify the installed package
+
+```bash
+python -m pip show tigrbl-base
+python - <<'PY'
+from importlib.metadata import version
+print(version("tigrbl-base"))
+PY
+```
+
+### Import the package boundary
+
+```python
+import importlib
+
+module = importlib.import_module("tigrbl_base._base")
+print(module.__name__)
+```
+
+### Inspect available modules
+
+```python
+import importlib
+import pkgutil
+
+module = importlib.import_module("tigrbl_base._base")
+for info in pkgutil.iter_modules(getattr(module, "__path__", [])):
+    print(info.name)
+```
+
+### Use with the facade when building applications
+
+```bash
+uv add tigrbl tigrbl-base
+python - <<'PY'
+import tigrbl
+print(tigrbl.__name__)
+PY
+```
+
+## How To Choose This Package
+
+Choose `tigrbl-base` when the quick-answer table matches your use case. Choose [`tigrbl`](https://pypi.org/project/tigrbl/) instead when you want the full public facade. Choose a lower-level package such as [`tigrbl-core`](https://pypi.org/project/tigrbl-core/), [`tigrbl-base`](https://pypi.org/project/tigrbl-base/), or [`tigrbl-runtime`](https://pypi.org/project/tigrbl-runtime/) when you are building framework extensions or testing a specific internal boundary.
 
 ## Related Packages
 
-- [`tigrbl`](https://pypi.org/project/tigrbl/)
 - [`tigrbl-core`](https://pypi.org/project/tigrbl-core/)
 - [`tigrbl-atoms`](https://pypi.org/project/tigrbl-atoms/)
+- [`tigrbl`](https://pypi.org/project/tigrbl/)
+- [`tigrbl-runtime`](https://pypi.org/project/tigrbl-runtime/)
+
+## Documentation Links
+
+- [Workspace docs](https://github.com/tigrbl/tigrbl/blob/master/docs/README.md)
+- [Package catalog](https://github.com/tigrbl/tigrbl/blob/master/docs/developer/PACKAGE_CATALOG.md)
+- [Package layout](https://github.com/tigrbl/tigrbl/blob/master/docs/developer/PACKAGE_LAYOUT.md)
+- [Current target](https://github.com/tigrbl/tigrbl/blob/master/docs/conformance/CURRENT_TARGET.md)
+- [Current state](https://github.com/tigrbl/tigrbl/blob/master/docs/conformance/CURRENT_STATE.md)
+- [Next steps](https://github.com/tigrbl/tigrbl/blob/master/docs/conformance/NEXT_STEPS.md)
+- [Documentation pointers](https://github.com/tigrbl/tigrbl/blob/master/docs/governance/DOC_POINTERS.md)
+- [SSOT registry](https://github.com/tigrbl/tigrbl/blob/master/.ssot/registry.json)
+- [Release workflow](https://github.com/tigrbl/tigrbl/actions/workflows/publish.yml)
 
-## Canonical Repository Docs
+## Support
 
-- `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`
+- Community: [Discord](https://discord.gg/K4YTAPapjR).
+- Issues: [GitHub Issues](https://github.com/tigrbl/tigrbl/issues).
+- Repository: [pkgs/core/tigrbl_base](https://github.com/tigrbl/tigrbl/tree/master/pkgs/core/tigrbl_base).
 
 ## Package-local Boundary
 
-This file is a package-local distribution entry point.
-Use this page for package installation and boundary orientation. Repository governance, conformance state, target status, and release evidence remain governed from `docs/` and `.ssot/`.
+This file is a package-local distribution entry point. This README is the package-local distribution entry point for `tigrbl-base`. 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.
 
 ## License
 
-Licensed under the Apache License, Version 2.0. See `LICENSE` and the official [Apache 2.0 license text](https://www.apache.org/licenses/LICENSE-2.0).
+Licensed under the Apache License, Version 2.0. See `LICENSE`, `NOTICE`, and the official [Apache 2.0 license text](https://www.apache.org/licenses/LICENSE-2.0).
 

tigrbl_base-0.4.3.dev4/README.md

@@ -0,0 +1,218 @@
+<div align="center">
+<h1>tigrbl-base</h1>
+<img src="https://raw.githubusercontent.com/swarmauri/swarmauri-sdk/master/assets/tigrbl_full_logo.png" alt="Tigrbl logo" width="140"/>
+<p><strong>Base contract package for Tigrbl apps, routers, tables, sessions, middleware, requests, responses, bindings, and engine interfaces.</strong></p>
+<a href="https://pypi.org/project/tigrbl-base/"><img src="https://img.shields.io/pypi/v/tigrbl-base?label=PyPI" alt="PyPI version for tigrbl-base"/></a>
+<a href="https://pypi.org/project/tigrbl-base/"><img src="https://static.pepy.tech/badge/tigrbl-base" alt="Downloads for tigrbl-base"/></a>
+<a href="https://discord.gg/K4YTAPapjR"><img src="https://img.shields.io/badge/Discord-Join%20chat-5865F2?logo=discord&logoColor=white" alt="Discord community for tigrbl-base"/></a>
+<a href="https://github.com/tigrbl/tigrbl/blob/master/pkgs/core/tigrbl_base/README.md"><img src="https://hits.sh/github.com/tigrbl/tigrbl/blob/master/pkgs/core/tigrbl_base/README.md.svg?label=hits" alt="Repository hits for tigrbl-base README"/></a>
+<a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache%202.0-525252" alt="Apache 2.0 license"/></a>
+<a href="pyproject.toml"><img src="https://img.shields.io/badge/python-3.10%2C%203.11%2C%203.12%2C%203.13%2C%203.14-3776ab" alt="Python versions 3.10 | 3.11 | 3.12 | 3.13 | 3.14 for tigrbl-base"/></a>
+<a href="https://github.com/tigrbl/tigrbl/blob/master/docs/README.md"><img src="https://img.shields.io/badge/workspace-core-1f6feb" alt="Workspace group for tigrbl-base"/></a>
+</div>
+
+## What is tigrbl-base?
+
+Base contract package for Tigrbl apps, routers, tables, sessions, middleware, requests, responses, bindings, and engine interfaces.
+
+## Why use tigrbl-base?
+
+Use it when you need this foundational Tigrbl layer directly as a small, focused dependency.
+
+## When should I install tigrbl-base?
+
+Install it for extension packages, package-local tests, or internals that need this boundary without the whole facade.
+
+## Who is tigrbl-base for?
+
+Framework maintainers, extension authors, and advanced users composing Tigrbl from split packages.
+
+## Where does tigrbl-base fit?
+
+`tigrbl-base` lives at `pkgs/core/tigrbl_base` and serves a focused layer in the split Tigrbl framework.
+
+## How does tigrbl-base work?
+
+It owns a narrow layer in the split workspace and is consumed by higher-level packages through explicit dependencies.
+
+## Certification Status
+
+- Package status: governed package in the `tigrbl/tigrbl` workspace.
+- Governance source: [SSOT registry](https://github.com/tigrbl/tigrbl/blob/master/.ssot/registry.json).
+- Release evidence: [publish workflow](https://github.com/tigrbl/tigrbl/actions/workflows/publish.yml) 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.
+
+## Install
+
+```bash
+uv add tigrbl-base
+```
+
+```bash
+pip install tigrbl-base
+```
+
+## Surface Coverage
+
+| Surface | Value |
+|---|---|
+| PyPI package | [`tigrbl-base`](https://pypi.org/project/tigrbl-base/) |
+| Repository path | [`pkgs/core/tigrbl_base`](https://github.com/tigrbl/tigrbl/tree/master/pkgs/core/tigrbl_base) |
+| Python import root | `tigrbl_base` |
+| Console scripts | none declared |
+| Entry points | none declared |
+| Optional extras | none declared |
+| Legal files | `LICENSE`, `NOTICE` |
+| Supported Python | `3.10, 3.11, 3.12, 3.13, 3.14` |
+
+## What It Owns
+
+`tigrbl-base` 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_base`: _base/, column/
+
+Package catalog:
+- `_base/_app_base.py`, `_router_base.py`, and `_table_base.py`: abstract app, router, and table behavior used by concrete framework classes.
+- `_base/_op_base.py`, `_binding_base.py`, `_rest_map.py`, and `_rpc_map.py`: operation, binding, REST mapping, and JSON-RPC mapping contracts.
+- `_base/_schema_base.py`, `_request_base.py`, `_response_base.py`, `_headers_base.py`, and `_middleware_base.py`: request/response/schema/header/middleware abstractions.
+- `_base/_engine_base.py`, `_engine_provider_base.py`, `_session_abc.py`, `_session_base.py`, and `_storage.py`: engine, provider, session, and storage interfaces.
+- `_base/_column_base.py`, `_table_registry_base.py`, `_alias_base.py`, `_hook_base.py`, `_security_base.py`, and `_datatype_lowering.py`: table metadata, aliasing, hook/security contracts, and data-type lowering hooks.
+- `_base/_assembly.py` and `_mapping_access.py`: assembly and mapping helpers for concrete implementations.
+- `column/infer`: column inference planning, JSON hint handling, type interpretation, and utility helpers.
+
+## Public API and Import Surface
+
+- Import roots: `tigrbl_base`.
+- Public symbols: public surface is module-oriented; import the package boundary and inspect submodules as needed.
+- Workspace dependencies: [`tigrbl-core`](https://pypi.org/project/tigrbl-core/), [`tigrbl-atoms`](https://pypi.org/project/tigrbl-atoms/).
+- External runtime dependencies: `sqlalchemy>=2.0`, `pydantic>=2.0`.
+
+## Abstraction Semantics
+
+`tigrbl-base` is the abstract contract layer between core specs and concrete implementations. It is useful when you need interface behavior without importing the facade or concrete ASGI/application classes.
+
+The package answers questions such as:
+
+- What must an app/router/table expose for assembly?
+- How do REST and JSON-RPC maps represent operation bindings?
+- What does a request, response, middleware, hook, session, engine provider, or storage adapter need to provide?
+- How should column metadata be inferred before a concrete table class lowers it into ORM/schema/runtime behavior?
+
+It should not own route registration side effects, transport IO, database engine construction, or runtime execution. Those belong in `tigrbl-concrete`, engine packages, kernel/runtime packages, or the facade.
+
+## Base Contracts by Area
+
+| Area | Base responsibility |
+|---|---|
+| App/router/table | Provide shared assembly, inclusion, registration, and metadata contracts. |
+| Operations and bindings | Represent operation maps, REST maps, RPC maps, alias behavior, and binding access. |
+| Schema and IO | Provide base shape for request/response/schema objects without deciding concrete rendering. |
+| Engine/session/storage | Define provider/session/storage contracts so concrete engines can plug in consistently. |
+| Hooks/security/middleware | Provide registration and interface surfaces for lifecycle customization and request policy. |
+| Columns | Infer and lower type information while keeping spec-level intent separate from concrete ORM wiring. |
+
+## Column Inference
+
+`tigrbl_base.column.infer` supports the framework's schema-first and table-first workflows. It helps interpret Python typing, JSON hints, planning metadata, and column options before concrete packages lower them into SQLAlchemy/Pydantic/runtime representations.
+
+Best practices for column inference:
+- Keep inference deterministic; the same type hints and config should produce the same plan.
+- Keep storage intent separate from wire-schema intent.
+- Preserve explicit user configuration over inferred defaults.
+- Add tests for ambiguous type handling instead of silently guessing.
+
+## Extension Guidance
+
+- Depend on `tigrbl-base` when you are writing concrete adapters, engine adapters, or framework tests that need abstract contracts.
+- Do not import `tigrbl` facade classes here; base should remain lower than the public facade.
+- Keep methods small and contract-oriented. Put operational side effects in concrete implementations or atoms.
+- Treat base classes as compatibility surfaces. Renaming or tightening a method affects all concrete packages.
+- Prefer composition with `tigrbl-core` specs rather than duplicating spec fields in base classes.
+
+Authoring BCP for this boundary:
+- Do use `tigrbl-base` for abstract app/router/table/session/request/response/binding/security/middleware/storage contracts and column inference behavior.
+- Do keep column inference deterministic and spec-driven before concrete packages lower intent into ORM, schema, runtime, or docs behavior.
+- Do not make `tigrbl-base` the public application import path for normal service code.
+- Do not put route registration side effects, direct database transaction calls, concrete engine construction, FastAPI/Starlette route objects, or runtime execution into this package.
+- Avoid treating SQLAlchemy materialization as the source of truth here. Base may prepare and validate metadata, but reusable field behavior should remain represented by Tigrbl specs.
+
+## Usage Examples
+
+### Verify the installed package
+
+```bash
+python -m pip show tigrbl-base
+python - <<'PY'
+from importlib.metadata import version
+print(version("tigrbl-base"))
+PY
+```
+
+### Import the package boundary
+
+```python
+import importlib
+
+module = importlib.import_module("tigrbl_base._base")
+print(module.__name__)
+```
+
+### Inspect available modules
+
+```python
+import importlib
+import pkgutil
+
+module = importlib.import_module("tigrbl_base._base")
+for info in pkgutil.iter_modules(getattr(module, "__path__", [])):
+    print(info.name)
+```
+
+### Use with the facade when building applications
+
+```bash
+uv add tigrbl tigrbl-base
+python - <<'PY'
+import tigrbl
+print(tigrbl.__name__)
+PY
+```
+
+## How To Choose This Package
+
+Choose `tigrbl-base` when the quick-answer table matches your use case. Choose [`tigrbl`](https://pypi.org/project/tigrbl/) instead when you want the full public facade. Choose a lower-level package such as [`tigrbl-core`](https://pypi.org/project/tigrbl-core/), [`tigrbl-base`](https://pypi.org/project/tigrbl-base/), or [`tigrbl-runtime`](https://pypi.org/project/tigrbl-runtime/) when you are building framework extensions or testing a specific internal boundary.
+
+## Related Packages
+
+- [`tigrbl-core`](https://pypi.org/project/tigrbl-core/)
+- [`tigrbl-atoms`](https://pypi.org/project/tigrbl-atoms/)
+- [`tigrbl`](https://pypi.org/project/tigrbl/)
+- [`tigrbl-runtime`](https://pypi.org/project/tigrbl-runtime/)
+
+## Documentation Links
+
+- [Workspace docs](https://github.com/tigrbl/tigrbl/blob/master/docs/README.md)
+- [Package catalog](https://github.com/tigrbl/tigrbl/blob/master/docs/developer/PACKAGE_CATALOG.md)
+- [Package layout](https://github.com/tigrbl/tigrbl/blob/master/docs/developer/PACKAGE_LAYOUT.md)
+- [Current target](https://github.com/tigrbl/tigrbl/blob/master/docs/conformance/CURRENT_TARGET.md)
+- [Current state](https://github.com/tigrbl/tigrbl/blob/master/docs/conformance/CURRENT_STATE.md)
+- [Next steps](https://github.com/tigrbl/tigrbl/blob/master/docs/conformance/NEXT_STEPS.md)
+- [Documentation pointers](https://github.com/tigrbl/tigrbl/blob/master/docs/governance/DOC_POINTERS.md)
+- [SSOT registry](https://github.com/tigrbl/tigrbl/blob/master/.ssot/registry.json)
+- [Release workflow](https://github.com/tigrbl/tigrbl/actions/workflows/publish.yml)
+
+## Support
+
+- Community: [Discord](https://discord.gg/K4YTAPapjR).
+- Issues: [GitHub Issues](https://github.com/tigrbl/tigrbl/issues).
+- Repository: [pkgs/core/tigrbl_base](https://github.com/tigrbl/tigrbl/tree/master/pkgs/core/tigrbl_base).
+
+## Package-local Boundary
+
+This file is a package-local distribution entry point. This README is the package-local distribution entry point for `tigrbl-base`. 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.
+
+## License
+
+Licensed under the Apache License, Version 2.0. See `LICENSE`, `NOTICE`, and the official [Apache 2.0 license text](https://www.apache.org/licenses/LICENSE-2.0).

{tigrbl_base-0.4.2.dev3 → tigrbl_base-0.4.3.dev4}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "tigrbl-base"
-version = "0.4.2.dev3"
+version = "0.4.3.dev4"
 description = "Base contract package for Tigrbl apps, routers, tables, sessions, middleware, requests, responses, bindings, and engine interfaces."
 readme = "README.md"
 license = { file = "LICENSE" }

{tigrbl_base-0.4.2.dev3 → tigrbl_base-0.4.3.dev4}/tigrbl_base/_base/__init__.py

@@ -22,6 +22,8 @@ _EXPORTS = {
     "SchemaBase": "_schema_base",
     "SessionABC": "_session_abc",
     "TigrblSessionBase": "_session_base",
+    "CrudTableBase": "_table_base",
+    "RealtimeTableBase": "_table_base",
     "TableBase": "_table_base",
     "TableRegistryBase": "_table_registry_base",
     "AttrDict": "_mapping_access",
@@ -29,6 +31,9 @@ _EXPORTS = {
 
 __all__ = list(_EXPORTS)
 
+for _symbol in __all__:
+    globals().pop(_symbol, None)
+
 
 def __getattr__(name: str) -> Any:
     module_name = _EXPORTS.get(name)

{tigrbl_base-0.4.2.dev3 → tigrbl_base-0.4.3.dev4}/tigrbl_base/_base/_app_base.py

@@ -5,7 +5,7 @@ import inspect
 from typing import Any
 from typing import Callable, Optional, Sequence
 
-from tigrbl_core._spec.app_spec import AppSpec
+from tigrbl_core._spec.app_spec import AppSpec, normalize_execution_backend
 from tigrbl_core._spec.engine_spec import EngineCfg
 from tigrbl_core._spec.response_spec import ResponseSpec
 
@@ -100,7 +100,7 @@ class AppBase(AppSpec):
             title=spec.title,
             description=spec.description,
             version=spec.version,
-            execution_backend=spec.execution_backend,
+            execution_backend=normalize_execution_backend(spec.execution_backend),
             engine=spec.engine,
             routers=routers,
             ops=tuple(spec.ops or ()),
@@ -133,7 +133,7 @@ class AppBase(AppSpec):
             title=str(spec.title or "Tigrbl"),
             description=spec.description,
             version=str(spec.version or "0.1.0"),
-            execution_backend=str(spec.execution_backend or "auto"),
+            execution_backend=normalize_execution_backend(spec.execution_backend),
             engine=spec.engine,
             routers=cls._bind_mapped_children(spec.routers, parent=parent),
             ops=cls._bind_mapped_children(spec.ops, parent=parent),

{tigrbl_base-0.4.2.dev3 → tigrbl_base-0.4.3.dev4}/tigrbl_base/_base/_mapping_access.py

@@ -15,5 +15,11 @@ class AttrDict(dict):
     def __setattr__(self, key: str, value: Any) -> None:  # pragma: no cover - trivial
         self[key] = value
 
+    def __delattr__(self, item: str) -> None:
+        try:
+            del self[item]
+        except KeyError as exc:
+            raise AttributeError(item) from exc
+
 
 __all__ = ["AttrDict"]

{tigrbl_base-0.4.2.dev3 → tigrbl_base-0.4.3.dev4}/tigrbl_base/_base/_table_base.py

@@ -11,6 +11,13 @@ from sqlalchemy import CheckConstraint, ForeignKey, MetaData
 from sqlalchemy.types import Enum as SAEnum, String
 
 from ._datatype_lowering import lower_datatype_to_sqla_type
+from tigrbl_core._spec.table_profile_spec import (
+    CRUD_TABLE_PROFILE,
+    PLAIN_TABLE_PROFILE,
+    REALTIME_TABLE_PROFILE,
+    TableProfileError,
+    coerce_table_profile,
+)
 
 # ──────────────────────────────────────────────────────────────────────────────
 # Helpers – type inference & SA type instantiation
@@ -342,6 +349,39 @@ def _attach_model_ops_namespace(model: type) -> None:
     model.opspecs = ops_ns
 
 
+def _normalize_table_profile_declaration(cls: type) -> None:
+    profile_attr = "TABLE_PROFILE"
+    explicit_profile = profile_attr in cls.__dict__
+
+    legacy_attrs = {
+        "DEFAULT_CANON_VERBS",
+        "should_wire_canonical",
+        "__tigrbl_defaults_mode__",
+        "__tigrbl_defaults_include__",
+        "__tigrbl_defaults_exclude__",
+        "__tigrbl_ops__",
+        "OPS",
+    }
+    present_legacy = sorted(name for name in legacy_attrs if name in cls.__dict__)
+    cfg = cls.__dict__.get("table_config")
+    if isinstance(cfg, dict) and (
+        "binding_profiles" in cfg
+        or "default_bindings" in cfg
+        or "default_binding_profiles" in cfg
+    ):
+        present_legacy.append("table_config.binding_profiles")
+
+    if explicit_profile and present_legacy:
+        raise TableProfileError(
+            f"{cls.__name__} declares TABLE_PROFILE and legacy table default "
+            f"authority {', '.join(present_legacy)}"
+        )
+
+    value = cls.__dict__.get(profile_attr, getattr(cls, profile_attr, PLAIN_TABLE_PROFILE))
+    normalized = coerce_table_profile(value)
+    setattr(cls, profile_attr, normalized)
+
+
 # ──────────────────────────────────────────────────────────────────────────────
 # Declarative Base
 # ──────────────────────────────────────────────────────────────────────────────
@@ -349,8 +389,11 @@ def _attach_model_ops_namespace(model: type) -> None:
 
 class TableBase(DeclarativeBase):
     __allow_unmapped__ = True
+    TABLE_PROFILE = PLAIN_TABLE_PROFILE
 
     def __init_subclass__(cls, **kw):
+        _normalize_table_profile_declaration(cls)
+
         # 0) Remove any previously registered class with the same module path.
         try:
             reg = TableBase.registry._class_registry
@@ -540,4 +583,14 @@ class TableBase(DeclarativeBase):
         return getattr(self, key)
 
 
-__all__ = ["TableBase"]
+class CrudTableBase(TableBase):
+    __abstract__ = True
+    TABLE_PROFILE = CRUD_TABLE_PROFILE
+
+
+class RealtimeTableBase(TableBase):
+    __abstract__ = True
+    TABLE_PROFILE = REALTIME_TABLE_PROFILE
+
+
+__all__ = ["CrudTableBase", "RealtimeTableBase", "TableBase"]

tigrbl_base-0.4.2.dev3/README.md

@@ -1,70 +0,0 @@
-<div align="center">
-<h1>tigrbl-base</h1>
-<img src="https://raw.githubusercontent.com/swarmauri/swarmauri-sdk/master/assets/tigrbl_full_logo.png" alt="Tigrbl logo" width="140"/>
-<p><strong>Base contract package for Tigrbl apps, routers, tables, sessions, middleware, requests, responses, bindings, and engine interfaces.</strong></p>
-<a href="https://pypi.org/project/tigrbl-base/"><img src="https://img.shields.io/pypi/v/tigrbl-base?label=PyPI" alt="PyPI version for tigrbl-base"/></a>
-<a href="https://pypi.org/project/tigrbl-base/"><img src="https://static.pepy.tech/badge/tigrbl-base" alt="Downloads for tigrbl-base"/></a>
-<a href="https://github.com/tigrbl/tigrbl/blob/master/pkgs/core/tigrbl_base/README.md"><img src="https://hits.sh/github.com/tigrbl/tigrbl/blob/master/pkgs/core/tigrbl_base/README.md.svg?label=hits" alt="Repository hits for tigrbl-base README"/></a>
-<a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache%202.0-525252" alt="Apache 2.0 license"/></a>
-<a href="pyproject.toml"><img src="https://img.shields.io/badge/python-3.10%20to%203.15-3776ab" alt="Python requirement for tigrbl-base"/></a>
-<a href="https://github.com/tigrbl/tigrbl/blob/master/docs/README.md"><img src="https://img.shields.io/badge/workspace-core-1f6feb" alt="Workspace group for tigrbl-base"/></a>
-</div>
-
-## Install
-
-```bash
-uv add tigrbl-base
-```
-
-```bash
-pip install tigrbl-base
-```
-
-## What It Owns
-
-`tigrbl-base` owns the base boundary inside the split Python workspace.
-
-## Use It When
-
-Use `tigrbl-base` when you want this subsystem directly as a package boundary instead of consuming it only through the top-level `tigrbl` facade.
-
-## Public Surface
-
-- Package-local implementation lives under `pkgs/core/tigrbl_base` and is consumed as a distribution boundary rather than a single broad root re-export.
-
-## Internal Layout
-
-- Workspace path: `pkgs/core/tigrbl_base`.
-- Package class: `core framework package`.
-- Python requirement: `>=3.10,<3.15`.
-
-## Dependency Surface
-
-- Workspace package dependencies: [`tigrbl-core`](https://pypi.org/project/tigrbl-core/), [`tigrbl-atoms`](https://pypi.org/project/tigrbl-atoms/).
-- External runtime dependencies: `sqlalchemy>=2.0`, `pydantic>=2.0`.
-- Optional extras: none declared.
-
-## Related Packages
-
-- [`tigrbl`](https://pypi.org/project/tigrbl/)
-- [`tigrbl-core`](https://pypi.org/project/tigrbl-core/)
-- [`tigrbl-atoms`](https://pypi.org/project/tigrbl-atoms/)
-
-## Canonical Repository Docs
-
-- `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-local Boundary
-
-This file is a package-local distribution entry point.
-Use this page for package installation and boundary orientation. Repository governance, conformance state, target status, and release evidence remain governed from `docs/` and `.ssot/`.
-
-## License
-
-Licensed under the Apache License, Version 2.0. See `LICENSE` and the official [Apache 2.0 license text](https://www.apache.org/licenses/LICENSE-2.0).