Riven Deliverables
LiveTurns model output into real files: documents, spreadsheets, slides, and PDFs, stored with a stable link and a retention policy.
A lot of useful work ends as a file someone else has to open. Deliverables is the service that renders output into real formats and stores it, so a Computer run can end with a document rather than a wall of text to copy.
Formats#
| Kind | Formats | Typical source |
|---|---|---|
| Documents | PDF, DOCX, Markdown, HTML | Reports, memos, summaries |
| Spreadsheets | XLSX, CSV | Extracted tables, financial models, catalog exports |
| Presentations | PPTX, PDF | Briefings and decks |
| Data | JSON, JSONL | Structured extraction for downstream systems |
Lifecycle#
- A surface or task requests a deliverable, supplying content and a target format.
- The file is rendered — templated where the tenant has branding configured.
- It is stored tenant-scoped and addressed by a stable URL that survives regeneration.
- Access is checked on every read against the requesting session; links are not capability tokens by default.
- Retention follows the tenant policy — kept, expired, or held under legal hold.
Publishing versus delivering#
Deliverables produces a *file*; Riven Pages produces a *page*. Send a PDF to someone who needs to file it; send a page to someone who needs to read it and expects it to stay current. The two compose — a page can offer its deliverable as a download.
Application installers and desktop builds are a different concern and are served by Riven Relay, not Deliverables.