Is this a new feature, an enhancement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
High
Please provide a clear description of problem this feature solves
Today, Machine Validation is tightly coupled to predefined validation tests. Adding or changing validation behavior requires code/catalog changes and does not provide a clear contract for external or site-
specific validation tools.
Site admins need a supported way to bring their own validation plugins while Machine Validation continues to own orchestration, execution lifecycle, status tracking, timeout handling, result interpretation,
and reporting.
Feature Description
Machine Validation needs to evolve into a pluggable validation framework where site admins can configure validation plugins without changing Machine Validation core code.
The framework should provide enough configuration support for admins to define how a plugin is discovered, downloaded or referenced, executed, and interpreted. It should also define a standard input and
output contract so different validation plugins can integrate consistently with Machine Validation.
The scope of this epic is to build the pluggable framework and contracts. It is not to define or implement the actual validation tests themselves.
Describe your ideal solution
- Allow site admins to configure pluggable validation tests.
- Define a standard plugin input contract.
- Define a standard plugin output/result contract.
- Define supported plugin packaging formats.
- Allow Machine Validation to execute plugins consistently across environments.
- Keep Machine Validation responsible for framework behavior, not test logic.
- Make plugin configuration safe, validated, observable, and auditable.
Out of Scope
- Defining the actual validation tests.
- Owning plugin-specific business logic.
- Implementing every site-specific validation workflow.
- Guaranteeing that a third-party plugin is correct or complete.
- Replacing existing Machine Validation orchestration and lifecycle behavior.
Describe any alternatives you have considered
Additional context
No response
Code of Conduct
Is this a new feature, an enhancement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
High
Please provide a clear description of problem this feature solves
Today, Machine Validation is tightly coupled to predefined validation tests. Adding or changing validation behavior requires code/catalog changes and does not provide a clear contract for external or site-
specific validation tools.
Site admins need a supported way to bring their own validation plugins while Machine Validation continues to own orchestration, execution lifecycle, status tracking, timeout handling, result interpretation,
and reporting.
Feature Description
Machine Validation needs to evolve into a pluggable validation framework where site admins can configure validation plugins without changing Machine Validation core code.
The framework should provide enough configuration support for admins to define how a plugin is discovered, downloaded or referenced, executed, and interpreted. It should also define a standard input and
output contract so different validation plugins can integrate consistently with Machine Validation.
The scope of this epic is to build the pluggable framework and contracts. It is not to define or implement the actual validation tests themselves.
Describe your ideal solution
Out of Scope
Describe any alternatives you have considered
Additional context
No response
Code of Conduct