CS-SEM-002 · SEM Canonical identity, authority and temporal context · 102 of 192
Resolve one subject across several systems
Semantic Steward · Trigger: ERP, MES, historian and equipment identifiers refer to a common subject.
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 satisfiedCross-source records will resolve consistently and retain issuer-specific lineage.
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-028/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: 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
Conflicting matches will remain visible rather than creating silent duplicate or merged identities.
Alternate path. Stewards disagree: open the conflict case and leave the binding pending until it is decided.
not yet satisfiedOperates onBIND-028/in/qc-results-2026-09.csv → 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 submit scoped source references to the semantic authority and apply the approved canonical resolution while preserving all original identifiers.
Evidence written in this session
Nothing run yet in this session. Record state shown above may already satisfy steps from the seeded fixture history.