tigrbl 0.3.16.dev4__tar.gz → 0.3.17__tar.gz

{tigrbl-0.3.16.dev4 → tigrbl-0.3.17}/PKG-INFO

@@ -1,10 +1,9 @@
 Metadata-Version: 2.4
 Name: tigrbl
-Version: 0.3.16.dev4
+Version: 0.3.17
 Summary: A modern pure ASGI/WSGI Python framework for building schema-first REST and JSON-RPC APIs with SQLAlchemy models, typed validation, lifecycle hooks, and engine extension support.
 License-Expression: Apache-2.0
 License-File: LICENSE
-Keywords: tigrbl,sdk,standards,asgi,rest,rpc
 Author: Jacob Stewart
 Author-email: jacob@swarmauri.com
 Requires-Python: >=3.10,<3.13
@@ -27,6 +26,15 @@ Requires-Dist: jinja2 (>=3.1.4) ; extra == "templates"
 Requires-Dist: psycopg2-binary (>=2.9.9) ; extra == "postgres"
 Requires-Dist: pydantic (>=2.0.0)
 Requires-Dist: sqlalchemy (>=2.0)
+Requires-Dist: tigrbl-atoms
+Requires-Dist: tigrbl-base
+Requires-Dist: tigrbl-canon
+Requires-Dist: tigrbl-concrete
+Requires-Dist: tigrbl-core
+Requires-Dist: tigrbl-kernel
+Requires-Dist: tigrbl-ops-oltp
+Requires-Dist: tigrbl-orm
+Requires-Dist: tigrbl-runtime
 Requires-Dist: tigrbl-tests ; extra == "tests"
 Requires-Dist: uvicorn
 Description-Content-Type: text/markdown
@@ -59,11 +67,28 @@ A high-leverage ASGI meta-framework that turns plain SQLAlchemy models into a fu
 - 🧩 Pluggable engine and provider abstractions
 - 🚀 Built as an ASGI-native framework with Pydantic-powered schema generation
 
+## Split Package Module Locations 🗂️
+
+These surfaces are now maintained in the split Tigrbl packages (with `tigrbl.*`
+kept as compatibility imports):
+
+- `tigrbl.ddl` → `tigrbl_concrete.ddl`
+- `tigrbl.system` → `tigrbl_concrete.system`
+- `tigrbl.op` → `tigrbl_core.op`
+- `tigrbl.config` → `tigrbl_core.config`
+- `tigrbl.schema` → `tigrbl_core.schema`
+- `tigrbl.security` → `tigrbl_concrete.security`
+
+## Runtime-owned Routing Contract
+
+For the kernel-first flow that avoids pre-runtime REST/RPC dispatching, see
+[`RUNTIME_OWNED_ROUTING.md`](./RUNTIME_OWNED_ROUTING.md).
+
 ## Terminology 📚
 
 - **Tenant** 🏢 – a namespace used to group related resources.
 - **Principal** 👤 – an owner of resources, such as an individual user or an organization.
-- **Resource** 📦 – a logical collection of data or functionality exposed by the API.
+- **Resource** 📦 – a logical collection of data or functionality exposed by the router.
 - **Engine** ⚙️ – the database connection and transaction manager backing a resource.
 - **Model / Table** 🧱 – the ORM or database representation of a resource's records.
 - **Column** 📏 – a field on a model that maps to a table column.
@@ -223,7 +248,7 @@ Operation Handler
 v
 JSON-RPC Response
 
-````
+```
 
 ## Hooks 🪝
 
@@ -240,7 +265,7 @@ class Item(Base):
     async def validate(cls, ctx):
         if ctx["request"].payload.get("name") == "bad":
             raise ValueError("invalid name")
-````
+```
 
 The function runs during the `PRE_HANDLER` phase of `create`. The
 `ctx` mapping provides request and response objects, a database session,
@@ -310,7 +335,7 @@ increasing order of precedence:
 
 1. defaults
 2. app config
-3. API config
+3. router config
 4. table config
 5. column config
 6. operation spec
@@ -318,7 +343,7 @@ increasing order of precedence:
 
 Later entries override earlier ones, so request overrides win over all other
 sources. This can be summarized as
-`overrides > opspec > colspecs > tabspec > apispec > appspec > defaults`.
+`overrides > opspec > colspecs > tabspec > routerspec > appspec > defaults`.
 
 ### Schema Config Precedence 🧬
 
@@ -327,7 +352,7 @@ Later layers override earlier ones, with the precedence order:
 
 1. defaults (lowest)
 2. app configuration
