How to

Create a report

Attach draft or accepted mission-level research, validation, quality, or handoff evidence.

What changes

report writes draft evidence by default. Use --from to import completed Markdown and --accept to validate and accept it for the current flow gate.

When this helps

Research or handoff context needs a durable mission-level artifact.
A quality lead needs to record whole-mission validation or quality evidence.
Work needs validation evidence before closeout.

Run this command

terminal

$sumr mission report SUM-123 --type validation --from validation.md --accept# accepted test evidence

Flags you can use

--type <kind>

Choose research, validation, quality, or handoff for mission-level evidence.

--from <file>

Read evidence from an existing Markdown file instead of writing a template.

--accept

Validate and accept substantive evidence in the same command.

--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

A report template or imported file without --accept remains a draft and does not complete an evidence-driven flow step.
Task submission and structured task reviews satisfy tasks.execute and tasks.review; mission-level reports do not replace those facts.
Whole-mission evidence is ordered: completed tasks, validation, then quality. Research and handoff do not use those prerequisites.
Reports should include exact commands, browser routes, screenshots, or workflow evidence when available.
Validation acceptance requires concrete reproduction and verification evidence, not only a command name or a generated template.