Your first audit session

1. Read a test in Trace

1. 1Pick a test in the list on the left. Failures show first in the run panel.
2. 2Click any call in the call trace: the source panel jumps to the line it ran, with its arguments and return value.
3. 3Switch to Call graph to see the same test as a graph of contracts, or open Ask AI on a call to have it explained.

2. Map the contract in Atlas

1. 1Open Atlas. Graph shows every function with what it reads, writes, calls and emits.
2. 2Paths walks one function step by step, with replay.
3. 3The numbers in the header (coverage, untested, findings) open the summary.

3. Triage findings

The findings tray at the bottom of Atlas merges Slither, Aderyn and Luora's own checks into one finding per issue. Mark each one Confirmed or False positive, then download the confirmed ones as a Markdown report.

4. Pin intended behaviour with a scenario

1. 1Open Scenarios (Atlas, or the Scenario view in Trace).
2. 2Wire Actor → Call → Expect revert or Assert, or start from a template.
3. 3Press Run to check it against the run's values, then Export .t.sol (or Generate test) and add it to your suite.

A failing assertion is a finding for you to review, not an attack. Scenarios only use the Lab's cards: actors, amounts, calls, expected reverts, asserts and snapshots.