Open this lesson in your favourite AI. It'll walk you through the why, explain the demo, and quiz you on the try-it list.
Audit reports from Trail of Bits, OpenZeppelin, Spearbit, Cantina, Code4rena are the highest-density technical writing in DeFi. Senior auditors read them not to find bugs the team missed, but to learn new bug classes and see how peers describe risk. The skill is in the cross-reading: same protocol, two reports, find what one auditor saw and the other didn't.
A typical report's anatomy: severity matrix (Critical/High/Medium/Low/Informational), per-finding sections (description, impact, recommendation, response), executive summary. The Critical findings are usually obvious in retrospect; reading WHY they were missed in pre-audit dev is the lesson.
Use these three in order. Each builds on the one before.
In one paragraph, describe an audit report's structure and audience.
Walk me through reading a Critical finding from Trail of Bits.
Pick two reports on the same protocol; identify a finding one auditor saw and the other missed.