Work / Chitragupt / Wiki / Flows
document-lifecycle-family-transfer
Flowcanonicalverified 2026-06-26
FLOW.DOCUMENT-LIFECYCLE.FAMILY-TRANSFERFlow — Document lifecycle · Family transfer
Summary
Owner validation matched a different family workspace member. The document waits for that member to accept or decline the transfer (Pro Family only).
Audience
end-user (Pro Family member)
Entry
Document marked pending_family_transfer from the document-lifecycle-ingest branch or document-lifecycle-owner-mismatch; available only on tier-pro-family via family-workspace.
Steps
| # | Step | Surface | Notes |
|---|---|---|---|
| 1 | Document is pending_family_transfer |
review-document-transfer-pending | Visible to uploader as "transfer in flight" |
| 2 | Recipient sees the doc in their transfer queue | inbox-transfers | Member-facing queue |
| 3a | Recipient accepts | review-document | → unreviewed for the recipient — see document-lifecycle-standard-review |
| 3b | Recipient declines | review-document-owner-mismatch | → rejected_transfer_denied then bounces back to uploader as pending_owner_confirmation — see document-lifecycle-owner-mismatch |
Exit
Recipient accepts; the doc enters the standard review path under the recipient's account.
Escapes
- Confirm gate:
pending_family_transferis NOT confirmable (neither party has accepted ownership). See the shared rule in document-lifecycle-ingest. - Recipient never acts: doc remains pending; uploader can recall by re-uploading or deleting.
- Workspace dissolved mid-transfer: doc bounces back to uploader.
- Non Pro Family: path is not reachable; owner mismatch resolves via Accept / Delete only.
Sources
- .context/wiki/flows/* § "Flow 12 — Document lifecycle state machine" · "G. Family transfer"
Every project of mine is written down like this.
Read the résumé