OptimonCoreSync Studio
IE
CS-SEM-008 · SEM Canonical identity, authority and temporal context · 108 of 192

Propagate approved identity merges and splits

Semantic Steward · Trigger: The semantic authority corrects duplicate or conflated identities.

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

Impacted records will retain a navigable link between original and corrected resolutions.

Run the remaining steps below. The result is read back from record state — nothing here is a toast.

Normal path

Meaning is agreed: the canonical subject is resolved, approved and carried into a published contract.
Step 1. Resolve the canonical subject and its event-time rule.
not yet satisfied
Operates onBIND-006Line1/Furnace/Heat.Temp → canonicalBinding· OPTIMON-IND / Nagda Warehouse
resolutionpendingconflictstableapprovalpending
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: resolution = resolved, conflict = stable
Step 2. Approve the effective mapping from its effective date.
satisfied
Operates onBIND-013/in/qc-results-2026-09.csv → canonicalBinding· OPTIMON-IND / Raigarh Melt Shop
resolutionresolvedconflictstableapprovalapproved
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: approval = approved
Step 3. Publish the contract version that carries the agreed meaning.
not yet satisfied
Operates onCONT-020defect.event v5.1Contract version· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
statesupersededcompatibilitypartialimpactblocked
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: state = published

Exception path

CoreSync will not independently merge identities or relabel all history without authority.
Alternate path. Stewards disagree: open the conflict case and leave the binding pending until it is decided.
not yet satisfied
Operates onBIND-006Line1/Furnace/Heat.Temp → canonicalBinding· OPTIMON-IND / Nagda Warehouse
resolutionpendingconflictstableapprovalpending
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: conflict = conflicting, resolution = pending

Workflow as specified

CoreSync will update future binding resolution and emit or coordinate approved correction references for affected publications without deleting their original 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.

Journeys that include it

Not part of a composite journey; exercised through its family views.