# Report Analysis Guide

Execution reports explain runtime outcomes. Use reports to answer questions such as “why did this scenario fail?”

## Compiler diagnostics versus runtime outcomes

Compiler diagnostics describe invalid or suspicious Logline source. A scenario can fail even when compiler diagnostics are empty.

Runtime failure usually means the input records did not satisfy required scenario evidence.

## Key fields to inspect

When explaining a report, inspect:

- summary counts
- scenario outcomes
- attempted scenario count
- passed/failed/inconclusive/not-attempted counts
- input record counts
- diagnostics
- attempts
- segment progression
- collector values

## Scenario outcomes

A scenario outcome should be explained in terms of evidence:

- which segment was reached,
- which condition passed or missed,
- which required evidence was missing,
- which records were considered,
- whether attempt classification made the scenario attempted.

## Why a scenario can fail with no diagnostics

No diagnostics can mean the program was valid. It does not mean the log satisfied the scenario.

A scenario may fail because:

- an expected signal transition was missing,
- an event condition was never satisfied,
- a required branch did not complete,
- a repeat count was not fulfilled,
- an essential segment missed,
- the log ended before a candidate completed.

## Good answer style

A good answer should state:

1. the scenario outcome,
2. the specific segment or condition responsible,
3. the relevant observed or missing evidence,
4. whether the problem is in the program, the input log, or just insufficient evidence.

Avoid answering only “there are no diagnostics” when asked why a scenario failed.