ECC 2.0 Video Suite Production Manifest

Snapshot date: 2026-05-19.

This is the production contract for the ECC 2.0 release video suite. It keeps the public release story, local source inventory, render outputs, and self-eval gate in one place without committing raw footage, private transcript exports, or absolute local paths.

Claim

ECC 2.0 is the harness-native operator system for agentic work.

The videos should prove that claim directly:

• one reusable layer across Claude Code, Codex, OpenCode, Cursor, Gemini, Zed, GitHub Copilot, and terminal workflows;
• reusable skills, rules, hooks, agents, MCP conventions, release gates, and operator workflows;
• ecc2/ as the alpha control-plane/TUI direction, not the whole product;
• AgentShield and supply-chain gates as the enterprise trust layer;
• OSS stays free, with GitHub Sponsors, ECC Tools Pro, and consulting as the funding surface.

Do not frame the launch as a rename, pivot, config pack, or Claude-only package.

Private Inputs

Do not commit raw footage, transcript JSON, or timeline exports.

Operators should point the validator at local media using environment variables:

ECC_VIDEO_SOURCE_ROOT=/path/to/ecc_2_raws \
ECC_VIDEO_RELEASE_SUITE_ROOT=/path/to/ecc_2_release_suite \
npm run release:video-suite -- --format json

ECC_VIDEO_SOURCE_ROOT should contain proof images and may contain an _edited/ subdirectory with edited source clips. ECC_VIDEO_RELEASE_SUITE_ROOT should contain edl/, segments/, renders/, timelines/, and transcripts/.

Source Inventory

These basenames are the required local inputs for the release suite validator.

Deliverables

Primary Launch Video

The rough v1 primary launch assembly is the current spine. It should stay speech-led, with product proof covering jump cuts and older wording.

Required local rough v1 artifacts:

• edl/primary-launch.edl.md
• timelines/primary-launch-v1.timeline.json
• renders/ecc-2-primary-launch-rough-v1.mp4
• renders/ecc-2-primary-launch-rough-v1.captions.srt
• segments/primary-launch-v1/01-structured-context.mp4
• segments/primary-launch-v1/02-agentic-harness-optimization.mp4
• segments/primary-launch-v1/03-not-another-harness.mp4
• segments/primary-launch-v1/04-agentic-ide-surface.mp4
• segments/primary-launch-v1/05-github-app-proof.mp4
• segments/primary-launch-v1/06-security-risk.mp4
• segments/primary-launch-v1/07-agentshield-proof.mp4
• segments/primary-launch-v1/08-oss-paid-model.mp4
• segments/primary-launch-v1/09-close-shipping-system.mp4

Publish-Candidate Outputs

The release validator also expects the current publish-candidate set under renders/publish-candidates/. These are still local review files, not public uploads or committed media.

video-use compatible workflow

Use the same production shape as Video Use while keeping the ECC-specific media stack intact:

1. Treat transcript and timeline data as the editing surface.
2. Keep visual inspection on demand: filmstrips, waveform/timeline composites, or frame samples only at ambiguous cut points.
3. Propose the edit strategy and EDL before rendering.
4. Cut deterministically with FFmpeg.
5. Add proof overlays with Remotion or Manim where product claims need visual evidence.
6. Export the MP4 plus editable timeline and caption state.
7. Run cut-boundary, audio, caption, black-frame, and product-claim self-eval before any upload or social post.

Do not dump frames into the repo. Frame samples used for self-eval belong in the local release suite workspace.

Browser Capture Plan

Use Browser or equivalent desktop capture only for proof footage that must be current on release day:

If a surface is not live, use a local browser capture and label it as local or release-candidate proof. Do not claim marketplace, billing, or official directory availability before evidence exists.

Self-Eval Gate

Run the validator:

ECC_VIDEO_SOURCE_ROOT=/path/to/ecc_2_raws \
ECC_VIDEO_RELEASE_SUITE_ROOT=/path/to/ecc_2_release_suite \
npm run release:video-suite -- --format json

Then manually check the final render for:

• validator self-eval passes for the primary render: 90-150 seconds, at least 1280x720, video stream present, audio stream present, and non-empty output;
• validator self-eval passes for the publish-candidate set: primary MP4 plus captions and five short clips in both wide and vertical formats;
• validator visual QA reports zero detected black-frame segments for every publish-candidate MP4;
• no blank frames or accidental desktop exposure;
• no stale repo name, pivot, rename, or Claude-only framing in captions;
• no captions that rewrite speech into a false claim;
• no stale URLs, old install commands, or pre-rename repository links;
• no internal MRR numbers unless the post explicitly needs them;
• audio continuity across every cut;
• first 10 seconds clearly say what ECC is;
• final CTA routes to repo, sponsor, Pro, or consulting without clutter.

Do Not Publish If

• npm run release:video-suite is not ready for the local source roots.
• The primary launch render is outside the 90-150 second target.
• Captions mention the old repository name.
• Product proof relies on private screens, secrets, customer data, or raw local paths.
• The release URL, npm, plugin, billing, or marketplace claims outrun the evidence in publication-readiness.md.