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

Hold an unresolved or ambiguous identity for review

Data Steward · Trigger: A record has no unique approved subject match.

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 satisfied

Resolution evidence will show the candidates, decision, effective interval and affected records.

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.
satisfied
Operates onBIND-001Line1/Furnace/Heat.Temp → canonicalBinding· OPTIMON-IND / Raigarh Melt Shop
resolutionresolvedconflictstableapprovalapproved
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.
not yet satisfied
Operates onBIND-008/in/qc-results-2026-09.csv → canonicalBinding· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
resolutionresolvedconflictstableapprovalrejected
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.
satisfied
Operates onCONT-015defect.event v5.2Contract version· OPTIMON-IND / Halol Packaging Line
statepublishedcompatibilitycurrentimpactaccepted
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: state = published

Exception path

Human review will not bypass protected identity or tenant-boundary checks.
Alternate path. Stewards disagree: open the conflict case and leave the binding pending until it is decided.
not yet satisfied
Operates onBIND-001Line1/Furnace/Heat.Temp → canonicalBinding· OPTIMON-IND / Raigarh Melt Shop
resolutionresolvedconflictstableapprovalapproved
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: conflict = conflicting, resolution = pending

Workflow as specified

CoreSync will retain admissible raw evidence, open a resolution case and prevent inappropriate canonical publication until the contract permits a qualified or resolved outcome.

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.