CS-SEM-006 · SEM Canonical identity, authority and temporal context · 106 of 192
Apply source authority and retain conflicting assertions
Data Steward · Trigger: Two sources report incompatible states or values.
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 satisfiedA conflict test will show both sources, the governing rule and the disposition.
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.
satisfiedOperates onBIND-004Packing/Vision/Cam3/Defect → canonicalBinding· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
resolutionresolvedconflictstableapprovalrejected
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.
satisfiedresolutionresolvedconflictstableapprovalapproved
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 satisfiedstatedraftcompatibilitybreachedimpactreview
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: state = published
Exception path
Last arrival, larger numeric value or higher model confidence will not independently establish authority.
Alternate path. Stewards disagree: open the conflict case and leave the binding pending until it is decided.
not yet satisfiedOperates onBIND-004Packing/Vision/Cam3/Defect → canonicalBinding· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
resolutionresolvedconflictstableapprovalrejected
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: conflict = conflicting, resolution = pending
Workflow as specified
CoreSync will preserve both assertions and use approved field- or fact-specific precedence, keeping unresolved disagreement visible to downstream consumers.
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.