Problem
Today the only way to verify a run package outside the benchmark harness is the product's import screen. Evaluation pipelines and CI jobs need the same thing from a shell.
Proposal
stateproof verify run-package.zip --contract compiled-contract.json --out evidence/
Reusing the importer and executeContract unchanged, writing the same JSON and Markdown evidence pack the product exports, and exiting non-zero on FAIL (configurable for NEEDS_REVIEW).
Constraints
- No model call unless a contract is missing and a credential is explicitly supplied.
- The same validation errors as the import screen, field by field.
- Read-only by construction, like everything else.
Problem
Today the only way to verify a run package outside the benchmark harness is the product's import screen. Evaluation pipelines and CI jobs need the same thing from a shell.
Proposal
Reusing the importer and
executeContractunchanged, writing the same JSON and Markdown evidence pack the product exports, and exiting non-zero onFAIL(configurable forNEEDS_REVIEW).Constraints