Use Case 3.2
The Use Case category captures the context in which AI use is being proposed. It is not focused on the tool in the abstract, but on the intended use of AI in a particular business and workflow setting. This category is especially important because governance decisions are often use-dependent. The same capability may be treated differently depending on the project visibility, production function, input assets, output role, and intended benefit.
Use Case 3.2
Business Context 3.2.1
Business Context describes the organizational and production setting in which the AI use would occur. It helps situate the proposed use within the practicality that shape governance decisions.
Note This subcategory matters because the center of an approval decision is often an evaluation of the anticipated benefit relative to the relevant risks, and those risks are highly dependent on the business context in which the AI use is proposed.
Use Case 3.2 /Business Context 3.2.1
Project Visibility
The visibility of the project or activity in which the approved AI use would occur.
Examples internal testing · public visibility
Use Case 3.2 /Business Context 3.2.1
Release and Legal Status of Media Content
The release and legal status of the media content involved in the use in either inputs or outputs.
Examples public-domain material · pre-release concept art image with copyrighted character · storyboard image with trademarked product · audio with licensed and likeness-protected voice
Note Sub-categories Inputs and Outputs in Section 3.2.3 and 3.2.4 can be used to be more precise about the release and legal status.
Use Case 3.2 /Business Context 3.2.1
Commercial Nature
The commercial nature of the project or activity.
Examples commercial release · other commercial use (for example marketing or promotion) · non-commercial use such as demonstration
Use Case 3.2 /Business Context 3.2.1
Business Benefit
The organizational or production value sought from the use.
Examples accelerating localization · improving restoration quality · supporting creative exploration · improving talent or crew safety · evaluating tool fit
Use Case 3.2 /Business Context 3.2.1
Use Case Maturity
How mature or speculative the proposed use is.
Examples engineering effort · short-term research · long-term research
Use Case 3.2 /Business Context 3.2.1
Stakeholder Function
The production function or department in which the approved AI use applies.
Examples previz · VFX · sound · localization · archive · marketing
Use Case 3.2 /Business Context 3.2.1
Primary User
The profile of the primary user of the approved AI.
Examples a servicing vendor · a technologist within a department · a creative artist
Use Case 3.2
Approval Context 3.2.2
Approval Context describes what is being put forward for approval and what bounded use is being requested. Parts of it may be used to communicate studio guidelines for production teams and servicing vendors.
Note Note that if the Approval Subject is AI Fine-Tuning Workflow, then the rest of the fields in this subcategory as well as the fields in the Inputs and Output sub-categories refer to the conditions around the use of AI after it is fine-tuned.
Note Overall, this subcategory recognizes that approvals may differ across studios and scenarios, and that many groups may be involved, including technologists, production leadership, legal, compliance, and creative stakeholders. This subcategory helps annotate precisely what is being requested so the relevant stakeholders can evaluate it.
Use Case 3.2 /Approval Context 3.2.2
Approval Subject
What is being submitted for approval.
Examples AI Tool · AI Model · AI Workflow · AI Fine-Tuning Workflow
Note If the intended use is AI Workflow, this field includes details about the workflow stages. If the intended use is AI Fine-Tuning Workflow, this field includes details about the fine-tuning approach as well as how the fine-tuned AI is intended to be used.
Use Case 3.2 /Approval Context 3.2.2
Proposed Use
The bounded set of uses being requested.
Examples fixed-frame restoration only · metadata tagging only · voice cloning for narrowly defined circumstances · internal previz only
Use Case 3.2 /Approval Context 3.2.2
Output Reviews
The reviews that may be needed for output assets created using the approved AI or fine-tuned AI.
Examples technical review only · creative review in rare cases · creative review required · compliance check
Use Case 3.2 /Approval Context 3.2.2
Tool(s) in Scope
The tool or tools brought inside the approval request scope.
Note The Tool category described in section 3.3 can be used to express the specifics of the tools.
Use Case 3.2 /Approval Context 3.2.2
Tool Capabilities in Scope
The capability or capabilities brought inside the approval request scope.
Examples upscaling · voice cloning · inpainting · script breakdown · full tool
Note Capabilities can be expressed using the Tool Capability category described in section 3.6.
Use Case 3.2 /Approval Context 3.2.2
AI in Scope
The AI Models and their provenance relevant for processing the approval.
Note The AI Provenance category described in section 3.4 can be used to express the specifics.
Use Case 3.2 /Approval Context 3.2.2
AI Interaction
How the Primary User (3.2.1) intends to interface with AI directly.
Example the video generation capability offers conditional inputs; we intend to guide the capability using text prompt, depth map, start frame, end frame, and camera poses expressed using DCT-based tokens, and iterate to derive precise video rendering and camera movement
Note The Creative Controllability subcategory described in section 3.6.2 characterizes the controls that a tool capability exposes. AI Interaction, here, describes how the user intends to use those controls.
Use Case 3.2 /Approval Context 3.2.2
Workflow Provenance Tracking
Describes the measures that the Primary User (3.2.1) intends to take to record the workflow and asset provenance, where such provenance will be stored (embedded in assets, captured in specific production facility, or both), how sensitive aspects of the workflow such as critical story lines are managed, and if cryptographic measures will be used for ensuring records are tamper-evident.
Note Provenance may include prompts, seeds, nature and degree of human contributions, AI tools and capabilities used, workflow configurations, and inputs and outputs from the workflow.
Use Case 3.2
Inputs 3.2.3
Inputs describes the types of media content provided to the approved AI or fine-tuned AI.
Note Production guidelines can also use this subcategory to communicate how AI is expected to be used while the workflows can document the inputs they supply to AI.
Note Input characterization is often essential because the risk profile of a use case depends heavily on what material enters the workflow. The same tool capability may be treated very differently depending on whether it is operating with public-domain material, pre-release concept art image with copyrighted character, storyboard image with trademarked product, or audio with licensed and likeness-protected voice.
Use Case 3.2 /Inputs 3.2.3
Input Types
The kinds of media content or material that enters the workflow.
Examples storyboard · concept art · script · audio dialogue · music · on-set plate · 3D · metadata · embeddings · point cloud data
Use Case 3.2 /Inputs 3.2.3
Release Status
The release status of content if in-house.
Examples pre-release · released · current production
Use Case 3.2 /Inputs 3.2.3
Legal Status
The legal position associated with the input content or elements of the input content.
Examples copyrighted · trademarked · patented · confidential · likeness-protected · licensed
Use Case 3.2 /Inputs 3.2.3
Legal Subject
The specific element of the input content that has legal status.
Examples product · character · voice · image
Use Case 3.2
Outputs 3.2.4
Outputs describes the media content that is produced by the approved AI or fine-tuned AI and the downstream roles such content may play.
Note This subcategory helps distinguish between supportive outputs that remain internal and outputs that may affect final media, audience experience, and related considerations.
Use Case 3.2 /Outputs 3.2.4
Output Types
The kinds of media content that is produced.
Examples concept art · storyboard · background plate · CG asset · synthetic voice track · proxy render · metadata · embeddings
Use Case 3.2 /Outputs 3.2.4
Output Novelty
Whether the output is a mere extraction of information from inputs or includes newly created elements or media.
Examples information extraction · modality conversion · simple transformation · correction · creative modification · guided creation
Note Output Novelty can be expressed using these classes: information extraction, modality conversion, simple transformation, correction, creative modification, or guided creation. See Tool Capability category for more information on Output Novelty.
Use Case 3.2 /Outputs 3.2.4
Intended Output Role
The role the output is expected to play when produced.
Examples non-media assets (like a report or summary, script breakdown, metadata tags) · working / WIP media asset
Use Case 3.2 /Outputs 3.2.4
Final Use Potential
Whether the output is likely to remain internal and supportive or may cross into final media.
Examples none · layered with other assets for final use · direct final use (with minor transformations)
Use Case 3.2 /Outputs 3.2.4
Talent Likeness
How talent voice, image, gait, aesthetics, or tag lines are manifested in outputs.
Examples none · voice · aesthetics · performance-related manifestations
Use Case 3.2 /Outputs 3.2.4
Brand Perception
How a brand is manifested in the outputs, where relevant.
Examples none · original brand in emotional context · damaged item
Note Brand, in this context, means a product or a service with public perception or reputation and most likely has a legal status (e.g., an associated trade name or mark).
Use Case 3.2 /Outputs 3.2.4
Provenance
If, what, and how the asset genealogy is preserved.
Examples visible/invisible watermark · cryptographic/plain-form embedded metadata · storage in specific production facility
Note Genealogy includes workflow inputs, prompts, configurations, outputs, AI tools and capabilities used, and so on.
Note This characterization should align with the Workflow Provenance Tracking plan stated in the Approval Context (3.2.2).
Tool 3.3
The Tool category captures information about the AI solution provider and how the relevant tool is packaged for use. In this Framework, a tool may be an AI model or a product, service, platform, plug-in, API, workflow environment. A tool offers one or more capabilities for use in media creation.
Tool 3.3
Tool Vendor Profile 3.3.1
Tool Vendor Profile describes the organization providing the tool or AI model.
Note This subcategory helps provide organizational context that may matter to customers when evaluating vendor documentation or situating the tool within broader procurement and governance processes.
Tool 3.3 /Tool Vendor Profile 3.3.1
Headquarters Location
The primary country of the vendor (and legal jurisdiction if they are different).
Examples USA · China · France
Tool 3.3 /Tool Vendor Profile 3.3.1
Operating Locations
The regions or jurisdictions in which the vendor operates.
Tool 3.3 /Tool Vendor Profile 3.3.1
AI Posture
The tool vendor's AI development thesis.
Examples vendor providing its own models · customizing third-party models · using open-source models · relying on third-party AI services
Tool 3.3
Tool Packaging 3.3.2
Tool Packaging describes what is being licensed and how the tool is packaged for use.
Note This subcategory helps clarify what is actually being adopted or proposed for use from a studio perspective and what is being made available from a tool vendor perspective. The packaging of a tool often shapes deployment, data handling, update control, access patterns, and the practical ability to constrain or approve only selected AI-enabled capabilities.
Tool 3.3 /Tool Packaging 3.3.2
Packaging
How the tool is packaged and offered as a single unit.
Examples desktop software · SaaS · API-driven service · plug-in · node for use in node-driven workflows · workflow platform · AI model aggregator/router
Tool 3.3 /Tool Packaging 3.3.2
Separability
Whether separable AI capabilities can be locked down or selectively governed.
Examples customer configurable · vendor configurable · user discretion subject to guideline · not possible because the AI capabilities are deeply integrated within one another
AI Provenance 3.4
The AI Provenance category captures how the AI relevant to the tool or tool capability is enabled and trained. This category may apply at the tool level or the tool capability level depending on the communication need. In some cases, it may also need to be associated with a particular model when a specific capability relies on a distinct model with distinct provenance characteristics.
AI Provenance 3.4
AI Model Provisioning 3.4.1
AI Model Provisioning describes what AI models are made available within or alongside the tool.
Note This subcategory is useful because governance questions often differ depending on whether the AI is fixed by the tool vendor, selectable from an approved set, or open to customer-provided models.
AI Provenance 3.4 /AI Model Provisioning 3.4.1
Vendor Enabled AI Models
Models designed, bundled, owned, or pre-configured by the tool vendor for the capability, including cases where none are vendor enabled, where vendor-owned models are used, or where specific third-party models are supported.
Note It is likely that multiple cases may apply.
AI Provenance 3.4 /AI Model Provisioning 3.4.1
Customer BYO AI Models
Customer-supplied or user-selectable models that the tool supports.
Examples no Bring Your Own (BYO) support · some specific supported models · any model with certain characteristics
Note Again, multiple cases may be simultaneously true.
AI Provenance 3.4
Vendor AI Models 3.4.2
Vendor AI Models describes the origin and provider context of the models relevant to the tool or a given capability.
Note Where multiple models are involved, more than one origin or headquarters may apply, unless details about each model are spelled out.
AI Provenance 3.4 /Vendor AI Models 3.4.2
Model Origin
Whether the model was vendor-trained, obtained as open weights, derived from open weights, commercial, or derived from a commercial model.
Examples vendor-trained · open weights · derived from open weights · commercial · derived from a commercial model
AI Provenance 3.4 /Vendor AI Models 3.4.2
Model Provider Headquarters
The provider headquarters of the model source (and legal jurisdiction if they are different).
AI Provenance 3.4
Training Data 3.4.3
Training Data describes the broad source types used in training or adapting the relevant models, and the duration of commitment to those source arrangements.
Note This subcategory surfaces the broad provenance conditions that often underlie several governance concerns.
AI Provenance 3.4 /Training Data 3.4.3
Source Types
How is the training data sourced by the model provider.
Examples commercially sourced · open-source datasets · public domain · web crawl · vendor-owned · algorithmically generated · distilled from another model
AI Provenance 3.4 /Training Data 3.4.3
Named Datasets
Enumeration of specific datasets that are used.
Examples Common Crawl August 2026 Crawl Archive (CC-MAIN-2026-34) · Fineweb v1.4.0
AI Provenance 3.4 /Training Data 3.4.3
Source Commitment Duration
What is the commitment of the sources.
Examples tool lifetime · long-term support period · a defined date-based commitment
Operational Characteristics 3.5
Operational Characteristics captures the conditions surrounding deployment and operational use. Like AI Provenance, this category may apply at the tool level or the tool capability level depending on the communication need, and in some cases it may need to be associated with particular models or deployment modes.
Operational Characteristics 3.5
AI Deployment 3.5.1
AI Deployment describes where the Tool and AI Models are deployed and who controls its rollout. Note the tool itself may be deployed in one location and the AI model used by the tool in another. Or the tool may rely on multiple AI models (for example, when the tool routes requests and aggregates results).
Note This information can highlight security and privacy posture as well as operational predictability.
Operational Characteristics 3.5 /AI Deployment 3.5.1
Deployment Artifact
What is being deployed.
Examples a specific tool that includes the AI Model · a specific tool that uses AI Model deployed separately · the AI Model
Operational Characteristics 3.5 /AI Deployment 3.5.1
Host Environment
Where is the artifact deployed.
Examples on-device · on-prem · customer-controlled data center · custom-controlled network on cloud · vendor-controlled data center · vendor-controlled network on cloud
Operational Characteristics 3.5 /AI Deployment 3.5.1
Deployment Location
Where is the geographical region, if the location is vendor-controlled data center or cloud.
Examples US · Ireland · Singapore
Operational Characteristics 3.5 /AI Deployment 3.5.1
Update Rollout Control
Whether rollout timing and updates of specific tool or AI versions are controlled by the customer or vendor.
Examples customer · vendor
Operational Characteristics 3.5
Customer Data Residency 3.5.2
Customer Data Residency describes where the inputs (including prompts), outputs, workflows, and configurations made by the customer reside operationally and who acts as their custodian.
Note This subcategory supports communication around enterprise data control and vendor-customer trust boundaries around data handling.
Operational Characteristics 3.5 /Customer Data Residency 3.5.2
Custodian
Who has operational control over the customer data of a tool or model.
Examples user (the artist using the tool) · customer (such as a studio) · the tool vendor
Operational Characteristics 3.5 /Customer Data Residency 3.5.2
Data Location
Which geographical region is the data located, if the custodian is the tool vendor.
Examples US · Ireland · Singapore
Operational Characteristics 3.5 /Customer Data Residency 3.5.2
Data Collection
Whether the vendor collects data for non-operational reasons, such as for making product improvements.
Examples not collected · collected with opt-out · collection is mandatory
Operational Characteristics 3.5 /Customer Data Residency 3.5.2
Collection Data Types
If data is collected, the kind of data that is collected.
Examples prompts · input assets · output assets · workflow configurations
Operational Characteristics 3.5 /Customer Data Residency 3.5.2
Collection Retention Period
If data is collected, how long is the data retained.
Examples until deletion request · until account termination · indefinite
Operational Characteristics 3.5 /Customer Data Residency 3.5.2
Vendor Use of Collected Data
If data is collected, what is the collected data specifically used for.
Examples tool improvement for all customers · customer-specific capability improvement
Operational Characteristics 3.5
Metadata Collection 3.5.3
Metadata Collection describes what the tool vendor collects from customer use and for how long.
Note This subcategory supports communication around privacy, enterprise controls, and vendor-customer trust boundaries around metadata handling.
Operational Characteristics 3.5 /Metadata Collection 3.5.3
Metadata Collection
Whether the vendor collects data for non-operational reasons, such as for making product improvements.
Examples not collected · collected with opt-out · collection is required
Operational Characteristics 3.5 /Metadata Collection 3.5.3
Collection Metadata Types
If metadata is collected, the kind of metadata that is collected.
Examples usage timestamps · used AI models or workflows
Operational Characteristics 3.5 /Metadata Collection 3.5.3
Collection Retention Period
If metadata is collected, how long is the metadata retained.
Examples until deletion request · until account termination · indefinite
Operational Characteristics 3.5 /Metadata Collection 3.5.3
Vendor Use of Collected Metadata
If metadata is collected, what is the collected metadata specifically used for.
Examples tool improvement for all customers · customer-specific capability improvement
Operational Characteristics 3.5
Customer Model Refinement 3.5.4
Customer Model Refinement describes whether customers may fine-tune or otherwise refine models using their own data and where such refinement occurs.
Note This becomes relevant where fine-tuning, adaptation, or customer-specific model behavior is part of the proposed solution or workflow.
Operational Characteristics 3.5 /Customer Model Refinement 3.5.4
Refinement Allowed
Whether customers can fine-tune the model, yes or no.
Operational Characteristics 3.5 /Customer Model Refinement 3.5.4
Refinement Location
Where can such fine-tuning occur.
Examples customer-controlled data center · customer-controlled network on cloud · vendor-controlled data center · vendor-controlled network on cloud
Operational Characteristics 3.5 /Customer Model Refinement 3.5.4
Vendor Access
Whether vendors can access such refined models, yes or no.
Operational Characteristics 3.5 /Customer Model Refinement 3.5.4
Vendor Usage
Whether vendors use such refined models for their use or other customers' use, yes or no.
Tool Capability 3.6
The Tool Capability category classifies a capability based on two governance-relevant dimensions: output novelty and creative controllability.
Tool Capability 3.6
Output Novelty 3.6.1
Output Novelty asks how the inputs to the AI are processed, specifically whether the capability primarily extracts information from the input media, enhances existing media, corrects limited portions of existing media, creates substantially new creative elements, or creates altogether a new media.
Note This dimension helps communicate the degree to which a capability extracts, preserves, repairs, modifies, or creates output media.
Tool Capability 3.6 /Output Novelty 3.6.1
Simple Transformation
Where fidelity is improved or media is transformed without introducing materially new elements.
Examples (Formulaic) Upscaling · (Formulaic) Denoising
Tool Capability 3.6 /Output Novelty 3.6.1
Correction
Where limited new elements are introduced to locally repair or complete an otherwise existing asset. Such repairs could be performed on different layers in the media and may be composited back with other non-AI produced layers or may be performed directly on the completed media.
Examples (Creative) Upscaling · (Creative) Denoising
Tool Capability 3.6 /Output Novelty 3.6.1
Creative Modification
Where new visual, audio, or structural elements are introduced in a way that materially changes the media, but the progression from original can be visually spotted or discovered.
Examples (Creative) Inpainting · Visual dubbing · De-aging · Aging · Style transfer
Tool Capability 3.6 /Output Novelty 3.6.1
Guided Creation
Where substantially new media is generated, often with many different valid outcomes from similar inputs.
Examples Text to video · Image to video · Performance transfer
Tool Capability 3.6
Creative Controllability 3.6.2
Creative Controllability asks how much of the AI-based transformation recipe is defined by, or inherent, to the AI versus explicitly driven by the user.
Note This dimension is important because governance may consider not only by what kind of output is produced, but also by how much creative agency, variability, and user-directed composition is involved in producing it.
Tool Capability 3.6 /Creative Controllability 3.6.2
Preset Automation
Where the user selects from predefined operations and the output is largely determined by the tool. In a video generative example, this could be when the capability exposes only a fixed set of input controls to the user, such as a single text prompt (limited tokens), start frame, and end frame.
Examples One Text Prompt (limited expression) · Start Frame · End Frame
Tool Capability 3.6 /Creative Controllability 3.6.2
Parameterized Automation
Where the user adjusts predefined parameters to influence the output, but within fixed processing areas. In a video generative example, this could be when the capability exposes a fixed set of input controls to the user plus some limited tunable parameters such as control over the grain in the media (by providing a control on the number of denoising steps).
Examples Denoising steps · Style weight slider · …
Tool Capability 3.6 /Creative Controllability 3.6.2
Conditioned Transformation
Where inputs and selected controls meaningfully shape the result within a constrained recipe, and multiple valid outcomes may exist. In a video generative example, this could be when the user has some freedom to control the output using, say, depth maps and camera motion track. In this hypothetical, while the user has the freedom to provide different depth maps and camera motion tracks, they neither can control how the AI uses them to produce the outputs nor can they control the camera angle.
Examples Depth Map · Timing reference · Camera motion reference · …
Tool Capability 3.6 /Creative Controllability 3.6.2
Composable Workflow
Where the user assembles and controls the workflow significantly and therefore has substantially more influence over the outcome. In the video generative example, this could be when the user can produce an output by deciding on the number of layers in the media and which layer to target in what order, by having the ability to work on specific region within each layer separately and to use several AI features such as segmentation, compositing, and inpainting on specific targeted regions and layers to produce the media.
Examples Layers (work on each layer) · Regions (work on separate regions) · Functions (compositing, segmentation) · Reusable pieces (poses, hair styles, fire styles, costume styles)