CS-SYN-006 · SYN Governed synchronization and action-boundary transport · 190 of 192
Acquire read-back evidence for outcome verification
Action Evidence Steward · Trigger: A command requires confirmation from the target or physical world.
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 satisfiedVerification will use actual correlated evidence or retain an explicit unknown outcome.
Run the remaining steps below. The result is read back from record state — nothing here is a toast.
Normal path
An outbound action is permitted, staged under dual control and evidenced by a receipt — permit, transport and outcome kept apart.
Step 1. Record the synchronization permit. A permit is not a transport.
satisfiedpermitgrantedsynchronizationblockedcommandEvidenceaccepted
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: permit = granted
Step 2. Stage the command under dual control.
not yet satisfiedpermitgrantedsynchronizationblockedcommandEvidenceaccepted
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: commandEvidence = queued
Step 3. Verify the receipt chain; a receipt is not a real-world outcome.
not yet satisfiedOperates onEVID-010Asset/Pump-P204 · vibration_velocity evidence 10Evidence chain· OPTIMON-IND / Nagda Warehouse
custodyreviewcompletenesspartialmaturitypartial
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: custody = verified
Exception path
CoreSync will not manufacture completion from elapsed time or an optimistic status code.
Alternate path. Authority is withdrawn: revoke the permit and hold every staged command.
not yet satisfiedpermitgrantedsynchronizationblockedcommandEvidenceaccepted
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: permit = revoked, synchronization = blocked
Workflow as specified
CoreSync will acquire the declared read-back or event evidence and deliver it to the authoritative outcome-verification service with command correlation and source provenance.
Evidence written in this session
Nothing run yet in this session. Record state shown above may already satisfy steps from the seeded fixture history.