Remove legacy raw pipeline contracts
This commit is contained in:
@@ -47,8 +47,8 @@ validator set before the runner receives source bytes.
|
||||
| `internal/framework/checkpoint` | Workspace-backed checkpoint loading, recording, and payload serialization. |
|
||||
| `internal/framework/debug` | Workspace-backed framework and LLM debug recording. |
|
||||
|
||||
Framework contracts provide both the production raw stage interfaces and typed
|
||||
artifact, provenance-wrapper, chunk-validator, serialized-validator, and
|
||||
Framework contracts provide typed artifact, provenance-wrapper, chunk-validator,
|
||||
serialized-validator, and
|
||||
typed-validator interfaces. The runner owns handoff provenance, validation
|
||||
sequencing, rejection handling, checkpoint and debug boundaries, and final
|
||||
manifest assembly.
|
||||
@@ -60,15 +60,13 @@ type equality across the lane, and records schema identity in the resolved lane
|
||||
and pipeline digest. Registry entries carry separate option-validation and
|
||||
run-local construction closures. Preparation injects shared dependencies and
|
||||
constructs input, chunk, validators, ordered lanes, and output before source
|
||||
parsing. Production input, chunk, and output modules use strict construction-time
|
||||
option decoding, and the LLM-backed scene chunker retains the injected shared
|
||||
client. The D&D family registers the canonical `dnd/spell-list` codec, typed
|
||||
spell extractor and validators, and kind-specific generic merge and normalize
|
||||
strategies; generic JSON validators use the serialized-validation contract. The
|
||||
runner executes the production D&D lane through private exact-type-checked
|
||||
closures and uses migration-only codec adapters for the existing raw
|
||||
checkpoint, debug, and output envelopes. Legacy raw lanes retain their separate
|
||||
executor while they migrate.
|
||||
parsing. Production modules use strict construction-time option decoding, and
|
||||
LLM-backed modules retain the injected shared client. The D&D family registers
|
||||
the canonical `dnd/spell-list` codec, typed spell extractor and validators, and
|
||||
kind-specific generic merge and normalize strategies; generic JSON validators
|
||||
use the serialized-validation contract. The runner executes lanes through
|
||||
private exact-type-checked closures and serializes artifacts only through their
|
||||
codec at checkpoint, debug, and output boundaries.
|
||||
|
||||
## Production Extensions
|
||||
|
||||
|
||||
Reference in New Issue
Block a user