A double-sided sheet has only one captured side; keep the batch incomplete, rescan and link the earlier attempt.
Trusted Records · Platform
Scanning and reconciliation
Bind each sheet to its scan images, processing attempt and routing result so recovery preserves the physical–digital link.
Inputs and starting conditions
Ready batch, preflight-checked station/device, SheetID and material-specific scan profile; duplex capture only where supported.
Workflow and control gates
- 01Preflight
- 02Capture image + SheetID
- 03Process / classify
- 04Route and ACK
- 05Reconcile job
Track sheet and side counts separately, detect missing/duplicate images and reconcile acknowledgements with physical position. Command delivery does not prove correct tray receipt. Do not close a job with unreconciled sheets.
Exceptions and recovery
Jam or multi-feed: stop safely, identify the affected range and rescan. Link the new attempt to old images without erasing history. Reconcile offline-buffered work after reconnecting.
Roles, outputs and states
| Responsibilities | Evidence and states |
|---|---|
| The operator checks paper; Edge executes through its adapter; the supervisor resolves exceptions; QC independently checks output. | ScanJob, ImageID, SheetID, attempt, device/profile, route, ACK and reconciliation. States: loaded → scanning → rescan required / reconciled. |
Station failure matrix
| Scenario | Operating decision |
|---|---|
| Jam / multi-feed | Stop, inspect affected range and retain rescan mappings. |
| Missing side | Compare profile, side counts and images before retry. |
| Full tray / missing ACK | Keep incomplete; verify paper position and avoid blind resends. |
| Sorter disconnect / offline Edge | Configured safe-stop/buffering; reconcile after reconnect. |
| AI timeout | Route to review or reasoned manual handling. |
| Shift handover | Hand over open jobs, buffers and paper custodians. |
Scenario and acceptance criteria
Complete only when
Every required side has an image and reconciliation result; replacements preserve history.
Interfaces for this workflow
Six steps of paper–digital operation
- 01Load dossiers
- 02Flow R captures images
- 03Mobile-ID recognizes
- 04Send decision
- 05Flow R executes
- 06Reconcile paper–digital
Control loop
Image → recognize → decide → execute → confirm. The device transports/holds paper; Mobile-ID recognizes and decides; Trusted Records reconciles. Early images, deadlines, ACKs and buffers are requirements pending vendor validation.
Governance loop
QC → acceptance → registration → access → discovery → preservation → delivery/disposition. Born-digital records use package validation and bypass Flow R. Uncertain AI results require configured holding/buffering/stopping rather than assuming a reviewer can respond during an unverified transport window.
Sheet ↔ image ↔ dossier ↔ decision ↔ location ↔ reconciliation. Capture order is not authoritative order; reconstruction requires mappings and evidence.
Integration handoff
End-to-end integration workflows
Connect technical states to business decisions instead of merely listing endpoints.
Read detailsOpenAPI and Swagger Reference
The proposed contract is rendered from one local specification; no network Try-It or real credentials.
Read detailsErrors and next actions
A consistent error envelope guides recovery without disclosing sensitive data.
Read detailsContinue the workflow
AI/OCR and human review
Turn images into searchable data, with human decisions when confidence or business rules are insufficient.
Read detailsTwo journeys, one records lifecycle
Connect paper and born-digital records through persistent identifiers, policies and evidence.
Read detailsIntegration quickstart
Exercise ingest → job tracking → registration → verification with synthetic data.
Read detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment