validate

Validate AEP artifacts by running a parallel Generator/Evaluator pattern that identifies design gaps and implementation issues, returning a consolidated validation report with required fixes and severity levels to ensure artifact correctness before dispatch.

Checking design specs and code for inconsistencies is handled by spawning an Evaluator and Protocol Checker to detect documentation gaps and downstream compatibility issues, producing a consolidated findings report appended to the artifact's changelog.

You can validate product-context.yaml files using Product Context Validation mode, which automatically detects the artifact type and runs consistency checks to outline required fixes with severity tracking.

Parallel agent validation works by spawning a Generator for dry-run testing and an Evaluator for consistency checking simultaneously, optionally adding a Protocol Checker for downstream compatibility to produce a consolidated findings report.

Artifact validation is needed after running envision, design, or build phases, or whenever you need to validate product-context, design specs, code, or documents to converge on correct artifacts before dispatch.

The validation report supports traceability and rollback by appending a changelog entry with outlined fixes and severity levels directly to the artifact, ensuring all validation findings remain documented and reversible.