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

Propose a missing canonical definition

Semantic Steward · Trigger: A legitimate source concept has no approved target definition.

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

Publication will use an approved definition or remain explicitly pending; the proposal history will be retained.

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-002WMS.dbo.BaleMovement → canonicalBinding· OPTIMON-IND / Nagda Warehouse
resolutionresolvedconflictstableapprovalpending
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-009Packing/Vision/Cam3/Defect → canonicalBinding· OPTIMON-IND / Raigarh Melt Shop
resolutionconflictingconflictconflictingapprovalapproved
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-016heat.telemetry v1.0Contract 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

A connector will not create private Core semantics to make its import succeed.
Alternate path. Stewards disagree: open the conflict case and leave the binding pending until it is decided.
not yet satisfied
Operates onBIND-002WMS.dbo.BaleMovement → canonicalBinding· OPTIMON-IND / Nagda Warehouse
resolutionresolvedconflictstableapprovalpending
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: conflict = conflicting, resolution = pending

Workflow as specified

CoreSync will create a governed proposal with examples, quantity semantics and intended scope for the appropriate Core, functional, DomainX or tenant steward.

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.