SheetID and sheet tracking
TURAPING Flow R is the selected device. Sheet-level compatibility and deployment configuration require separate validation.
Feasibility matrix requiring acceptance
| Control | Evidence status |
|---|---|
| Early image while paper remains controllable | Mobile-ID requirement; vendor image/timing traces required |
| SheetID, duplex sides and attempts | API/SDK mapping and missing/duplicate-image tests required |
| Decision/ACK/execution/location | Four distinct states; ACK is not location evidence |
| Buffering, interleaving and reordering | Ground-truth sample tests; no acceptance results supplied |
| Full/jam/offline/late | Configured safe-stop/hold; no blind physical-command replay |
Materials and operating responsibilities
Assess loose A4 sheets, thickness, curl, staples/adhesives, printed sides and condition before piloting. Bound books, fragile material and other sizes are outside default scope; do not substitute another model for Flow R. Operators prepare paper, retain custody and establish location after faults; suppliers agree maintenance/replacement, firmware and recovery instructions.
Flow R scope
The manufacturer describes intake, scanning, holding, return, filing and packaging. Trusted Records requires sheet–image–decision–location linkage. Received sources contain no accepted API/SDK, firmware, timing, buffer or execution-ACK evidence.
Sheets, sides and images
SheetID identifies a sheet; ImageID identifies an image/side and scan attempt. Rescans create new attempts linked to prior attempts. DossierID and sequence preserve structure, not image filenames alone.
Reconcile before closure
Compare expected sheets, captured images, missing sides, routes and ACKs. For exception-tray sheets, retain location/custodian. Jobs remain open until every sheet has a reconciliation decision.
Missing sides and duplicate images
Detect using capture configuration and checksum/sequence; humans identify authoritative copies. Rescans retain mappings; duplicate detection does not authorize source deletion.
Continue the workflow
Two 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 detailsIntegrity, provenance and evidence
Each evidence type answers a different question; hashes, timestamps and approvals are not interchangeable.
Read detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment