Following a finished creative back to its required inputs

Start with the version the caller expects#

A current-release pointer helps find media, but a caller may need the version it already reviewed. Retrieval resolves the expected path inside the local root, compares the manifest hash with the registry entry, and checks identity, version and canonical location.

The caller can also supply an independent manifest hash. That pin lets retrieval reject a different release even when the mutable registry now points to it. The hash identifies content; it doesn't authenticate the person who approved it.

The output is the end of an edit chain#

The validator checks the size and hash of every listed file, then checks the relationships between them. Edit steps must reference known assets and form a contiguous sequence. Technical and final semantic reviews must name the selected output, so a passing review for another file can't satisfy its checks.

An output-to-input map lets the validator walk from the final creative through its required sources. A visited set prevents repeated traversal. If a required input fails, advertising readiness is blocked; selecting one creative also doesn't excuse broken inventory elsewhere.

Byte integrity and review answer different questions#

Readiness also needs an allowed semantic state, recorded scope for restricted use and compatible resolutions for blocking claims. An unassessed creative stays unassessed even when every checksum matches. The CLI checks those records; it doesn't watch the video or establish legal permission.

The source includes in-memory probes for invalid manifest combinations. Independent synthetic fixtures and atomic release promotion remain open work, and the records are still editable. No manifests, media checks or probes were run for this note.