Reference
Production handoff checklist
Check record completeness before an authorized team makes a separate production decision.
Use this as a record-completeness check, not as automatic rights approval. Your authorized team still owns the decision.
Sources and people
- Every detected source is Linked or Not a person; none remain Review required without an owner and follow-up.
- Each known person appears once in the project and is reused across sources.
- Group sources link every represented person who needs to be in the project record.
- A source link has not been treated as proof of agreement or authority.
Intended use
- The brief is complete and understandable without the graph.
- Deliverables, channels, platforms, media treatment, territory, languages, dates, category, and final approval are explicit.
- Person-specific restrictions, compensation notes, caveats, and authority notes are reviewed separately.
- Compensation and exclusivity are included, handled separately, or explicitly out of scope.
- Revocation and takedown name an actionable path.
- Each workflow acknowledges the current scope against its own manifest.
Requests and decisions
- Each recipient outcome applies to the exact current scope.
- A caveat, change request, decline, exclusion, or no-authority response has not been treated as approval.
- Recipient response and internal review remain separate.
- An authorized internal reviewer completed the decision in the canonical Pluribus workspace.
- Material changes produce a new request while older responses remain historical evidence.
Recovery and security
- Restart recovers the project and private workflow/source bindings.
- ComfyUI is bound to loopback or protected with trusted authentication.
- The team has reviewed the data boundary for the exact production stack.
- If a device was disconnected, the server confirmed revocation.
- The current limits and applicable release notes are understood.
Need a hand?
Bring the graph structure and the question, not private media. Open a GitHub issue or email support@trypluribus.com with the release tag, ComfyUI version, node class names, and exact panel message.