Edge Controller and control flow
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.
Station roles
Edge retains job/SheetID context, receives decisions, routes sheets, handles ACKs and buffers offline work by design. mTLS/device trust needs configuration/certificates and is not assumed for every device.
Three communication paths
REST/API serves synchronous interactions; Kafka/domain events serve asynchronous business notifications; adapter/control paths handle deadline-bound commands and safe-stop. Test deadlines, retries and buffering per station.
Reconnect and handover
Reconcile sequence/idempotency, open jobs, unacknowledged routes and paper locations before syncing. Shift handovers retain buffer snapshots and responsibility; resets must not erase faults.
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