Device/Edge integration
Device command contracts retain commandId, SheetID, deadlines, acknowledgements and recovery semantics.
Proposed command and ACK
Command: commandId, jobId, sheetId, imageRefs, decisionRef/version, targetTray, deadline and stationId. ACK: commandId, sheetId, observedTray, resultCode, occurredAt. This proposal needs comparison with actual firmware/adapters.
Safe-stop and manual fallback
Missing ACK/full tray/disconnect remain incomplete; stop or use tested exception handling. Unknown paper position requires operator checks and custody records. Kafka does not establish hard real-time deadlines.
Go-live evidence
Require compatibility matrices, command/ACK traces, fault injection, offline-buffer/reconnect, rescans and shift handovers. Test device/service permissions and certificate lifecycles against configuration.
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