validate-output

To validate an output directory, you run an approved validator script with the target directory passed as its first argument. The validator must reside in an approved location alongside its schema to ensure workflow integrity.

When output validation fails, the process returns the specific validator errors and instructs you to fix the issues and rerun the task. This prevents workflows from progressing with incorrect output.

A completion token verifies output integrity by providing the sha256 hash of the validated directory contents upon success. This cryptographic token confirms the output directory passed validation and remains unchanged.

No, you cannot use a validator from any location. The validator must be located alongside its schema and within approved locations only. This constraint enforces a strict validator protocol for secure workflow automation.

You need to provide the target output directory and the validator script path. The validator is invoked with the target directory as its first argument to execute the validation protocol.

Output validation is necessary because it ensures workflows only progress after successful validation. By executing an explicit validator script, it guarantees directory contents meet schema requirements before downstream tasks continue.