CS-PER-007 · PER Vision, location, spatial and multimodal evidence · 91 of 192
Capture barcode, QR and checkpoint scans
Operations Data Integrator · Trigger: An operator or station scans an identifier.
Simulated fixture data. Every record, receipt and timeline entry on this screen is demonstration material. It is never production evidence.
Acceptance
1 of 3 steps satisfiedScan evidence will distinguish identity capture, checkpoint observation and separately verified execution.
Run the remaining steps below. The result is read back from record state — nothing here is a toast.
Normal path
Vision, location or spatial evidence is admitted under policy with its custody chain intact.
Step 1. Accept the perception event, preserving its original capture time.
satisfiedqueueacceptedcorrectionsupersededauthorityverified
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: queue = accepted, authority = verified
Step 2. Activate the policy that governs retention and minimisation.
not yet satisfiedstatedraftbindingpendingreviewreview
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: state = active, binding = granted
Step 3. Verify the custody chain from capture to record.
not yet satisfiedOperates onEVID-012Asset/Bale · mass evidence 12Evidence chain· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
custodyunknowncompletenessmissingmaturityconformant
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: custody = verified
Exception path
A successful scan will not automatically prove a downstream physical or business action.
Alternate path. The reading is disputed: record a correction; the original is retained, never erased.
satisfiedqueueacceptedcorrectionsupersededauthorityverified
Moves the record and writes evidence. Permission: remediate.
Acceptance for this step: correction = superseded
Workflow as specified
CoreSync will acquire the code, scanner identity, declared checkpoint, time and operator context where authorized, then resolve the code through its issuer and scheme.
Evidence written in this session
Nothing run yet in this session. Record state shown above may already satisfy steps from the seeded fixture history.
Journeys that include it
Not part of a composite journey; exercised through its family views.