Mission Control v2 artifact review brief

Bottom line

The first useful v2 slice is not another kanban tweak. It is a real artifact pipeline that makes long outputs readable on phone and laptop without relying on raw markdown attachments.

What this slice should do now

• Store artifacts as durable records in the v2 ledger.
• Save source markdown plus rendered HTML next to the artifact.
• Generate a Discord-friendly summary package with read time, key takeaways, and export links.
• Give Mission Control a clean artifact inbox and a detail reader with rendered markdown.

Delivery contract

1. Summary first in chat.
2. HTML preview for normal reading.
3. PDF-style export for dense documents.
4. Optional preview card image for fast mobile scanning.

Why this matters

Pete's main pain point is review friction, not lack of output. If the system produces a strong brief but ships it as a raw markdown blob, the last mile still fails.

Good agent ops means the work is reviewable, not just technically complete.

Recommended next step

After artifacts, add richer run detail and checkpoint flows so each artifact is tied to a specific execution attempt and review decision.