How to

Record verification receipts

Import or list bounded structured verification receipts.

What changes

verify records validated verification facts produced by a tool or human. Mission never executes the receipt's command field and does not store raw command output. The central Mission guide's Build structured JSON inputs section shows a valid task-scoped receipt with implementationArtifactHash.

When this helps

After a task-level test, lint, typecheck, build, reproduction, or requirements check finishes.
Before task completion when current passing verification is required.
Before close when whole-mission verification must match the exact current HEAD.

Run this command

terminal

$sumr mission verify record SUM-123 --from task-receipt.json# import task verification$sumr mission verify list SUM-123 --json# inspect receipt history

Flags you can use

--from <receipt.json>

Import a bounded structured JSON verification receipt.

--allow-custom-key

Accept a work key that does not match a configured work-provider prefix. Use only for local or intentionally custom work.

--json

Return a structured JSON envelope for scripts, CI jobs, and AI assistants.

--help, -h

Show the command syntax, supported flags, and examples without changing files.

Keep in mind

Task receipts can remain current when their SHA is an ancestor of the integrated current HEAD; whole-mission receipts require an exact HEAD match.
Receipt history is append-only, while freshness is derived from the plan hash, implementation artifact, Git state, and result.