Prepare pipelines before source execution
This commit is contained in:
@@ -19,10 +19,15 @@ validator chains and prompt asset collection.
|
||||
|
||||
Production extract, merge, normalize, and validator packages currently use the
|
||||
explicit legacy raw registration APIs. Typed registration is framework-ready,
|
||||
but no production artifact kind or codec is registered yet.
|
||||
but no production artifact kind or codec is registered yet. All selected
|
||||
production implementations are constructed during pipeline preparation through
|
||||
temporary adapters around their existing zero-argument constructors. Their raw
|
||||
option maps and LLM clients remain operation inputs until each implementation
|
||||
migrates to its construction-owned decoder and injected dependencies.
|
||||
|
||||
Specs expose capability and execution metadata without constructing an
|
||||
implementation. Chunk, extract, merge, and normalize modules that accept
|
||||
implementation. Registry entries separately expose option validation and
|
||||
run-local construction. Chunk, extract, merge, and normalize modules that accept
|
||||
auxiliary material declare identical reference slots from both
|
||||
`ReferenceSlots()` and `ModuleSpec().ReferenceSlots`; registration tests enforce
|
||||
that agreement. Runtime delivery uses the corresponding stage request's
|
||||
|
||||
Reference in New Issue
Block a user