OptimonCoreSync Studio
IE
CS-PUB-004 · PUB Publication, subscriptions and Unified Namespace · 132 of 192

Preserve declared ordering and partition scope

Data Engineer · Trigger: A consumer depends on sequence within a subject or key.

Simulated fixture data. Every record, receipt and timeline entry on this screen is demonstration material. It is never production evidence.

Acceptance

0 of 3 steps satisfied

Reordered test inputs will produce the declared key-level behavior and explicit gaps where required.

Run the remaining steps below. The result is read back from record state — nothing here is a toast.

Normal path

Data is published under contract, entitled, and confirmed as actually consumed.
Step 1. Publish the topic under its contract.
not yet satisfied
Operates onPUBL-004uns/shf/energy/4Publication· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
stateretireddeliveryHealthfailedentitlementgranted
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: state = published
Step 2. Grant the entitlement the consumer needs.
not yet satisfied
Operates onPUBL-011uns/hal/heat/11Publication· OPTIMON-IND / Halol Packaging Line
statepublisheddeliveryHealthhealthyentitlementreview
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: entitlement = granted
Step 3. Activate the subscription and confirm receipts, not just delivery.
not yet satisfied
Operates onSUBS-018Traceability app → uns/ngd/qcSubscription· OPTIMON-IND / Nagda Warehouse
statependingacceptancepartialentitlementgranted
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: state = active

Exception path

Global ordering will not be inferred across independent partitions or uncertain clocks.
Alternate path. The consumer did not accept: request redelivery; consumption history is preserved.
not yet satisfied
Operates onSUBS-004Partner BI → uns/shf/energySubscription· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
staterevokedacceptancerejectedentitlementexpired
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: acceptance = partial

Workflow as specified

CoreSync will apply approved partition keys, retain source/canonical sequence metadata and disclose the scope within which ordering is provided.

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