Artifact Review UX Roadmap

Executive Summary

This roadmap defines UX improvements for reviewing agent-generated artifacts across Discord mobile, Discord desktop, and Mission Control on the web. The core problem is that raw markdown is a poor delivery format on mobile, so the system must package outputs for review rather than shipping plaintext blobs. The phased build covers rendered HTML previews, PDF exports, and a dedicated artifact detail reader in Mission Control.

Goal

Make agent outputs easy to review from:

• Discord mobile
• Mission Control on laptop

The real problem

Raw markdown is a lousy delivery format in Discord. On mobile it is worse. If the output matters, the system should package it for review instead of making Pete wrestle with plaintext.

Design rules

1. Main channel gets summary, not the whole document.
2. Every substantial artifact gets at least one rendered preview path.
3. Mobile review should work even if Mission Control links are inconvenient.
4. Laptop review should feel like a document reader, not a note field.

Recommended artifact package

For markdown-heavy artifacts, generate:

• source.md
• preview.html
• summary.png
• full.pdf
• meta.json

Discord delivery modes

Mode 1: summary + image, default

Use when Pete mainly needs to scan and decide.

Post:

• title
• 3 to 5 bullets
• one-line recommendation
• summary image
• optional Mission Control link

Mode 2: summary + PDF

Use when the document is dense and likely needs full reading on mobile.

Post:

• summary card
• PDF attachment
• short note about what is inside

Mode 3: summary + thread chunks

Use only when Pete explicitly wants the text in Discord.

Rules:

• thread only
• semantic chunking by section
• headings preserved
• each chunk prefixed with part number

Clever options worth testing

Option A: card image generated from markdown headings and key bullets

Pros:

• fastest mobile scan
• works natively in Discord

Cons:

• not enough for long-form reading alone

Option B: rendered HTML served by Mission Control

Pros:

• best reading experience
• easy typography and internal links
• can support version compare later

Cons:

• depends on link accessibility from mobile

Option C: PDF snapshot from HTML

Pros:

• reliable mobile readability
• preserves layout

Cons:

• less skimmable than HTML

Option D: signed or tokenized local links, only if network setup supports it

Pros:

• direct artifact open from Discord

Cons:

• only useful if Pete can actually reach the host from phone
• should be optional, not assumed

Option E: stitched section images for ultra-mobile review

Generate one image per major section or first two pages.

Pros:

• very Discord-native

Cons:

• can get noisy fast

Mission Control artifact reader requirements

• rendered markdown
• sticky TOC
• section anchors
• raw view toggle
• export actions
• version history
• linked task/run/decision context
• review status

Best first implementation

1. HTML preview generation
2. artifact detail page
3. summary image generation
4. PDF export
5. Discord delivery helper

Success criteria

The UX is good enough when Pete can:

• scan a result in Discord mobile in under 30 seconds
• open a readable full version without touching raw markdown
• review the same artifact cleanly on laptop inside Mission Control