OptimonCoreSync Studio
IE
CS-SYN-004 · SYN Governed synchronization and action-boundary transport · 188 of 192

Validate the permit before command transport

Command Gateway Operator · Trigger: A separately authorized command reaches CoreSync.

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 satisfied

Negative tests will deny unpermitted commands and retain the exact rejection reason.

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.
not yet satisfied
Operates onSYNC-006CMMS work order sync 6Sync target· OPTIMON-IND / Nagda Warehouse
permitpendingsynchronizationdriftedcommandEvidencequeued
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.
satisfied
Operates onSYNC-006CMMS work order sync 6Sync target· OPTIMON-IND / Nagda Warehouse
permitpendingsynchronizationdriftedcommandEvidencequeued
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 satisfied
Operates onEVID-008Asset/PackLine-3 · energy evidence 8Evidence chain· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
custodyunknowncompletenessmissingmaturityconformant
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: custody = verified

Exception path

A recommendation, stale permit or forged target will not authorize transport.
Alternate path. Authority is withdrawn: revoke the permit and hold every staged command.
not yet satisfied
Operates onSYNC-006CMMS work order sync 6Sync target· OPTIMON-IND / Nagda Warehouse
permitpendingsynchronizationdriftedcommandEvidencequeued
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: permit = revoked, synchronization = blocked

Workflow as specified

CoreSync will validate permit scope, target, validity, required evidence and current policy before dispatch through the governed gateway.

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