Cases
Case objects, statuses, and review states for Klarefi intake workflows
Case object
A case represents one intake packet moving from submission to review. It keeps the applicant session, documents, extracted facts, follow-up history, review state, and integration metadata together.
Common fields
case_id: Klarefi case identifiercase_type_id: Case type used to evaluate the intakeworkflow_idandworkflow_version: Workflow declaration used by the caseoperating_mode:system_of_intelligenceorsystem_of_actionruntime_status:processing,intake_in_progress,gate_ready,gate_evaluating,ready_for_review, orcompleteworkspace.facts: Extracted facts with resolution status and cited evidenceworkspace.documents: Documents associated with the caseworkspace.operational_summary: Blockers, ownership, and the primary actionworkspace.summary: Fact and document countsupdated_at: Projection update time
Decision
A workflow can end with an offer or a decline. The case package's decision holds
it, with one of these statuses:
offer_sent: the offer is with the applicantaccepted: the applicant signed, or a person recorded that they acceptedapproved: a person sent a yes that expects no answer. It was final when it was sent, and it has novalid_untildeclined: a person declined the applicationnot_taken: the applicant said no, the offer's last day passed, or a person recorded that it was not takenwithdrawn: the offer was taken back, or the case was reopened
name is what the workflow calls the decision, such as "Coverage
confirmation", or null for a plain offer or decline. kind stays offer or
decline whatever it is called.
decision is null on a case without one. See
Offers and declines.
The package also has decisions, a list. That is the sign-off record: one
entry each time a person completed the case, with who and when. decision is
what they decided and sent.
Status guidance
Use runtime_status for workflow orchestration. Use the queue projection for
operator queues and workspace.facts[].status for item-level resolution state.