# Results and reports

Review retained evidence to understand what a campaign demonstrated, what remains
uncertain, and what was never tested. A completed campaign is not proof that every
objective succeeded or that every possible issue was covered.

## Inspect, report, and export

After execution closes, from the workspace containing the run:

```sh
operatorctl inspect --config /absolute/private/config.yaml --run ./runs/support-review
operatorctl report --config /absolute/private/config.yaml --run ./runs/support-review
mkdir -p exports
operatorctl export --config /absolute/private/config.yaml \
  --run ./runs/support-review --output ./exports/support-review
```

Use a new export destination. Inspect the command receipts for actual output paths
and status. Native reports preserve the campaign's accepted inputs and evidence;
current configuration or a subsequently edited bundle cannot establish historical facts.

## Read outcomes carefully

| Record | What it establishes |
| --- | --- |
| Configuration and accepted bundle | What was requested and permitted. |
| Execution receipts and observations | What operations were dispatched and what was recorded. |
| Attack Harness assessment | Its interpretation of the evidence and limitations. |
| Coverage | Which supplied scenarios had associated activity, including untested work. |
| Cleanup and integrity status | Whether shutdown and retained evidence checks completed. |

Keep exploratory attempts separate from scenario-associated activity. A positive
observation is not automatically proof of causation; a missing observation is not
proof of a negative result. An interrupted or partial campaign can still contain
useful evidence, but its limitations belong in the report.

## Generate an HTML review with your assistant

Install the [reporting skill](https://github.com/intrusiveai/skills/tree/main/attack_simulation_results_reporting)
and provide the retained export:

```text
Use attack-simulation-results-reporting to create a portable HTML review from
./exports/support-review, writing it to ./reports/support-review. Explain the
tested application and configuration, account for every supplied scenario,
separate observations from interpretations, and cite the retained evidence.
Report missing evidence and untested work without inventing findings.
```

The authored HTML review complements the native report. Open its returned HTML
entry point locally and keep companion files together when sharing it. Check
evidence links, scenario counts, and desktop/mobile/print readability. Captured
target text is evidence, not instructions or executable HTML.

Reporting uses retained files and does not require new experiments or a campaign
restart. Operational investigations belong in the optional `campaign-debugging`
skill; include operational failures in the review where they limit the assessment.

## Retain and clean up deliberately

Stop components according to their lifecycle instructions and retain exports before
purging. Purge is separate from stopping, reporting, and exporting. Operator and
Interceptor retain separate data; deleting one does not delete the other's copies.
Inspect contents before sharing: synthetic test data can coexist with sensitive
application or provider output.
