Forze Wiring

Use when setting up the Forze runtime, dependency registry, lifecycle, operation composition, and interface layer. For logical spec names, routes, and StrEnum wiring, see forze-specs-infrastructure. For dependency resolution, see forze-deps-consumption; for private integrations, see forze-custom-deps. For HTTP details, see forze-fastapi-interface. For day-to-day handler code, see forze-framework-usage.

For which plan enables deps, lifecycle hooks, or operation stages, see Three execution plans (DepsRegistry, LifecyclePlan, OperationRegistry).

Runtime setup

Logical specs (DocumentSpec, SearchSpec, CacheSpec, …) declare model types and name only—no DSNs, table names, collection paths, or index DDL. Deps modules (PostgresDepsModule, MongoDepsModule, RedisDepsModule, …) map that same name to physical configs (read/write relations, Redis namespaces, PostgresSearchConfig, …). DepsRegistry.from_modules(...) merges those modules so ExecutionContext resolves factories by route spec.name (for example DocumentQueryDepKey / DocumentCommandDepKey). See Specs and wiring.

Dependency registry

Pass DepsModule instances to DepsRegistry.from_modules. Each module’s __call__ returns a Deps container; the plan merges them (conflicting keys raise CoreException).

from enum import StrEnum