OptimonCoreSync Studio
IE
CS-PUB-003 · PUB Publication, subscriptions and Unified Namespace · 131 of 192

Create and retire a consumer subscription

Data Consumer Owner · Trigger: A service starts or stops consuming a stream.

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

Acceptance

3 of 3 steps satisfied

Activation and retirement tests will preserve authorization and an explicit outstanding-work outcome.

Every step's expected record state is present. This is read back from the records, not asserted by the screen.

Normal path

Data is published under contract, entitled, and confirmed as actually consumed.
Step 1. Publish the topic under its contract.
satisfied
Operates onPUBL-003uns/hal/qc/3Publication· OPTIMON-IND / Halol Packaging Line
statepublisheddeliveryHealthhealthyentitlementgranted
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-010uns/ngd/defect/10Publication· OPTIMON-IND / Nagda Warehouse
statedraftdeliveryHealthdegradedentitlementgranted
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.
satisfied
Operates onSUBS-017Energy app → uns/rgh/baleSubscription· OPTIMON-IND / Raigarh Melt Shop
stateactiveacceptanceacceptedentitlementgranted
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: state = active

Exception path

An unapproved subscriber will not read data by guessing a channel name.
Alternate path. The consumer did not accept: request redelivery; consumption history is preserved.
not yet satisfied
Operates onSUBS-003Traceability app → uns/hal/qcSubscription· OPTIMON-IND / Halol Packaging Line
stateactiveacceptanceacceptedentitlementreview
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: acceptance = partial

Workflow as specified

CoreSync will register consumer identity, contract compatibility, start position, retention expectations and permitted filters, then manage lifecycle and backlog disposition.

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