When an answer should become a file

Genesis Evo separates quick guidance from heavier delivery. A request that needs layout, export or later retrieval can continue as a document or artifact instead of becoming an endless chat reply.

The outcome this serves

Receive a designed report, reusable file or preview when the value depends on structure, visual hierarchy and future access rather than raw prose alone.

Start with a verifiable request

Turn these notes into a designed PDF and verify its rendered pages and delivery receipt.

Completion evidence
The interface must show the genuinely completed result; external, paid, delayed or downloadable delivery must also expose the relevant runtime evidence or receipt.
Failure state
A refusal, boundary or error must remain visible and may not be labelled complete; failed delivery may not be charged as success.
Public capability basis
document.foundry library.workspace notification.delivery · Open the live capability and evidence registry
Take this request to Genesis Evo

How the request moves

  1. Choose the delivery contract

    EVO determines whether the request needs a short answer, designed report, table, preview, media asset or workspace package.

  2. Render and inspect

    File-ready work is checked for layout, readability, completeness and format-specific failure before release.

  3. Attach a delivery trail

    Eligible outputs return through Library and the notification center with preview, download and provenance information.

What you receive

  • Designed PDF-style reports and document artifacts
  • Previewable or downloadable account assets
  • A notification that names the topic and result instead of a context-free completion message

What EVO will not pretend

  • A document request is not complete until the file exists and can be retrieved.
  • Formats differ in preview and export support.
  • A delivery receipt describes the run; it is not an external certification of the content.

Common questions

Will every long answer become a file?
No. EVO should stay concise unless the user asks for depth or the task clearly needs a structured deliverable.
Can I retrieve it later?
Eligible artifacts remain account-bound in Library or Workspace and can surface through a contextual notification.