techai-webutils

Development:

Overview

techai_webutils is the Python mirror of the knowledge-engine's Go substrate. It follows the same layers (core → foundation (+ execution) → clients → repos → services → pipelines → workflows → controllers) and the same rules, described in the repository's ARCHITECTURE.md. Every swappable component is a Kind + a config + a new_<type>_from_config factory, so switching a backend (memory → S3, stub → Bedrock, asyncio → Ray) is a configuration change.

How to use techai_webutils

uv add techai-webutils            # or: pip install techai-webutils
uv add "techai-webutils[postgres]"  # optional backends: ray, postgres, parsing, langdetect

Build a component from its config at your composition root and inject it:

from techai_webutils.clients.storage import (
    S3Config,
    StorageConfig,
    StorageKind,
    new_storage_from_config,
)

config = StorageConfig(
    kind=StorageKind.MEMORY,  # StorageKind.S3 in a deployment: same code, different config
    s3=S3Config(endpoint="", bucket="documents", region="us-east-1"),
)
storage = new_storage_from_config(config)

The base install already includes the AWS, gRPC, FastAPI, Qdrant, Redis and OpenTelemetry clients. The ray, postgres, parsing and langdetect extras are imported only when their backend is selected, so a service installs just the extras its configuration uses.

Load layered YAML config (base.yaml → {env}.yaml → secrets.yaml) under an env prefix of your own, and give your settings class the same env_prefix:

from techai_webutils.foundation.config import initialize_config

initialize_config("config", env_prefix="MYAPP")

Set a prefix: without one, config keys are exported under bare names (AWS_REGION, DEBUG) that collide with ambient variables, such as the service links Kubernetes injects (REDIS_PORT=tcp://…).