Guide for application users

PostProject is normally embedded inside another application. It remembers the difference between the media you are working with and the path where one copy currently lives.

That distinction allows an application to recognize moved media using stored file evidence. If several candidates are equally credible, PostProject reports the ambiguity instead of guessing; the application should show the choices and let you confirm one.

Originals, proxies, optimized media, and generated results can all be separate representations of a logical asset. Provenance records explain which inputs and tool produced a result without claiming that the result is cryptographically trusted.

A production file stores identity, representation structure, resource locators, fingerprint evidence, and production metadata. PostProject does not upload this data or contact identifier registries. There is no network service in the current release.

Applications can also run a read-only inventory across machine-local root mappings. Inventory distinguishes media already online from partial or missing representations, changed files, new media, duplicate or ambiguous relink candidates, and roots that are unmapped or unavailable. A disposable sidecar cache can accelerate repeated scans without changing the production file.

The portable production workflow follows a movie, image sequence, and camera package through import, a machine move, verification, inventory, and OTIO/OpenAssetIO resolution.