Build an asset provenance register before the environment moves

Provenance is an operating record

An environment package may contain original models, scans, textures, decals, reference imagery, purchased elements, client-supplied files, sample assets, and temporary placeholders. When that mix is invisible, a technical handoff becomes a release risk and a reshoot risk. A provenance register does not decide rights or grant permission. It gives the production enough facts and questions to direct the right item to the right owner before the asset is embedded in dozens of scene files.

OpenUSD’s Asset Resolver API documentation is useful evidence for the general problem: asset identifiers and the resolved asset locations are distinct concepts in a pipeline. Atlas’s register applies the same discipline in plain production language. Record both the identifier the scene uses and the source or package from which the production obtained it; do not assume a filename alone carries provenance.

Use one row per reusable source item

Do not make the register a catalogue of every generated cache or proxy. Start one row for each reusable input, then link derivatives to its parent. Give it a stable asset ID, a readable description, source/creator or supplier as supplied, acquisition route, project location, version or hash if available, stated usage information, an owner, and an open-question field. The stated usage field should quote or link the actual source terms or internal record; it should not translate them into a legal conclusion.

Track environment state separately

Epic’s Level Snapshots documentation notes that snapshots save actor and component state but not changes to assets themselves. That is why a stage-state list cannot replace a provenance register. A snapshot can restore a light position while the texture, model, license record, or source file has changed elsewhere. Keep the asset ID and the environment revision in the shot or stage record together, but do not merge their responsibilities.

Atlas proposed review cadence

Open the register at concept intake, then revisit it at first package delivery, at the stage test, and before any release decision. Mark an item “pending owner review” rather than silently replacing it with an assertion. If an asset is only visual reference and is not planned for output, say so; if its function changes into a visible in-camera background, update the row.

Illustrative: a city scene uses an original building model, a licensed texture pack, a client-provided logo image, and a temporary photograph used to guide lighting. Four rows make four different conversations possible. The register can say the photo is reference-only and still show the artist where it entered the work. It cannot say the photo is cleared.

• Keep source identifiers, resolved locations, and scene versions distinct.
• Link evidence rather than paraphrasing terms into a verdict.
• Assign open questions to a named production owner.
• Record when a placeholder becomes a visible production asset.