Add intra-module pipeline for LLM validation
This commit is contained in:
@@ -313,7 +313,13 @@ These primitives are wired into the production runner and report model. The gram
|
||||
- identical/no-effect rejection
|
||||
- conservative protected glossary-term guard for non-glossary modules
|
||||
|
||||
`internal/framework/runner` executes validator chains in order for each module and applies only validator-approved proposals.
|
||||
`internal/framework/runner` executes module pipelines with deterministic boundaries:
|
||||
- modules still execute serially over the working transcript;
|
||||
- section proposal work is launched promptly and can run concurrently;
|
||||
- section-level validator-chain work starts as section proposals become available (deterministic validators before LLM-backed validators);
|
||||
- proposal-generation and LLM-validator calls can overlap under composed scheduler limits;
|
||||
- approved proposals are still applied once per module after section work settles.
|
||||
|
||||
Validator rejections are reported distinctly from proposal-application skips.
|
||||
|
||||
## Implemented LLM-backed validator infrastructure
|
||||
|
||||
Reference in New Issue
Block a user