CS-SEM-005 · SEM Canonical identity, authority and temporal context · 105 of 192
Resolve operating context at event time
Manufacturing Data Steward · Trigger: An observation needs its order, batch, product or shift context.
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 late record will resolve to the correct historical context and expose unavailable context.
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 satisfiedOperates onBIND-003/in/qc-results-2026-09.csv → canonicalBinding· OPTIMON-IND / Halol Packaging Line
resolutionconflictingconflictconflictingapprovalapproved
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 satisfiedresolutionresolvedconflictstableapprovalpending
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
Current context will not automatically be applied to a delayed historical observation.
Alternate path. Stewards disagree: open the conflict case and leave the binding pending until it is decided.
not yet satisfiedOperates onBIND-003/in/qc-results-2026-09.csv → canonicalBinding· OPTIMON-IND / Halol Packaging Line
resolutionconflictingconflictconflictingapprovalapproved
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: conflict = conflicting, resolution = pending
Workflow as specified
CoreSync will request the context effective when the event occurred and retain the context snapshot/version used for admission.
Evidence written in this session
Nothing run yet in this session. Record state shown above may already satisfy steps from the seeded fixture history.