OptimonCoreSync Studio
IE
CS-PUB-002 · PUB Publication, subscriptions and Unified Namespace · 130 of 192

Route data to multiple authorized consumers

Integration Engineer · Trigger: A canonical stream supports several services.

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 satisfied

Fan-out tests will show per-consumer receipts and policy-correct payloads.

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-002uns/ngd/bale/2Publication· OPTIMON-IND / Nagda Warehouse
statedraftdeliveryHealthdegradedentitlementreview
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.
satisfied
Operates onPUBL-009uns/rgh/energy/9Publication· OPTIMON-IND / Raigarh Melt Shop
statepublisheddeliveryHealthhealthyentitlementgranted
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-016Yield app → uns/shf/heatSubscription· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
staterevokedacceptancerejectedentitlementexpired
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: state = active

Exception path

One failed consumer will not silently erase successful deliveries or block unrelated consumers unless the contract requires it.
Alternate path. The consumer did not accept: request redelivery; consumption history is preserved.
satisfied
Operates onSUBS-002Energy app → uns/ngd/baleSubscription· OPTIMON-IND / Nagda Warehouse
statependingacceptancepartialentitlementgranted
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: acceptance = partial

Workflow as specified

CoreSync will apply declared routing, minimization and access policies separately for each consumer, tracking fan-out and independent delivery outcomes.

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.