-3. API configuration
+3. router configuration
 4. table configuration
 5. column-level `cfg` values
 6. op-specific `cfg`
@@ -367,7 +392,7 @@ This hierarchy ensures that the most specific settings always win. 🥇
 When assembling values for persistence, defaults are resolved in this order:
 
 1. Client-supplied value
-2. API `default_factory`
+2. router `default_factory`
 3. ORM default
 4. Database `server_default`
 5. HTTP 422 if the field is required and still missing
@@ -408,15 +433,15 @@ approved usage. These are not optional—adhering to them keeps the runtime
 predictable, preserves hook lifecycle guarantees, and ensures schema
 consistency across REST and RPC surfaces.
 
-### 1) Never import SQLAlchemy directly or bypass Tigrbl APIs
+### 1) Never import SQLAlchemy directly or bypass Tigrbl routers
 
 **Why:** Direct imports bypass Tigrbl's compatibility layer and make it
 harder to evolve internal dependencies. Use the Tigrbl exports so your
-code stays aligned with the framework’s versioned ASGI API.
+code stays aligned with the framework’s versioned ASGI router.
 
 ✅ **Preferred:**
 ```python
-from tigrbl import Base, TigrblApp, TigrblApi
+from tigrbl import Base, TigrblApp, TigrblRouter
 from tigrbl.types import Integer, String, Mapped
 from tigrbl.types import Depends, HTTPException, Request
 ```
@@ -452,12 +477,12 @@ item_id = UUID(str(payload["id"]))
 ### 3) Use engine specs for persistence, not ad-hoc engines
 
 **Why:** Engine specs make persistence declarative, testable, and
-compatible with engine resolution across app, API, table, and op scopes.
+compatible with engine resolution across app, router, table, and op scopes.
 
 ✅ **Preferred:**
 ```python
 from tigrbl.engine.shortcuts import engine_spec
-from tigrbl.engine.decorators import engine_ctx
+from tigrbl.decorators.engine import engine_ctx
 
 spec = engine_spec(kind="postgres", async_=True, host="db", name="app_db")
 
@@ -588,9 +613,9 @@ async def rotate_keys(payload, *, ctx):
 
 🚫 **Avoid:**
 ```python
-from some_framework import APIRouter
+from some_framework import routerRouter
 
-router = APIRouter()
+router = routerRouter()
 
 @router.post("/keys/rotate")
 async def rotate_keys(payload):
@@ -606,7 +631,7 @@ resolved deterministically by the runtime.
 ✅ **Preferred:**
 ```python
 from tigrbl import hook_ctx, op_ctx, schema_ctx
-from tigrbl.engine.decorators import engine_ctx
+from tigrbl.decorators.engine import engine_ctx
 
 @engine_ctx(kind="sqlite", mode="memory")
 class Item(Table):
@@ -629,7 +654,7 @@ async def validate(ctx):
 
 ```python
 from tigrbl.engine.shortcuts import engine_spec, prov
-from tigrbl.engine._engine import Engine, Provider
+from tigrbl._concrete._engine import Engine, Provider
 
 # Build an EngineSpec from a DSN string
 spec = engine_spec("sqlite://:memory:")
@@ -656,7 +681,7 @@ provider_pg = Provider(spec_pg)
 `engine_ctx` binds database configuration to different layers. It accepts a
 DSN string, a mapping, an `EngineSpec`, a `Provider`, or an `Engine`. The
 resolver chooses the most specific binding in the order
-`op > table > api > app`.
+`op > table > router > app`.
 
 #### Engine precedence 🥇
 
@@ -664,8 +689,8 @@ When engine contexts are declared at multiple scopes, Tigrbl resolves them
 with strict precedence:
 
 1. **Op level** – bindings attached directly to an operation take highest priority.
-2. **Table/Model level** – definitions on a model or table override API and app defaults.
-3. **API level** – bindings on the API class apply when no model-specific context exists.
+2. **Table/Model level** – definitions on a model or table override router and app defaults.
+3. **router level** – bindings on the router class apply when no model-specific context exists.
 4. **App level** – the default engine supplied to the application is used last.
 
 This ordering ensures that the most specific engine context always wins.
@@ -679,7 +704,7 @@ from tigrbl.engine.shortcuts import prov, engine
 app = SimpleNamespace(db=prov(kind="sqlite", mode="memory"))
 alt = SimpleNamespace(db=engine(kind="sqlite", mode="memory"))
 
-class API:
+class router:
     db = {"kind": "sqlite", "memory": True}
 
 class Item:
