# Preview Media Delivery Guardrails

Use this when sending generated short-form preview videos (Telegram or similar), especially timing-card MP4s that can look identical in mobile previews.

## Problem signal

If the user says the same video was sent multiple times, do not immediately resend media. Verify the artifacts and switch to labeled delivery.

## Required delivery pattern

Before sending multiple preview MP4s:

1. Verify each artifact is distinct:
   - candidate ID / title;
   - absolute path;
   - duration via ffprobe or stored render metadata;
   - checksum/hash when feasible.
2. Send an indexed text summary first:
   - `1. <title> — <candidate_id> — <duration> — <short hash>`;
   - include what differs conceptually, not only file paths.
3. Attach media only when each attachment has a clear label/caption in the surrounding message.
4. If the previews are visually similar timing cards, prefer sending one sample MP4 plus the indexed list, then ask/continue to the next pipeline step rather than spamming three near-identical-looking videos.
5. If the user complains, acknowledge the delivery issue, stop resending, verify uniqueness, and continue building the pipeline.

## What to avoid

- Do not send several unlabeled `MEDIA:` attachments in one message when their thumbnails are likely identical.
- Do not rely on paths alone as human-readable differentiation.
- Do not claim files are the same or different without checking hashes/metadata when tooling is available.

## Good compact format

```text
Preview artifacts verified:
1. AI Automations Quietly Rot — 38.0s — sha256: 032ed16e…
2. Prompt vs System — 35.0s — sha256: 47023552…
3. AI Notes Become Useless — 34.0s — sha256: 55f27f60…

Sending only #1 as media now; the others are ready but visually similar timing cards.
```