Repository navigation
Assessment: Make L1 and L2 optional #1326
Description
Is your feature request related to a problem?
Currently, an ASSESSMENT config must include an assessment block, preventing pre-filter-only runs which could limit flexibility in processing.
Describe the solution you'd like
- Make both
assessmentandpre_filtersoptional, with at least one required (422 at config save). - Allow pre-filter-only runs to return
output.assessment = nullwith the verdict inoutput.pre_filter. - Ensure pipeline build, finalize, and provider/model checks accommodate a missing assessment stage.
- Maintain compatibility with existing config versions that always include
assessment.
Original issue
Context
An ASSESSMENT config must carry an assessment block today, so a pre-filter-only run is not possible.
Scope
assessmentandpre_filtersboth optional; at least one required (422 at config save).- A pre-filter-only run returns
output.assessment = nullwith the verdict inoutput.pre_filter. - Pipeline build, finalize and the provider/model checks handle a missing assessment stage.
- Existing config versions stay valid (they always have
assessment).
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
[-]Assessment: Make pre-filter and assessment optional in the config[/-][+]Assessment: Allow pre-filter-only runs[/+][-]Assessment: Allow pre-filter-only runs[/-][+]Assessment: Make L1 and L2 optional[/+]feat(assessment): Make pre-filter and assessment optional in the conf…
feat(assessment): Make pre-filter and assessment optional in the conf…
feat(assessment): Make pre-filter and assessment optional in the conf…
feat(assessment): Make pre-filter and assessment optional in the conf…
feat(assessment): Make pre-filter and assessment optional in the conf…