Skip to content
Ritesh FirodiyaGet in touch

Work / Chitragupt / Wiki / Flows

document-lifecycle-owner-mismatch

Flowcanonicalverified 2026-06-26

FLOW.DOCUMENT-LIFECYCLE.OWNER-MISMATCH

Flow — Document lifecycle · Owner mismatch

Summary

The extracted PAN / IFSC / account number did not match the uploader's profile. The user must accept ownership, transfer to a family member, or delete.

Audience

end-user

Entry

Document marked pending_identity_confirmation (the single collapsed status from 2026-07-11-user-identity-entry-model) from the document-lifecycle-ingest branch; identity-matcher logic per user-identity-entry (was: pending_owner_confirmation + 2026-05-31-owner-validation — superseded).

Steps

# Step Surface Notes
1 Document is pending_owner_confirmation review-document-owner-mismatch Shows mismatch reason + three actions
2a Accept ("it's mine") review-document → confirmed (EXIT)
2b Transfer to family member review-document-transfer-pending → pending_family_transfer — see document-lifecycle-family-transfer
2c Delete review-document-failed → rejected_owner_denied; swept after 7-day grace

Exit

Document confirmed (Accept path) — fields flow into Tax / Expense / Portfolio via onDocumentConfirmed.

Escapes

  • Confirm gate: pending_owner_confirmation IS confirmable — Accept is the confirm action. See the shared confirm-gate rule in document-lifecycle-ingest.
  • Delete + 7-day sweep: doc auto-deletes after grace; user has time to recover.
  • Transfer declined by recipient: bounces back to uploader as pending_owner_confirmation per document-lifecycle-family-transfer.
  • Non Pro Family workspace: transfer option hidden; only Accept / Delete shown.

Sources

  • .context/wiki/flows/* § "Flow 12 — Document lifecycle state machine" · "F. Owner mismatch"

Every project of mine is written down like this.

Read the résumé