CS-SEM-001 · SEM Canonical identity, authority and temporal context · 101 of 192
Bind a source field to an existing canonical parameter
Semantic Steward · Trigger: A selected source field needs approved meaning.
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 satisfiedA sample publication will resolve to the approved subject and definition with its binding version.
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 satisfiedresolutionconflictingconflictconflictingapprovalapproved
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 satisfiedresolutionpendingconflictstableapprovalpending
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.
satisfiedstatepublishedcompatibilitycurrentimpactaccepted
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: state = published
Exception path
Similar names will not justify a binding when quantity or applicability is incompatible.
Alternate path. Stewards disagree: open the conflict case and leave the binding pending until it is decided.
not yet satisfiedresolutionconflictingconflictconflictingapprovalapproved
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: conflict = conflicting, resolution = pending
Workflow as specified
CoreSync will connect the source field to a canonical subject and applicable parameter or event definition, preserving source unit, mapping method and evidence.
Evidence written in this session
Nothing run yet in this session. Record state shown above may already satisfy steps from the seeded fixture history.