Proxy file

How it works

The proxy is a different file. It has its own size, hash, and link. Notes on the proxy must be tied back to the master. Replacing the master with the proxy is a failed delivery.

A 200 MB H.264 proxy arrives in minutes. The 18 GB master finishes overnight. Editorial notes timecodes on the proxy. They lock only after the master hash matches.

How it differs

A proxy is not a CDN cache. A cache may hold the real file. A proxy is a different encode.

Approving the proxy in writing can be read as approving the master.

Label the file.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For proxy file, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive proxy file files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.