Output Formats
One completed file, several formats.
The browser report is the product. The PDF is the durable artifact. The email is a teaser and receipt. CSV/source exports are review material.
BrowserRead the file in the Atlas browser report first.
PDFUse the PDF when you need a portable file for archive or sharing.
CSVUse CSV/source exports to inspect evidence rows and gaps.
EmailEmail confirms readiness and points back to the browser report and artifacts.
Format Ownership
| Format | Role | Rule |
|---|---|---|
| Browser report | Primary reading surface | Must contain What changed, source trail, chart context, risks, catalysts, and open questions. |
| Artifact | Must preserve file identity, timestamp, source ledger, and hashes where available. | |
| CSV/source export | Evidence review | Must expose source rows and gaps without generating new prose on serve. |
| Teaser/receipt | Must not become the full report or a raw link dump. | |
| Saved file | Archive row | Must reopen the same completed research context. |
Serve-Path Rule
Note: Export and email serve paths should materialize an existing completed file. They should not fetch new sources or call a writer model during delivery.