Email, PDF, CSV
Delivery should confirm a file, not create a second product.
Email is a teaser and receipt. PDF is the durable artifact. CSV/source exports support audit. All of them should point back to the same browser report.
EmailShort, readable, and linked back to the file.
PDFDurable report with source ledger and file identity.
CSVEvidence rows, source metadata, and gaps for review.
ParityNo format should silently drift from the completed report context.
Delivery Contract
- Email announces that the report artifact is ready.
- Email does not dump a full source ledger.
- PDF contains the durable source ledger and report metadata.
- CSV/source export is for evidence review, not narrative replacement.
- Opening or exporting a saved file does not consume a fresh run.
Artifact Integrity
Note: The delivery path should reuse the completed file and cached material. It should not call writers or source fetchers while serving email, PDF, or CSV.