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

Keep truth context and value origin separate

Data Steward · Trigger: Data includes observations, plans, predictions or derived 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 satisfied

Tests will retain distinct assertion contexts and origins through storage and publication.

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-007WMS.dbo.BaleMovement → canonicalBinding· OPTIMON-IND / Halol Packaging Line
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-014Packing/Vision/Cam3/Defect → canonicalBinding· OPTIMON-IND / Nagda Warehouse
resolutionresolvedconflictstableapprovalpending
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-021heat.telemetry v1.2Contract version· OPTIMON-IND / Raigarh Melt Shop
statepublishedcompatibilitycurrentimpactaccepted
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: state = published

Exception path

A predicted value will not overwrite an actual observation even if subject and timestamp match.
Alternate path. Stewards disagree: open the conflict case and leave the binding pending until it is decided.
not yet satisfied
Operates onBIND-007WMS.dbo.BaleMovement → canonicalBinding· OPTIMON-IND / Halol Packaging Line
resolutionresolvedconflictstableapprovalapproved
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: conflict = conflicting, resolution = pending

Workflow as specified

CoreSync will validate actual, planned, normative, predicted, scenario and desired contexts separately from measured, inferred, estimated, derived or manual origin.

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.