Skip to main content

Submitting evidence

Select runs and explain how they support a requirement.

Use a submission to present recorded runs as evidence for one requirement. Explain the results so someone who did not run the experiments can assess them.

Create a draft#

For the quantized classifier, submit the accuracy evaluation and latency profile together. They answer the two checks on the same requirement.

Open either run and select Submit as evidence.

  1. Use Add run to include other results for the same model.
  2. Choose the requirement the runs support.
  3. Inspect the check results.
  4. Select Create draft. You can still change the runs in the draft.

Explain the evidence#

Use the Summary to explain the decision behind the evidence: why you chose this approach, which alternatives you considered, and what tradeoffs you accepted. Link to comparison runs or reports that support the reasoning.

A summary for an INT8 versus FP16 comparison might read:

FP16 gave slightly higher accuracy but exceeded the latency budget. We chose INT8 because the small accuracy loss was acceptable for this use case. We kept the same dataset and preprocessing to compare the two fairly.

Record observations and decisions in each run’s Description as you work, including approaches you ruled out and why. At submission time, draw on those notes to explain the conclusion across the selected runs.

Select Save to keep your summary before opening the draft for review.

Inspect the checks#

The draft evaluates its selected runs against the current checks. Expand a check to compare its observed and expected values. Open a run to inspect the settings or artifacts behind the result. Use View checks to open the requirement’s check configuration.

The latency check evaluates the profile run; the accuracy check evaluates the evaluation run.

If a result is unexpected, see Checks.

Open for review#

A draft stays editable until you submit it. Save your summary and inspect the checks. Choose a Reviewer to assign the review to a teammate, or leave it unassigned.

Use Summary (1) to explain your choice and Reviewer (2) to assign the review. Select Submit for review (3) and confirm.

If the Hub asks you to refresh, select Refresh and inspect the updated results before submitting again.

Submitting saves a numbered revision of the requirement details, evidence references, summary, checks, and evaluation results. This record stays fixed; links to source runs open their current contents.

The submission moves to In review. Share its page with the reviewer, who can accept it or request changes.

Revise a submission#

Read the reviewer’s feedback in Overview, or open Conversation to see the review history. As the author, select Convert to draft and confirm to update the evidence or summary. This pauses the review until you submit again.

Address the feedback and explain what changed. Save the summary, inspect the updated checks in the draft, then Submit for review again. This creates another numbered revision in the same submission.

Use the revision selector to revisit earlier evidence and decisions. The latest changes-requested feedback remains visible while you work on the draft.

Next steps#