Read statuses and scope changes
Keep source identity, recipient response, and internal review separate, and know when to request again.
A person row reports three different facts. Read all three; do not collapse them into one approval label.
| Axis | What it records |
|---|---|
| Source / person link | Who the source is meant to represent |
| Recipient request | What that recipient said about this exact scope |
| Internal review | What your own authorized team concluded separately |
Recipient response is not internal review
A recipient confirmation never completes internal review. The canonical Pluribus workspace owns that action. ComfyUI can read the current internal review status but cannot set it.
Examples:
| Recipient event | Request axis | Internal-review axis |
|---|---|---|
| No request yet | Ready to request | Unchanged |
| Request created | Pending or Sent | Unchanged |
| Recipient confirms | Confirmed | Unchanged |
| Recipient adds a caveat | Confirmed with caveat | Unchanged |
| Recipient asks for edits | Changes requested | Unchanged |
| Recipient lacks authority | No authority | Unchanged |
| Recipient declines | Declined | Unchanged |
| Recipient excludes the person | Excluded | Unchanged |
The plugin never turns a recipient response into Cleared.
Know when to request again
Pluribus keeps older responses as historical evidence, but marks them Scope changed — request again when a material rights fact changes.
| Change | Result |
|---|---|
| Move nodes or change unrelated generation settings | Response stays current |
| Edit a display label or internal marker note | Response stays current |
| Link a different person | Request again |
| Change a source classification | Request again |
| Add a rights-relevant AI operation | Request again |
| Change dates, channels, deliverables, terms, or per-person restrictions | Request again |
Rights manifest versus graph fingerprint
The rights manifest captures the facts that determine whether the request still matches the workflow:
- Stable workflow reference and workflow kind
- Stable source references and source classifications
- Linked project-person IDs
- Normalized downstream operation classes
- The current versioned intended-use scope
The full graph fingerprint is separate audit metadata. A graph can change without changing the smaller rights manifest, so unrelated plumbing does not automatically invalidate a response.
When a material fact changes, make a new exact request. Keep the old response as historical evidence rather than editing it into a different scope.