Describe the intended use
Create a complete project scope and review the terms and AI actions that apply to each person.
Open Intended use and write the brief so a recipient can understand it without access to your ComfyUI canvas.
The project shares one versioned intended-use scope. Each workflow separately acknowledges that scope against its own exact rights manifest.
What will be made
Describe the proposed use and every deliverable in plain language. Record:
- The intended use
- Each video, still, variation, localization, or other deliverable
- The product or service being advertised
- Whether final creative approval is required
Where and when it will run
Name the channels, platforms, paid and organic media treatment, territory, languages, and usage dates. Usage start and end are calendar dates; the recipient should see the same entered dates in every time zone.
What applies to each person
Review each project person separately. Record:
- Restrictions or prohibited contexts
- Person-specific compensation notes
- Usage comfort, caveats, or conditions
- The recorded basis or limits of representative authority
- The AI actions that apply to that person in this workflow
People can have different values. Do not copy one global restriction or blank compensation value across every record.
Representative notes are context, not an authority determination.
Compensation and exclusivity
For both compensation and exclusivity, choose one honest treatment:
- Included in this request — summarize what the recipient is being asked to confirm
- Handled separately — name the separate process and optionally summarize it
- Not part of this request — make the exclusion explicit
Do not leave either topic ambiguous merely because Pluribus does not execute contracts or payments.
Revocation and takedown
Paid media and external activation require an actionable path. Record usable instructions, an expected response time, and whether revocation requires:
- Disabling a person-specific model or adapter
- Removing published creative from named platforms
- Another specific action owned by a named party
A response-time promise alone does not say who should act or what they should do.
Review suggested AI actions
Pluribus suggests structured AI actions only for supported node classes. Current mappings can include:
- Face swap or supported image editing → face editing
- Face adapters → face-conditioned generation
- Identity LoRA loading → digital-replica generation use, not a claim that this workflow trained the LoRA
- Reference image loading → biometric or reference-input processing
- Supported image-to-video → synthetic-performance rendering
- Person-like prompt paths → directed depiction generation
Review the suggestions against what the workflow actually does. Unsupported custom nodes and work performed outside the graph are not captured automatically. A manual normalized AI-action override is not yet available in the panel.
Save per workflow
Choose Save intended use. Review and save again when you move from character sheet to storyboard, production, or final, even if the project-wide fields did not change. Each workflow must acknowledge the current scope against its own manifest.