CS-SYN-002 · SYN Governed synchronization and action-boundary transport · 186 of 192
Reconcile conflicting synchronization states
Data Steward · Trigger: Source and target report incompatible effective states.
Simulated fixture data. Every record, receipt and timeline entry on this screen is demonstration material. It is never production evidence.
Acceptance
2 of 3 steps satisfiedThe final state will retain the chosen rule, rejected alternatives and unresolved uncertainty.
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.
satisfiedpermitgrantedsynchronizationcurrentcommandEvidenceaccepted
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.
satisfiedcustodyverifiedcompletenesscompletematurityproposed
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: custody = verified
Exception path
Arrival order will not silently decide which business state is authoritative.
Alternate path. Authority is withdrawn: revoke the permit and hold every staged command.
not yet satisfiedpermitgrantedsynchronizationcurrentcommandEvidenceaccepted
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: permit = revoked, synchronization = blocked
Workflow as specified
CoreSync will compare versions, authority, source history and delivery evidence, then apply an approved conflict rule or open a resolution case.
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.