quadkit 0.0.2__tar.gz → 0.0.4__tar.gz

{quadkit-0.0.2 → quadkit-0.0.4}/.gitignore

@@ -28,6 +28,8 @@
 !.importlinter
 !.superpowers/
 !.superpowers/**
+!.gitattributes
+!.editorconfig
 !Makefile
 !docker-compose.test.yml
 !quadkit.yaml.example
@@ -98,69 +100,62 @@ internal-docs/
 # Editor swap files
 *.swp
 
-# Tiered package layout (core/, packages/, experimental/<family>/)
 !core/
 !packages/
-!experimental/
-!experimental/*/
 !core/quadkit*/
 !packages/quadkit*/
-!experimental/*/quadkit*/
 !core/quadkit*/pyproject.toml
 !packages/quadkit*/pyproject.toml
-!experimental/*/quadkit*/pyproject.toml
 !core/quadkit*/CHANGELOG.md
 !packages/quadkit*/CHANGELOG.md
-!experimental/*/quadkit*/CHANGELOG.md
 !core/quadkit*/README.md
 !packages/quadkit*/README.md
-!experimental/*/quadkit*/README.md
 !core/quadkit*/alembic.ini
 !packages/quadkit*/alembic.ini
-!experimental/*/quadkit*/alembic.ini
 !core/quadkit*/mypy.ini
 !packages/quadkit*/mypy.ini
-!experimental/*/quadkit*/mypy.ini
 !core/quadkit*/*.yaml.example
 !packages/quadkit*/*.yaml.example
-!experimental/*/quadkit*/*.yaml.example
 !core/quadkit*/src/
 !core/quadkit*/src/**
 !packages/quadkit*/src/
 !packages/quadkit*/src/**
-!experimental/*/quadkit*/src/
-!experimental/*/quadkit*/src/**
 !core/quadkit*/tests/
 !core/quadkit*/tests/**
 !packages/quadkit*/tests/
 !packages/quadkit*/tests/**
-!experimental/*/quadkit*/tests/
-!experimental/*/quadkit*/tests/**
 !core/quadkit*/docs/
 !core/quadkit*/docs/**
 !packages/quadkit*/docs/
 !packages/quadkit*/docs/**
-!experimental/*/quadkit*/docs/
-!experimental/*/quadkit*/docs/**
 
 # dev/
 !dev/
 !dev/**
 
 # Admin dev playground (committed dev asset; local SQLite files stay ignored)
-!experimental/*/quadkit*/playground/
-!experimental/*/quadkit*/playground/**
-experimental/*/quadkit*/playground/*.db
-experimental/*/quadkit*/playground/*.db-*
+!packages/quadkit-admin/playground/
+!packages/quadkit-admin/playground/serve.py
+
+# gatewai apps
+!apps/
+!apps/**
+!apps/gatewai/
+!apps/gatewai/**
+apps/**/node_modules/
+apps/**/dist/
+apps/**/__pycache__/
+apps/**/*.pyc
+apps/**/*.db
+apps/**/*.db-wal
+apps/**/*.db-shm
 
 # Re-exclude private content under the tiered paths.
 # MUST come after the !...docs/** negations above — last match wins.
 core/quadkit*/docs/plans/
 packages/quadkit*/docs/plans/
-experimental/*/quadkit*/docs/plans/
 core/quadkit*/docs/**/
 packages/quadkit*/docs/**/
-experimental/*/quadkit*/docs/**/
 
 # Re-exclude tooling artifacts under the tiered paths
 __pycache__/
@@ -178,13 +173,11 @@ test.db
 *.log
 !core/quadkit*/tests/fixtures/test.db
 !packages/quadkit*/tests/fixtures/test.db
-!experimental/*/quadkit*/tests/fixtures/test.db
 
 # Allow the generated example gifs to be tracked (README hero images).
 !core/quadkit*/docs/gifs/
 !core/quadkit*/docs/gifs/**
 !packages/*/quadkit*/docs/gifs/
 !packages/*/quadkit*/docs/gifs/**
-!experimental/*/quadkit*/docs/gifs/
-!experimental/*/quadkit*/docs/gifs/**
 examples/*/screenshot.png
+!banner*

quadkit-0.0.4/PKG-INFO

