Outcome
Users can download a completed Run so they can keep, inspect, or share their Results outside
SetScout.
The download should preserve the useful public parts of the Run:
- Search Brief
- Ranked Results
- Requirement Checks
- Evidence Citations and source links
- Known issues
- Result Limitations
It must not include credentials, prompts, internal pipeline logs, stack traces, or other private
implementation details.
Why this is separate
This is intentionally deferred from the first Run View implementation in #6. Download behavior
has its own product and technical decisions and should not delay the core Run experience.
Open design decisions
- Export format: Markdown, JSON, PDF, or a combination
- Whether to include Stage history and Run Activity
- Filename and document structure
- How citations and external links appear in each format
- Whether completed Runs also remain accessible inside the current browser session
- Whether export generation happens in the browser or on the server
Not ready for implementation
Start with a short product-design pass before implementation. This issue records the deferred
need but does not yet prescribe a format or storage model.
Follow-up to #6.
Outcome
Users can download a completed Run so they can keep, inspect, or share their Results outside
SetScout.
The download should preserve the useful public parts of the Run:
It must not include credentials, prompts, internal pipeline logs, stack traces, or other private
implementation details.
Why this is separate
This is intentionally deferred from the first Run View implementation in #6. Download behavior
has its own product and technical decisions and should not delay the core Run experience.
Open design decisions
Not ready for implementation
Start with a short product-design pass before implementation. This issue records the deferred
need but does not yet prescribe a format or storage model.
Follow-up to #6.