Your brand buys an AI-assisted product film from a production partner in China, then asks for every source file so another team can make next season’s ads. The film combines your product photography, newly generated scenes and an AI clip downloaded from a catalog. One sentence promising ownership of “all AI content” may conceal three different permission histories.
ONCE recommends identifying how each component was acquired before agreeing to a reusable asset handoff. This hypothetical example is not an ONCE client case.
AI appearance does not establish the license
The current Artlist License, checked October 31, 2026, distinguishes catalog Assets from Output created using its AI services. Editing an Asset does not turn it into AI Output; Asset-derived results remain subject to the applicable Asset license.
Its license explanation also treats AI content supplied through AI Explore or the catalog differently from users’ own generations. These are that provider’s contractual categories, not a universal copyright ruling, exclusivity promise or rule for every AI service.
Classify acquisition before promising delivery
ONCE proposes a shot-level source record with four practical routes:
- Supplied material: who provided it, what permission accompanied it, and whether upload, modification and onward delivery are allowed.
- New generation: the service, generation record, input sources and relevant terms.
- Catalog download: the asset identifier, source page, account, acquisition date and applicable license.
- Asset-based processing: the original component and its relationship to the modified shot, with continuing conditions identified.
Mark unresolved provenance for confirmation. “AI” is not a sufficient source description. This record need not expose confidential prompts or account access to unrelated parties; it must make the permission basis checkable.
Existing publication and a future edit are separate questions
For Artlist Assets, the current guidance links project completion and publication to an active subscription. Qualifying existing projects and new projects after expiry are treated differently. The formal license also distinguishes delivering a compliant project to a client from distributing Assets as standalone material. Check the applicable plan, agreement and exceptions rather than relying on a broad summary.
Suppose this quarter’s approved film will become a new packaging advertisement next quarter. Ask separately about continued use of the existing project, creation of the new version, and transfer of components to its editor. A previous production payment does not establish all three permissions.
If the proposed revision falls into an unclear category, seek confirmation from the rights provider using the actual brief. Do not invent a universal rule that a sufficiently short change is exempt, or manufacture a nominal publication to evade a requirement.
Make the next team’s handoff usable
Separate the approved film, independently deliverable material, and third-party components restricted to the relevant project. For restricted components, provide the source and usage record without assuming the underlying file can be shared. The receiving team may need its own permission path or a replacement.
An editing project file is not a license workaround. Where it contains material that cannot be shared independently, agree a compliant handoff: licensing by the next team, replacement, or a project stripped of that component with clear notes. Keep authorized layers separable so a future substitution is technically practical. Separation alone does not expand rights.
Price the intended reuse, not only the generations
Catalog material may suit a defined one-off project. Repeated revisions, regional-team handoffs or a long-lived brand library may justify comparing commissioned production, a more suitable license and replacement of restricted components. None is inherently the cheapest route.
Ask for scope covering acquisition, source checks, permitted handoff preparation and anticipated revisions, with unresolved third-party permissions identified. A production brief should say who will make the next version, not merely who receives today’s export.
For an annual content service, maintaining source records and replacement relationships can support future decisions. That is ONCE service-design analysis, not a measured efficiency or margin claim. Start by asking the supplier to identify what can be delivered, how it can be reused and which components remain conditional.
Source scope: Artlist’s license, license explanation and Studio FAQs were checked October 31, 2026. No rule-change date is inferred. This is evergreen procurement research; scenarios are hypothetical, and actual rights depend on the applicable agreement and rights-holder confirmation. Provenance classification is not a legal ownership determination.
