An extraction result should not also be permission to export

Description and use

In Aplos Document Desk, extraction, review, and export are separated: the model outputs a draft, a human reviews it, and only after payment can the CSV be downloaded.

Problem

Separating extraction, review, and export ensures that a model’s output is not automatically treated as a final, exportable artifact, preventing incorrect data from being sold.

Outcome

The workflow enforces a clear separation between model output, human validation, and payment authorization, reducing the risk of exporting incorrect data.

Workflow

• Upload documents → queued → processing → draft
• Human reviewer reviews draft, resolves errors, and marks as reviewed
• Server validates required fields and checks for duplicates or inconsistencies
• If approved, server seals batch into a CSV within a transaction
• Payment is verified against the export job before allowing download

Evidence

The extractor returns fields with a value and a source quote. Application code normalizes the candidate and checks whether the quoted text occurs in the extracted source.

Source

Make review a server-side state transition

Source

Preparing an export happens inside a database transaction. Each included document must be reviewed; excluded documents are omitted.

Source