Checks
Declared output checks
Section titled “Declared output checks”uh verify <mission-id> checks every expected_artifacts entry after command
checks. Legacy expected_outputs.files declarations use the same verification.
Paths resolve inside the effective workspace (the bound sandbox when selected).
Missing, empty, non-regular, unreadable, and workspace-escaping outputs fail.
Directory links cannot redirect these reads outside the workspace.
expected_artifacts: - path: out/data.json - path: out/report.md completion_marker: DONEFiles ending in .json, or explicitly declared with type: json, must parse.
An optional completion_marker must match the last nonblank line exactly after
trimming surrounding whitespace. Thus a required DONE marker does not accept
BLOCKED: .... Parse failures do not copy malformed file contents into findings.
These checks appear in the existing verification.yaml result and can verify
file-only missions without a shell command. Presence, syntax, and a marker do
not prove that claims are correct: retain semantic acceptance criteria and
independent review. These checks are not a filesystem sandbox or a secret scanner.
Documentation checks
Section titled “Documentation checks”find docs -type f | sortExpected: required docs from the handoff are present.
git diff -- README.md docsExpected: changes are intentional and navigable.
Optional later:
markdown-link-check docs/**/*.md README.mdFuture schema checks
Section titled “Future schema checks”uh validate .harness/project.yamluh validate .harness/missions/<id>/mission.yamluh validate .harness/adapters/<adapter>.yamlFuture runtime checks
Section titled “Future runtime checks”uh adapter check hermesuh mission dry-run .harness/missions/<id>/mission.yamluh sandbox inspect <sandbox-id>