Pluribus Docs

Pluribus for ComfyUI

Connect the people in a ComfyUI workflow to a specific project and intended use without uploading the graph or creative assets.

Pluribus helps an AI-media production team connect person-bearing sources in a ComfyUI workflow to the real people involved, document a specific proposed use, request confirmation from the right recipient, and track what changes.

The source scan runs locally. Pairing enables a narrow structured sync for the project, people, intended use, requests, responses, and internal review state. It does not upload the graph or creative assets.

Release status: Pluribus for ComfyUI is in controlled release-candidate testing. Read the v0.4.0-rc.2 notes before using it in a production workflow.

The five-step workflow

  1. Find sources. Scan supported graph provenance locally for sources that may represent people.
  2. Link people. Connect each source to the correct project person or deliberately mark it as not a person.
  3. Describe intended use. Record the client, deliverables, channels, territory, dates, restrictions, compensation and exclusivity treatment, final approval, and revocation path.
  4. Request confirmation. Present that exact scope to the person or their representative.
  5. Track and review. Keep the recipient response and your team's internal review as separate, explicit states.

The questions Pluribus helps answer

  • Which real people may be represented by this graph?
  • Which sources are linked to each project person?
  • What exactly are we proposing to do?
  • What did the recipient say about that request?
  • Has our own authorized team reviewed it separately?

The boundary

Pluribus does not identify a face from pixels, determine legal authority, approve rights, or replace legal, business-affairs, union, or production review. A source link records who a source is intended to represent. A recipient response records what that recipient said about one exact request. Neither is an automatic internal approval.

Start here

On this page