@@ -700,7 +725,7 @@ create.__tigrbl_engine_ctx__ = {
 #### Decorative bindings 🎛️
 
 ```python
-from tigrbl.engine.decorators import engine_ctx
+from tigrbl.decorators.engine import engine_ctx
 from tigrbl.engine.shortcuts import prov, engine
 
 @engine_ctx(prov(kind="sqlite", mode="memory"))
@@ -708,7 +733,7 @@ class App:
     pass
 
 @engine_ctx(engine(kind="sqlite", mode="memory"))
-class DecoratedAPI:
+class Decoratedrouter:
     pass
 
 @engine_ctx(kind="sqlite", mode="memory")
@@ -735,7 +760,7 @@ The bridge examples cover two integration styles:
   * A Swarmauri `Factory` invocation during `PRE_HANDLER` via `hook_ctx`.
   * Tigrbl default verbs (`create`, `get`, `list`, `update`, `delete`) plus a custom op.
   * `engine_ctx` at model and operation scope.
-  * Generated OpenAPI and OpenRPC documents mounted from the same model bindings.
+  * Generated Openrouter and OpenRPC documents mounted from the same model bindings.
 
 * **Smoother direct-model flow** (`swarmauri_tigrbl_bridge_smooth.py`)
   * Uses hooks + default `create` persistence to normalize Swarmauri payloads.

{tigrbl-0.3.16.dev4 → tigrbl-0.3.17}/README.md

@@ -26,11 +26,28 @@ A high-leverage ASGI meta-framework that turns plain SQLAlchemy models into a fu
 - 🧩 Pluggable engine and provider abstractions
 - 🚀 Built as an ASGI-native framework with Pydantic-powered schema generation
 
+## Split Package Module Locations 🗂️
+
+These surfaces are now maintained in the split Tigrbl packages (with `tigrbl.*`
+kept as compatibility imports):
+
+- `tigrbl.ddl` → `tigrbl_concrete.ddl`
+- `tigrbl.system` → `tigrbl_concrete.system`
+- `tigrbl.op` → `tigrbl_core.op`
+- `tigrbl.config` → `tigrbl_core.config`
+- `tigrbl.schema` → `tigrbl_core.schema`
+- `tigrbl.security` → `tigrbl_concrete.security`
+
+## Runtime-owned Routing Contract
+
+For the kernel-first flow that avoids pre-runtime REST/RPC dispatching, see
+[`RUNTIME_OWNED_ROUTING.md`](./RUNTIME_OWNED_ROUTING.md).
+
 ## Terminology 📚
 
 - **Tenant** 🏢 – a namespace used to group related resources.
 - **Principal** 👤 – an owner of resources, such as an individual user or an organization.
-- **Resource** 📦 – a logical collection of data or functionality exposed by the API.
+- **Resource** 📦 – a logical collection of data or functionality exposed by the router.
 - **Engine** ⚙️ – the database connection and transaction manager backing a resource.
 - **Model / Table** 🧱 – the ORM or database representation of a resource's records.
 - **Column** 📏 – a field on a model that maps to a table column.
@@ -190,7 +207,7 @@ Operation Handler
 v
 JSON-RPC Response
 
-````
+```
 
 ## Hooks 🪝
 
@@ -207,7 +224,7 @@ class Item(Base):
     async def validate(cls, ctx):
         if ctx["request"].payload.get("name") == "bad":
             raise ValueError("invalid name")
-````
+```
 
 The function runs during the `PRE_HANDLER` phase of `create`. The
 `ctx` mapping provides request and response objects, a database session,
@@ -277,7 +294,7 @@ increasing order of precedence:
 
 1. defaults
 2. app config
-3. API config
+3. router config
 4. table config
 5. column config
 6. operation spec
@@ -285,7 +302,7 @@ increasing order of precedence:
 
 Later entries override earlier ones, so request overrides win over all other
 sources. This can be summarized as
-`overrides > opspec > colspecs > tabspec > apispec > appspec > defaults`.
+`overrides > opspec > colspecs > tabspec > routerspec > appspec > defaults`.
 
 ### Schema Config Precedence 🧬
 
@@ -294,7 +311,7 @@ Later layers override earlier ones, with the precedence order:
 
 1. defaults (lowest)
 2. app configuration
-3. API configuration
+3. router configuration
 4. table configuration
 5. column-level `cfg` values
 6. op-specific `cfg`
@@ -334,7 +351,7 @@ This hierarchy ensures that the most specific settings always win. 🥇
 When assembling values for persistence, defaults are resolved in this order:
 
 1. Client-supplied value
-2. API `default_factory`
+2. router `default_factory`
 3. ORM default
 4. Database `server_default`
 5. HTTP 422 if the field is required and still missing
@@ -375,15 +392,15 @@ approved usage. These are not optional—adhering to them keeps the runtime
 predictable, preserves hook lifecycle guarantees, and ensures schema
 consistency across REST and RPC surfaces.
 
-### 1) Never import SQLAlchemy directly or bypass Tigrbl APIs
+### 1) Never import SQLAlchemy directly or bypass Tigrbl routers
 
 **Why:** Direct imports bypass Tigrbl's compatibility layer and make it
 harder to evolve internal dependencies. Use the Tigrbl exports so your
-code stays aligned with the framework’s versioned ASGI API.
+code stays aligned with the framework’s versioned ASGI router.
 
 ✅ **Preferred:**
 ```python
-from tigrbl import Base, TigrblApp, TigrblApi
+from tigrbl import Base, TigrblApp, TigrblRouter
 from tigrbl.types import Integer, String, Mapped
 from tigrbl.types import Depends, HTTPException, Request
 ```
@@ -419,12 +436,12 @@ item_id = UUID(str(payload["id"]))
 ### 3) Use engine specs for persistence, not ad-hoc engines
 
 **Why:** Engine specs make persistence declarative, testable, and
-compatible with engine resolution across app, API, table, and op scopes.
+compatible with engine resolution across app, router, table, and op scopes.
 
 ✅ **Preferred:**
 ```python
 from tigrbl.engine.shortcuts import engine_spec
-from tigrbl.engine.decorators import engine_ctx
+from tigrbl.decorators.engine import engine_ctx
 
 spec = engine_spec(kind="postgres", async_=True, host="db", name="app_db")
 
@@ -555,9 +572,9 @@ async def rotate_keys(payload, *, ctx):
 
 🚫 **Avoid:**
 ```python
-from some_framework import APIRouter
+from some_framework import routerRouter
 
-router = APIRouter()
+router = routerRouter()
 
 @router.post("/keys/rotate")
 async def rotate_keys(payload):
@@ -573,7 +590,7 @@ resolved deterministically by the runtime.
 ✅ **Preferred:**
 ```python
 from tigrbl import hook_ctx, op_ctx, schema_ctx
-from tigrbl.engine.decorators import engine_ctx
+from tigrbl.decorators.engine import engine_ctx
 
 @engine_ctx(kind="sqlite", mode="memory")
 class Item(Table):
@@ -596,7 +613,7 @@ async def validate(ctx):
 
 ```python
 from tigrbl.engine.shortcuts import engine_spec, prov
-from tigrbl.engine._engine import Engine, Provider
+from tigrbl._concrete._engine import Engine, Provider
 
 # Build an EngineSpec from a DSN string
 spec = engine_spec("sqlite://:memory:")
@@ -623,7 +640,7 @@ provider_pg = Provider(spec_pg)
 `engine_ctx` binds database configuration to different layers. It accepts a
 DSN string, a mapping, an `EngineSpec`, a `Provider`, or an `Engine`. The
 resolver chooses the most specific binding in the order
-`op > table > api > app`.
+`op > table > router > app`.
 
 #### Engine precedence 🥇
 
@@ -631,8 +648,8 @@ When engine contexts are declared at multiple scopes, Tigrbl resolves them
 with strict precedence:
 
 1. **Op level** – bindings attached directly to an operation take highest priority.
-2. **Table/Model level** – definitions on a model or table override API and app defaults.
-3. **API level** – bindings on the API class apply when no model-specific context exists.
+2. **Table/Model level** – definitions on a model or table override router and app defaults.
+3. **router level** – bindings on the router class apply when no model-specific context exists.
 4. **App level** – the default engine supplied to the application is used last.
 
 This ordering ensures that the most specific engine context always wins.
@@ -646,7 +663,7 @@ from tigrbl.engine.shortcuts import prov, engine
 app = SimpleNamespace(db=prov(kind="sqlite", mode="memory"))
 alt = SimpleNamespace(db=engine(kind="sqlite", mode="memory"))
 
-class API:
+class router:
     db = {"kind": "sqlite", "memory": True}
 
 class Item:
@@ -667,7 +684,7 @@ create.__tigrbl_engine_ctx__ = {
 #### Decorative bindings 🎛️
 
 ```python
-from tigrbl.engine.decorators import engine_ctx
+from tigrbl.decorators.engine import engine_ctx
 from tigrbl.engine.shortcuts import prov, engine
 
 @engine_ctx(prov(kind="sqlite", mode="memory"))
@@ -675,7 +692,7 @@ class App:
     pass
 
 @engine_ctx(engine(kind="sqlite", mode="memory"))
-class DecoratedAPI:
+class Decoratedrouter:
     pass
 
 @engine_ctx(kind="sqlite", mode="memory")
@@ -702,7 +719,7 @@ The bridge examples cover two integration styles:
   * A Swarmauri `Factory` invocation during `PRE_HANDLER` via `hook_ctx`.
   * Tigrbl default verbs (`create`, `get`, `list`, `update`, `delete`) plus a custom op.
   * `engine_ctx` at model and operation scope.
-  * Generated OpenAPI and OpenRPC documents mounted from the same model bindings.
+  * Generated Openrouter and OpenRPC documents mounted from the same model bindings.
 
 * **Smoother direct-model flow** (`swarmauri_tigrbl_bridge_smooth.py`)
   * Uses hooks + default `create` persistence to normalize Swarmauri payloads.

{tigrbl-0.3.16.dev4 → tigrbl-0.3.17}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "tigrbl"
-version = "0.3.16.dev4"
+version = "0.3.17"
 description = "A modern pure ASGI/WSGI Python framework for building schema-first REST and JSON-RPC APIs with SQLAlchemy models, typed validation, lifecycle hooks, and engine extension support."
 license = "Apache-2.0"
 readme = "README.md"
@@ -18,22 +18,24 @@ classifiers = [
 ]
 authors = [{ name = "Jacob Stewart", email = "jacob@swarmauri.com" }]
 dependencies = [
+    "tigrbl-core",
+    "tigrbl-base",
+    "tigrbl-concrete",
+    "tigrbl-canon",
+    "tigrbl-orm",
+    "tigrbl-runtime",
+    "tigrbl-atoms",
+    "tigrbl-kernel",
+    "tigrbl-ops-oltp",
     "pydantic>=2.0.0",
     "sqlalchemy>=2.0",
     "aiosqlite>=0.19.0",
     "httpx>=0.27.0",
     "greenlet>=3.2.3",
-    "uvicorn", 
-]
-keywords = [
-    'tigrbl',
-    'sdk',
-    'standards',
-    'asgi',
-    'rest',
-    'rpc',
+    "uvicorn",
 ]
 
+
 [project.optional-dependencies]
 postgres = [
     "asyncpg>=0.30.0",
@@ -47,7 +49,18 @@ tests = [
 ]
 
 [tool.uv.sources]
+"tigrbl-core" = { workspace = true }
+"tigrbl-base" = { workspace = true }
+"tigrbl-concrete" = { workspace = true }
+"tigrbl-canon" = { workspace = true }
+"tigrbl-orm" = { workspace = true }
+"tigrbl-runtime" = { workspace = true }
+"tigrbl-atoms" = { workspace = true }
+"tigrbl-kernel" = { workspace = true }
+"tigrbl-ops-oltp" = { workspace = true }
 tigrbl-tests = { workspace = true }
+tigrbl_client = { workspace = true }
+
 
 [tool.pytest.ini_options]
 norecursedirs = ["combined", "scripts"]
@@ -81,6 +94,7 @@ packages = [
 
 [dependency-groups]
 dev = [
+    "tigrbl_client",
     "pytest>=8.0",
     "pytest-asyncio>=0.24.0",
     "pytest-xdist>=3.6.1",

{tigrbl-0.3.16.dev4 → tigrbl-0.3.17}/tigrbl/README.md

@@ -86,7 +86,7 @@ Some objects also expose optional helpers:
 | Column | `column_spec.py` | `_column.py` | — | `shortcuts.py` | `collect.py` | — | — |
 | Engine | `engine_spec.py` | `_engine.py` | `decorators.py` | `shortcuts.py` | `collect.py` | `resolver.py` | `builders.py` |
 | Op | `types.py` | `_op.py` | `decorators.py` | — | `collect.py` | — | — |
-| API | `api_spec.py` | `_api.py` | — | `shortcuts.py` | — | — | — |
+| API | `router_spec.py` | `_api.py` | — | `shortcuts.py` | — | — | — |
 | App | `app_spec.py` | `_app.py` | — | `shortcuts.py` | — | — | — |
 | Table | `table_spec.py` | `_table.py` | — | `shortcuts.py` | — | — | — |