Skip to content
Ritesh FirodiyaGet in touch

Work / Chitragupt / Wiki / Flows

document-lifecycle-classification

Flowcanonicalverified 2026-06-26

FLOW.DOCUMENT-LIFECYCLE.CLASSIFICATION

Flow — Document lifecycle · Classification path

Summary

The parser could not identify the form type. The user picks form_type + ay from a picker; classifyDocument re-extracts fields with the manual hint and routes the doc onward.

Audience

end-user

Entry

Document marked needs_classification from the document-lifecycle-ingest branch, document-lifecycle-upgrade-backfill, or document-lifecycle-ocr.

Steps

# Step Surface Notes
1 Document is needs_classification review-confirm-doc Inbox Review surfaces a "What document is this?" picker
2 User picks form_type + AY review-confirm-doc Choices drawn from inbox-document-types
3 classifyDocument re-extracts pillar-inbox Sets fields + transitions state
4 Transitions to unreviewed review-document See document-lifecycle-standard-review

Exit

Document is unreviewed with classified form_type + ay; standard review begins.

Escapes

  • Confirm gate: needs_classification is NOT confirmable until classification completes — see the shared rule in document-lifecycle-ingest.
  • User misclassifies: parser may surface no fields; doc returns to needs_classification (or parse_pending).
  • No matching form_type in picker: doc must be deleted or re-uploaded as a different export.

Sources

  • .context/wiki/flows/* § "Flow 12 — Document lifecycle state machine" · "D. Classification path"

Every project of mine is written down like this.

Read the résumé