@@ -0,0 +1,270 @@
+Metadata-Version: 2.5
+Name: quadkit
+Version: 0.0.4
+Summary: Async-first DI/IoC framework for Python — core package
+Project-URL: Homepage, https://dbtinoy-.github.io/quadkit/
+Project-URL: Repository, https://github.com/dbtinoy-/quadkit
+Project-URL: Documentation, https://dbtinoy-.github.io/quadkit/
+Project-URL: Issues, https://github.com/dbtinoy-/quadkit/issues
+Project-URL: Changelog, https://github.com/dbtinoy-/quadkit/blob/main/CHANGELOG.md
+Author-email: Quadkit Framework Team <team@quadkit.dev>
+Maintainer-email: Quadkit Framework Team <team@quadkit.dev>
+License: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: async,dependency-injection,framework,ioc,provider-pattern
+Classifier: Development Status :: 3 - Alpha
+Classifier: Framework :: AsyncIO
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries :: Application Frameworks
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: orjson<4,>=3.0.0
+Requires-Dist: pydantic<3,>=2.10.0
+Requires-Dist: quadkit-contracts>=0.0.2
+Requires-Dist: structlog<27,>=25.1.0
+Provides-Extra: codegen
+Requires-Dist: jinja2<4,>=3.1.0; extra == 'codegen'
+Provides-Extra: dev
+Requires-Dist: mypy<3,>=1.0.0; extra == 'dev'
+Requires-Dist: pre-commit<5,>=3.0.0; extra == 'dev'
+Requires-Dist: ruff<1,>=0.16.4; extra == 'dev'
+Provides-Extra: docs
+Requires-Dist: mkdocs-material<10,>=9.0.0; extra == 'docs'
+Requires-Dist: mkdocs<2,>=1.4.0; extra == 'docs'
+Provides-Extra: security
+Requires-Dist: cryptography<52,>=41.0.0; extra == 'security'
+Provides-Extra: test
+Requires-Dist: pytest-asyncio<2,>=0.21.0; extra == 'test'
+Requires-Dist: pytest-cov<8,>=4.0.0; extra == 'test'
+Requires-Dist: pytest-mock<4,>=3.10.0; extra == 'test'
+Requires-Dist: pytest<10,>=8.0.0; extra == 'test'
+Provides-Extra: web
+Requires-Dist: quadkit-web[granian]>=0.0.2; extra == 'web'
+Description-Content-Type: text/markdown
+
+# quadkit
+
+![Quadkit](https://raw.githubusercontent.com/dbtinoy-/quadkit/main/banner.jpg)
+
+[![PyPI](https://img.shields.io/pypi/v/quadkit?color=%2322c55e&label=pypi)](https://pypi.org/project/quadkit/)
+[![Python](https://img.shields.io/pypi/pyversions/quadkit?color=%2322c55e)](https://pypi.org/project/quadkit/)
+[![License](https://img.shields.io/pypi/l/quadkit?color=%2322c55e)](https://github.com/dbtinoy-/quadkit/blob/main/LICENSE)
+
+Async-first application framework for Python: dependency-injection
+container, application lifecycle, typed configuration, and the `Result`
+error model. This is the core package; everything else published from
+this repository builds on it.
+
+For application developers — write providers and modules, bind
+contracts, and let one container boot them in order.
+
+What's in the box:
+
+- **DI container** — singleton, scoped, and transient bindings, async
+  factories, override support for tests; the graph resolves once, at
+  boot.
+- **Provider & module system** — providers register bindings, boot
+  resources, and shut them down in reverse order; modules compose
+  providers into reusable units.
+- **Typed configuration** — `application.yaml` validated against
+  dataclass models at boot (unknown keys fail fast), every key
+  overridable via `QK_*` environment variables, profiles via `QK_PROFILE`.
+- **The `Result` model** — expected failures are values
+  (`Ok`/`Err`), not exceptions; `ResultPipeline` chains them fluently
+  while keeping the error type visible to mypy.
+- **Structured logging** — `get_logger()` gives every service a
+  keyed, structlog-style logger out of the box.
+- **Domain primitives** — `AggregateRoot`, `Entity`, `DomainEvent`,
+  `AbstractUnitOfWork` for DDD-style modelling without a framework
+  tax.
+
+## The quadkit family
+
+| Package | Role |
+| --- | --- |
+| [`quadkit-contracts`](https://pypi.org/project/quadkit-contracts/) | zero-dependency protocols, types, exception hierarchy |
+| [`quadkit`](https://pypi.org/project/quadkit/) | the framework core — DI container, modules, config, logging, `Result` |
+| [`quadkit-web`](https://pypi.org/project/quadkit-web/) | ASGI layer — controllers, routing, middleware, OpenAPI docs |
+| [`quadkit-cli`](https://pypi.org/project/quadkit-cli/) | project scaffolding and code generators |
+| [`quadkit-testing`](https://pypi.org/project/quadkit-testing/) | in-process test beds, fakes, fixtures |
+
+## Installation
+
+```bash
+uv add quadkit
+# batteries-included web stack:
+uv add "quadkit[web]"
+```
+
+Requires **Python >= 3.11**.
+
+## Minimal working example
+
+```python
+import asyncio
+
+from quadkit import Application
+from quadkit.contracts.core.di import ContainerRegistrarProtocol
+from quadkit.di.provider import Provider
+
+
+class Settings:
+    greeting = "hello, quadkit"
+
+
+class SettingsProvider(Provider):
+    async def register(self, container: ContainerRegistrarProtocol) -> None:
+        container.singleton(Settings, instance=Settings())
+
+
+async def main() -> None:
+    app = Application()
+    app.add_provider(SettingsProvider())
+    await app.start()
+    try:
+        settings = await app.container.resolve(Settings)
+        print(settings.greeting)
+    finally:
+        await app.stop()
+
+
+asyncio.run(main())
+```
+
+For the web quickstart (a real endpoint in minutes), see
+[the docs](https://dbtinoy-.github.io/quadkit/getting-started/first-app/).
+
+## Expected failures are values
+
+`Result[T, E]` keeps the happy path and the failure path in the type
+system — `pipeline()` chains fallible steps without `try/except`
+pyramids, and `mypy` sees the error type at every step:
+
+```python
+from quadkit.result import Err, Ok, pipeline
+
+
+def parse_port(raw: str):
+    try:
+        port = int(raw)
+    except ValueError as exc:
+        return Err(exc)
+    if not 1 <= port <= 65535:
+        return Err(ValueError(f"port out of range: {port}"))
+    return Ok(port)
+
+
+result = (
+    pipeline("8080")  # infallible start
+    .then(parse_port)  # Result[int, ValueError]
+    .map(lambda port: f"listening on :{port}")
+    .finalize()  # Result[str, ValueError]
+)
+```
+
+In controllers, returning an `Err` renders as an RFC 7807 problem
+response automatically — see the
+[error-handling guide](https://dbtinoy-.github.io/quadkit/guides/error-handling/).
+
+## Optional extras
+
+| Extra | Contents |
+| --- | --- |
+| `quadkit[web]` | `quadkit-web[granian]` — the full web stack |
+| `quadkit[test]` | `pytest`, `pytest-asyncio`, `pytest-cov`, `pytest-mock` |
+| `quadkit[security]` | `cryptography` (signing/token helpers) |
+| `quadkit[codegen]` | code generation toolchain |
+| `quadkit[docs]` / `[dev]` | documentation / development tooling |
+
+## Public API entry points
+
+```python
+from quadkit import Application, Result, Ok, Err
+from quadkit.di.provider import Provider
+from quadkit.di.container import Container
+from quadkit.config import BaseConfig, ConfigLoader
+from quadkit.logging import get_logger
+from quadkit.domain import AggregateRoot, Entity, DomainEvent, AbstractUnitOfWork
+from quadkit.contracts.core.di import (
+    ContainerRegistrarProtocol,
+    ContainerResolverProtocol,
+)
+```
+
+Providers can also define an async `boot()` (acquire resources) and
+`shutdown()` (release them, in reverse registration order) — the
+container drives the whole lifecycle.
+
+Concepts: [contracts](https://dbtinoy-.github.io/quadkit/concepts/contracts/) ·
+[dependency injection](https://dbtinoy-.github.io/quadkit/concepts/dependency-injection/) ·
+[modules](https://dbtinoy-.github.io/quadkit/concepts/modules/) ·
+[lifecycle](https://dbtinoy-.github.io/quadkit/concepts/lifecycle/) ·
+[async model](https://dbtinoy-.github.io/quadkit/concepts/async-model/).
+
+## Configuration
+
+`application.yaml` at the working directory, validated against typed
+config models at boot (unknown keys fail fast); application metadata
+lives at the root (`name`, `version`, `description`); every typed key
+overrides from the environment with `QK_<SECTION>__<KEY>`. Use
+`QK_PROFILE` to select a profile.
+
+```bash
+QK_QUADKIT__LOGGING__LEVEL=DEBUG   # fold into the root `logging` section
+QK_PROFILE=production              # select a profile block
+```
+
+See
+[configuration](https://dbtinoy-.github.io/quadkit/getting-started/configuration/).
+
+## Error handling
+
+`Result[T, E]` for expected domain failures; the
+`quadkit-contracts` exception hierarchy (`QuadkitError → DomainError →
+NotFoundError`, `ValidationError`, `ConflictError`, ...) for everything
+else. The web layer renders both as problem responses — see
+[error handling](https://dbtinoy-.github.io/quadkit/guides/error-handling/).
+
+## Testing
+
+Pair with `quadkit-testing`: `AppTestBed.from_factory(create_app)` boots
+your application in-process (with `overrides={Contract: fake}` for test
+doubles), no server required. See
+[testing](https://dbtinoy-.github.io/quadkit/getting-started/testing/).
+
+## Security
+
+Never put secrets in `application.yaml` — pass them through `QK_*`
+environment variables or a secret store. Unexpected exceptions never
+leak internals to clients. See
+[secure configuration](https://dbtinoy-.github.io/quadkit/security/secure-configuration/) and
+report vulnerabilities privately per
+[SECURITY.md](https://github.com/dbtinoy-/quadkit/blob/main/SECURITY.md).
+
+## Stability
+
+Version `0.0.3` in the `0.x` series, released in lockstep with the
+other four distributions; APIs may change between minor versions until
+1.0 — pin an exact version
+(`quadkit==0.0.3`) or a tight range (`>=0.0.3,<0.1.0`). Full policy:
+[stability and compatibility](https://dbtinoy-.github.io/quadkit/reference/stability/).
+
+## Links
+
+- **Documentation** — <https://dbtinoy-.github.io/quadkit/>
+- **Getting started** — <https://dbtinoy-.github.io/quadkit/getting-started/installation/>
+- **Changelog** — <https://github.com/dbtinoy-/quadkit/blob/main/CHANGELOG.md>
+- **Issues** — <https://github.com/dbtinoy-/quadkit/issues>
+- **Security** — report privately per [SECURITY.md](https://github.com/dbtinoy-/quadkit/blob/main/SECURITY.md)
+- **Contributing** — [CONTRIBUTING.md](https://github.com/dbtinoy-/quadkit/blob/main/CONTRIBUTING.md)
+
+Apache-2.0 — see [LICENSE](https://github.com/dbtinoy-/quadkit/blob/main/LICENSE). "Quadkit" and the
+Quadkit logo are trademarks of the project — see
+[TRADEMARK.md](https://github.com/dbtinoy-/quadkit/blob/main/TRADEMARK.md).

quadkit-0.0.4/README.md

@@ -0,0 +1,219 @@
+# quadkit
+
+![Quadkit](https://raw.githubusercontent.com/dbtinoy-/quadkit/main/banner.jpg)
+
+[![PyPI](https://img.shields.io/pypi/v/quadkit?color=%2322c55e&label=pypi)](https://pypi.org/project/quadkit/)
+[![Python](https://img.shields.io/pypi/pyversions/quadkit?color=%2322c55e)](https://pypi.org/project/quadkit/)
+[![License](https://img.shields.io/pypi/l/quadkit?color=%2322c55e)](https://github.com/dbtinoy-/quadkit/blob/main/LICENSE)
+
+Async-first application framework for Python: dependency-injection
+container, application lifecycle, typed configuration, and the `Result`
+error model. This is the core package; everything else published from
+this repository builds on it.
+
+For application developers — write providers and modules, bind
+contracts, and let one container boot them in order.
+
+What's in the box:
+
+- **DI container** — singleton, scoped, and transient bindings, async
+  factories, override support for tests; the graph resolves once, at
+  boot.
+- **Provider & module system** — providers register bindings, boot
+  resources, and shut them down in reverse order; modules compose
+  providers into reusable units.
+- **Typed configuration** — `application.yaml` validated against
+  dataclass models at boot (unknown keys fail fast), every key
+  overridable via `QK_*` environment variables, profiles via `QK_PROFILE`.
+- **The `Result` model** — expected failures are values
+  (`Ok`/`Err`), not exceptions; `ResultPipeline` chains them fluently
+  while keeping the error type visible to mypy.
+- **Structured logging** — `get_logger()` gives every service a
+  keyed, structlog-style logger out of the box.
+- **Domain primitives** — `AggregateRoot`, `Entity`, `DomainEvent`,
+  `AbstractUnitOfWork` for DDD-style modelling without a framework
+  tax.
+
+## The quadkit family
+
+| Package | Role |
+| --- | --- |
+| [`quadkit-contracts`](https://pypi.org/project/quadkit-contracts/) | zero-dependency protocols, types, exception hierarchy |
+| [`quadkit`](https://pypi.org/project/quadkit/) | the framework core — DI container, modules, config, logging, `Result` |
+| [`quadkit-web`](https://pypi.org/project/quadkit-web/) | ASGI layer — controllers, routing, middleware, OpenAPI docs |
+| [`quadkit-cli`](https://pypi.org/project/quadkit-cli/) | project scaffolding and code generators |
+| [`quadkit-testing`](https://pypi.org/project/quadkit-testing/) | in-process test beds, fakes, fixtures |
+
+## Installation
+
+```bash
+uv add quadkit
+# batteries-included web stack:
+uv add "quadkit[web]"
+```
+
+Requires **Python >= 3.11**.
+
+## Minimal working example
+
+```python
+import asyncio
+
+from quadkit import Application
+from quadkit.contracts.core.di import ContainerRegistrarProtocol
+from quadkit.di.provider import Provider
+
+
+class Settings:
+    greeting = "hello, quadkit"
+
+
+class SettingsProvider(Provider):
+    async def register(self, container: ContainerRegistrarProtocol) -> None:
+        container.singleton(Settings, instance=Settings())
+
+
+async def main() -> None:
+    app = Application()
+    app.add_provider(SettingsProvider())
+    await app.start()
+    try:
+        settings = await app.container.resolve(Settings)
+        print(settings.greeting)
+    finally:
+        await app.stop()
+
+
+asyncio.run(main())
+```
+
+For the web quickstart (a real endpoint in minutes), see
+[the docs](https://dbtinoy-.github.io/quadkit/getting-started/first-app/).
+
+## Expected failures are values
+
+`Result[T, E]` keeps the happy path and the failure path in the type
+system — `pipeline()` chains fallible steps without `try/except`
+pyramids, and `mypy` sees the error type at every step:
+
+```python
+from quadkit.result import Err, Ok, pipeline
+
+
+def parse_port(raw: str):
+    try:
+        port = int(raw)
+    except ValueError as exc:
+        return Err(exc)
+    if not 1 <= port <= 65535:
+        return Err(ValueError(f"port out of range: {port}"))
+    return Ok(port)
+
+
+result = (
+    pipeline("8080")  # infallible start
+    .then(parse_port)  # Result[int, ValueError]
+    .map(lambda port: f"listening on :{port}")
+    .finalize()  # Result[str, ValueError]
+)
+```
+
+In controllers, returning an `Err` renders as an RFC 7807 problem
+response automatically — see the
+[error-handling guide](https://dbtinoy-.github.io/quadkit/guides/error-handling/).
+
+## Optional extras
+
+| Extra | Contents |
+| --- | --- |
+| `quadkit[web]` | `quadkit-web[granian]` — the full web stack |
+| `quadkit[test]` | `pytest`, `pytest-asyncio`, `pytest-cov`, `pytest-mock` |
+| `quadkit[security]` | `cryptography` (signing/token helpers) |
+| `quadkit[codegen]` | code generation toolchain |
+| `quadkit[docs]` / `[dev]` | documentation / development tooling |
+
+## Public API entry points
+
+```python
+from quadkit import Application, Result, Ok, Err
+from quadkit.di.provider import Provider
+from quadkit.di.container import Container
+from quadkit.config import BaseConfig, ConfigLoader
+from quadkit.logging import get_logger
+from quadkit.domain import AggregateRoot, Entity, DomainEvent, AbstractUnitOfWork
+from quadkit.contracts.core.di import (
+    ContainerRegistrarProtocol,
+    ContainerResolverProtocol,
+)
+```
+
+Providers can also define an async `boot()` (acquire resources) and
+`shutdown()` (release them, in reverse registration order) — the
+container drives the whole lifecycle.
+
+Concepts: [contracts](https://dbtinoy-.github.io/quadkit/concepts/contracts/) ·
+[dependency injection](https://dbtinoy-.github.io/quadkit/concepts/dependency-injection/) ·
+[modules](https://dbtinoy-.github.io/quadkit/concepts/modules/) ·
+[lifecycle](https://dbtinoy-.github.io/quadkit/concepts/lifecycle/) ·
+[async model](https://dbtinoy-.github.io/quadkit/concepts/async-model/).
+
+## Configuration
+
+`application.yaml` at the working directory, validated against typed
+config models at boot (unknown keys fail fast); application metadata
+lives at the root (`name`, `version`, `description`); every typed key
+overrides from the environment with `QK_<SECTION>__<KEY>`. Use
+`QK_PROFILE` to select a profile.
+
+```bash
+QK_QUADKIT__LOGGING__LEVEL=DEBUG   # fold into the root `logging` section
+QK_PROFILE=production              # select a profile block
+```
+
+See
+[configuration](https://dbtinoy-.github.io/quadkit/getting-started/configuration/).
+
+## Error handling
+
+`Result[T, E]` for expected domain failures; the
+`quadkit-contracts` exception hierarchy (`QuadkitError → DomainError →
+NotFoundError`, `ValidationError`, `ConflictError`, ...) for everything
+else. The web layer renders both as problem responses — see
+[error handling](https://dbtinoy-.github.io/quadkit/guides/error-handling/).
+
+## Testing
+
+Pair with `quadkit-testing`: `AppTestBed.from_factory(create_app)` boots
+your application in-process (with `overrides={Contract: fake}` for test
+doubles), no server required. See
+[testing](https://dbtinoy-.github.io/quadkit/getting-started/testing/).
+
+## Security
+
+Never put secrets in `application.yaml` — pass them through `QK_*`
+environment variables or a secret store. Unexpected exceptions never
+leak internals to clients. See
+[secure configuration](https://dbtinoy-.github.io/quadkit/security/secure-configuration/) and
+report vulnerabilities privately per
+[SECURITY.md](https://github.com/dbtinoy-/quadkit/blob/main/SECURITY.md).
+
+## Stability
+
+Version `0.0.3` in the `0.x` series, released in lockstep with the
+other four distributions; APIs may change between minor versions until
+1.0 — pin an exact version
+(`quadkit==0.0.3`) or a tight range (`>=0.0.3,<0.1.0`). Full policy:
+[stability and compatibility](https://dbtinoy-.github.io/quadkit/reference/stability/).
+
+## Links
+
+- **Documentation** — <https://dbtinoy-.github.io/quadkit/>
+- **Getting started** — <https://dbtinoy-.github.io/quadkit/getting-started/installation/>
+- **Changelog** — <https://github.com/dbtinoy-/quadkit/blob/main/CHANGELOG.md>
+- **Issues** — <https://github.com/dbtinoy-/quadkit/issues>
+- **Security** — report privately per [SECURITY.md](https://github.com/dbtinoy-/quadkit/blob/main/SECURITY.md)
+- **Contributing** — [CONTRIBUTING.md](https://github.com/dbtinoy-/quadkit/blob/main/CONTRIBUTING.md)
+
+Apache-2.0 — see [LICENSE](https://github.com/dbtinoy-/quadkit/blob/main/LICENSE). "Quadkit" and the
+Quadkit logo are trademarks of the project — see
+[TRADEMARK.md](https://github.com/dbtinoy-/quadkit/blob/main/TRADEMARK.md).