Validation commands
A validation command must prove the task result while bounding its working directory, runtime, file access, and exposure of secrets. The current default timeout is 60 seconds and the maximum accepted timeout is 120 seconds.
Command requirements
- Use an explicit executable and arguments instead of interpolating untrusted text into a shell.
- Fix the working directory and read only the configuration and dependencies required for validation.
- Do not print tokens, private keys, or complete environment variables in arguments, output, or diagnostics.
- Preserve exit status together with assertions, file diffs, or artifact checks.
- Review any test that writes databases, publishes artifacts, or calls production services separately.
Platform isolation
Linux can use namespaces to isolate networking, hide credential directories, and expose a read-only filesystem. Windows and macOS do not receive equivalent namespace protection and use weaker process and path hardening. Cross-platform reviews must not describe all three as equally strong sandboxes.
Validation record
Retain at least:
command / arguments
working directory
platform and versions
timeout
exit status
key assertions and redacted output
touched files or external effects
Failure handling
Treat timeouts, signal termination, and missing output as failures rather than converting them to success. A command changed by redaction must not be executed or used for promotion because it is no longer the command that was reviewed.
Related pages
EvoX Docs · Security · Execution boundaries