A report is not a document the platform writes in one pass. It is a structure of blocks — a section's narrative, a finding, a table, a chart, a diagram, a figure lifted from a source document — each one carrying its own citations and its own review state.
Why blocks
Because a deliverable is reviewed in pieces and revised in pieces. If the security section is signed off and the architecture section is not, that has to be visible — and a change to one finding must not quietly rewrite the paragraph an analyst already accepted.
Review states
| State | Meaning |
|---|---|
| Draft | Produced from this project's evidence. Nobody has read it yet. |
| Reviewed | An analyst read it and accepted it as written. |
| Revised | An analyst read it and changed it. |
| Analyst | A person wrote it from scratch. |
The chrome names the stage of the work, not the technology that typed the first version. What a reader of a diligence report needs to know is whether a person has stood behind a statement yet — and that is what these labels say.
The skeleton
Each review area contributes a section. Within a section, findings are ordered by materiality, tables and figures sit with the finding they support, and evidence appendices are assembled from the citations actually used.
Blocks are built when they are needed
A section's blocks are materialized on read. If you regenerate a section, open it again to see the new blocks rather than a cached older layout — the report view resolves the current content when you view it.
Where the numbers come from
Every figure in a report traces to a source: a page in a document, a range in a spreadsheet, a moment in a transcript, or a measurement from a repository extract. Where a figure comes from an extract, the report states the date the extract was taken, because an "as of" date is part of what makes the number meaningful.