32 lines
1.5 KiB
Markdown
32 lines
1.5 KiB
Markdown
# Validation Roadmap
|
|
|
|
The first-class raw-output validation system is implemented. Current behavior is
|
|
documented outside roadmap files, especially in [Configuration](../config.md),
|
|
[CLI Reference](../cli.md), [Pipeline Internals](../internal/pipeline.md), and
|
|
[JSON Output](../integrations/json-output.md).
|
|
|
|
Implemented behavior includes:
|
|
|
|
- a single raw module-output validator contract for chunk, extract, merge, and
|
|
normalize outputs;
|
|
- validator specs with deterministic and LLM-backed execution classes;
|
|
- central production validator registration and default chain mappings;
|
|
- stage-local config overrides that distinguish omitted, explicit empty, and
|
|
explicit non-empty validator chains;
|
|
- manifest provenance for resolved validator chains;
|
|
- generic JSON validators and D&D spell validators under `internal/validators`;
|
|
- production defaults for the `dnd/spells` extractor.
|
|
|
|
## Future Work
|
|
|
|
- Add production LLM-backed validators when there is a concrete review policy
|
|
that benefits from model judgment.
|
|
- Add validator diagnostics and timing summaries if operators need more detail
|
|
than `manifest.json`, `rejected.json`, and `warnings.json` provide.
|
|
- Add media-type validators for non-JSON module outputs when such modules are
|
|
introduced.
|
|
- Add compatibility metadata only if real deployments need config-time
|
|
enforcement that a validator is suitable for a specific stage or module.
|
|
- Add batching or context-window controls for LLM-backed validators if validator
|
|
inputs become large enough to require them.
|