Configuration and extensions
RAGLight 4 has no global configuration singleton. Applications either inject ready component instances or build them from an explicitPipelineConfig and
IntegrationRegistries value.
Direct dependency injection
Direct injection is the primary API and is the best choice for application code, notebooks, and tests.Optional extras
Extras compose:
Registry-backed construction
Registries are useful when component selection comes from JSON or TOML. Built-in registries contain lazy references, so inspecting names does not import every provider SDK.PipelineConfig.from_file() supports .toml and .json. The serialized
component sections are llm, embeddings, vector_store, and optional
reranker. Provider-specific options remain owned by the selected factory.
Register a custom component
Credentials and environment variables
Provider adapters read conventional environment variables when an explicit key is not supplied:.env file or configure global logging; those are
application responsibilities.
Validation behavior
top_kmust be greater than zero.- Unknown serialized fields are rejected.
- Duplicate registry names require
replace=True. - Missing optional dependencies produce an error naming the required extra.
- The vector-store embedding model is injected by the pipeline and cannot be overridden in serialized options.