# Evidence and results

Start from a study you can access in the selected workspace. The useful result is the material you can inspect, together with its limits. A confident response or a finished execution attempt alone does not establish a scientific conclusion.

## Inspect the research record

1. Read the study description to recover its question and requested deliverable.
2. Open Activity and expand the relevant agent card. Read the hand-in, its source references and any errors.
3. Open Files to browse generated artifacts and attached material. Search or switch between grid and list views when the collection grows.
4. Open Notebook for recorded computation, including code, printed output and standard error where present.
5. Open Review for the available checks and their explanations. Select a stage or check to inspect its details.

For a failed Validation replay, open **Full log** on the rerun card in Activity to see the script's exit status and any recorded standard error.

[![Searcher Grounding Team hand-in identity and Assignment heading](/docs/study-progress-detail.jpg)](/docs/study-progress.jpg)

The detail identifies the hand-in. Open the image for the full assignment and findings in the actual study screenshot.

The example shows a Searcher hand-in. Grounding scoring was unavailable, so this capture is not a passed review or a validated finding.

## Open a final report

When the study has a final report, select **Go to the report** in Activity to open its final hand-in and evidence graph. The action appears only for a finished study with a stored report; unfinished or stopped studies, Workflow runs and older studies without a report do not show it. The local demonstration studies are waiting for scoring, so they do not yet have a finished report. Report access is described from the implementation; it was not verified live for these studies.

## Inspect recorded output files

The DISC-2 demonstration study runs a sampling simulation using explicitly simulated data. Its Files surface contains recorded outputs, including a plot and a CSV. Open a file to inspect it and compare it with the study's stated method and inputs.

[![DISC-2 Files surface with a simulated-data plot and CSV output](/docs/experiment-outputs-detail.jpg)](/docs/experiment-outputs.jpg)

This detail is from the actual study; open the image for the full dashboard view. The files show what was produced from simulated data. DISC-2 is still waiting for unavailable scoring, so the presence of these files does not mean its review gate passed or that the result is a validated finding.

## Check before reusing a result

Follow cited sources and compare them with the claims being made. Check whether an artifact actually exists and whether the recorded analysis corresponds to the question and inputs. Note missing sources, failed computation and unresolved objections in your own interpretation.

Review displays the records available for that study. Older studies may show legacy review history. Read the labels and explanations rather than assuming scores from different review formats are directly comparable.

## Handle missing material

An empty Files or Notebook view can mean the work did not produce that type of record. Read Activity first. A loading error is different: use the retry control and preserve the error if it persists. If review is waiting, inspect the reported blocker.

You are ready to use an output when you can locate it, trace its relevant evidence and explain what remains uncertain. See [scientific stages](/docs/scientific-stages/) for completion and [troubleshooting](/docs/troubleshooting/) for execution problems.
