Media Asset Ingestion and Web Transcoding Orchestration Spec

Role: Lead Media Systems Full-Stack Developer

Context

• Destination Store: {{storage_backend}}
• Ingest Formats: {{supported_codecs}}
• Max Payload: {{max_upload_size_gb}} GB
• Event Transport: {{notification_protocol}}
• Client Concurrency: {{worker_concurrency_limit}}

Task

Author a technical engineering specification for a browser-based media ingest pipeline that manages chunked uploads, pre-flight client-side integrity validation, and real-time transcode progress rendering.

Method

1. Define client-side file inspection using WebAssembly or Web Workers to validate {{supported_codecs}} prior to upload initiation.
2. Construct the chunking, MD5/SHA-256 calculation, and presigned multi-part upload lifecycle to {{storage_backend}}.
3. Establish client-side retry budgets, backoff curves, and pause/resume session persistence via IndexedDB.
4. Design the backend transcode trigger event fired upon multipart assembly completion.
5. Specify the {{notification_protocol}} payload contract for real-time transcode milestones (probe, decode, encode, thumbnailing, packaging).
6. Outline memory management techniques to prevent browser tab crashes while processing files up to {{max_upload_size_gb}} GB.
7. Detail optimistic UI states and progress bar smoothing calculations.

Constraints

• MUST enforce a maximum of {{worker_concurrency_limit}} parallel network chunk transfers.
• MUST NOT hold uncompressed video frames in main-thread JavaScript heap memory.
• Require end-to-end cryptographic integrity verification matching client hashes with object store ETags.
• Provide exhaustive error state tables for dropped WebSocket/SSE connections.

Output format

Produce a technical integration specification containing:

1. Client Upload & Validation Sequence
2. Multipart Storage Protocol & Payload Schemas
3. Real-Time Event Protocol Specs (JSON event payloads)
4. Resilience, Resume & Error Handling Matrix
5. Browser Memory & Thread Safety Guidelines Length: 850-1350 words.

Self-review

• Ensure memory constraints strictly respect {{max_upload_size_gb}} GB limitations.
• Verify {{notification_protocol}} event structures contain actionable error codes.
• Confirm chunking concurrency does not exceed {{worker_concurrency_limit}}.