# Prooflane product-media capture plan

The product pages intentionally ship without fabricated CLI recordings. Each page currently renders assets/demo-pending.svg, an inline planned transcript, and a visible “recording pending” label. Replace a placeholder only after the corresponding workflow is implemented and the capture below can be reproduced from repository fixtures.

manifest.json is the source of truth for media status, output paths, commands, fixtures, and required assertions. A ready entry must have every listed artifact present. Until then, keep its status pending and do not add a source element to the page’s video.

## Published screenshot set

The current Security and RAG pages use publication copies only:

- `report-attack-graph-redacted.png` removes the connected target and third-party model.
- `report-sandbox-breakout-redacted.png` removes the third-party model, tool identifier, and local resource URIs.
- `report-model-extraction-redacted.png` removes connected tool identifiers.
- `report-prompt-sandwich-redacted.png` removes the third-party model and synthetic canary.
- `report-rag-history-redacted.png` removes every third-party model identifier.
- `reports/security-surface-sample.html` is the full deterministic scan report;
  its target, tool, argument, canary, and third-party identifiers are replaced
  with explicit publication-safe labels.

Redactions are rendered into the image pixels and cannot be revealed with CSS,
the browser inspector, or image metadata. Do not reference the original desktop
captures or the unredacted `rag.jpg` from a public page.

## Capture standard

1. Start from a clean local build and record the commit SHA in the evidence JSON.
2. Use only seeded synthetic fixtures. Do not use customer data, production tokens, provider credentials, or live destructive targets.
3. Prefer a deterministic local provider/MCP fixture. If a hosted model is required, pin the provider route, record the model identifier, and redact request identifiers.
4. Fix the terminal viewport to 120 columns × 32 rows, use the repository’s documented Node version, disable shell-history expansion, and set a stable prompt such as $.
5. Run the manifest’s setup and demo commands without manually altering output. A deliberate failure must be generated by its named fixture, not edited into the video.
6. Capture at 1440×900 or higher, 30 fps. Export a visually lossless master first.
7. Encode WebM as VP9 and MP4 as H.264 High profile with yuv420p and fast-start. Generate a 1280×720 WebP or PNG poster from a representative real frame.
8. Keep each loop between 30 and 60 seconds. Avoid rapid flashes, animated cursor trails, and time compression that makes commands unreadable.
9. Produce a WebVTT caption file and a plain-text transcript. Silent recordings still require a transcript describing commands and visible result changes.
10. Generate graphs and screenshots from the exact JSON evidence produced during the recording. Never redraw numbers by hand.
11. Run the privacy checklist below and then update manifest.json to ready.
12. Add WebM first and MP4 second inside the corresponding video, add the captions track, replace the poster, and keep the text transcript link.

## Privacy and authenticity checklist

- No API key, bearer token, cookie, authorization header, email, local username, absolute home path, customer name, or provider request ID is visible.
- Canaries and attack strings are synthetic and safe to publish.
- Security demonstrations target only the repository-owned fixture.
- Every displayed score and graph can be regenerated from the checked-in demo evidence.
- Illustrative UI remains labeled illustrative; measured fixture output is labeled demo evidence.
- The page disclaimer does not imply certification, guaranteed security, guaranteed model quality, or production performance.
- Each video remains usable with reduced motion, paused playback, captions, a poster, and a transcript.

## Proposed artifact layout

    site/assets/videos/<demo>.webm
    site/assets/videos/<demo>.mp4
    site/assets/videos/<demo>.vtt
    site/assets/posters/<demo>.webp
    site/assets/transcripts/<demo>.txt
    site/assets/reports/<demo>.json
    site/assets/reports/<demo>.html
    site/assets/graphs/<demo>-*.svg

The directories are created when the first authentic artifact exists; empty or invented media is not checked in.

## Verification

Run python3 site/media/validate_site.py before publishing. The validator checks local links, required metadata, video fallback state, sitemap coverage, and manifest consistency. It does not certify the factual accuracy of a product claim; the capture reviewer must do that against the evidence JSON.
