OptimonCoreSync Studio
IE
CS-PUB-001 · PUB Publication, subscriptions and Unified Namespace · 129 of 192

Publish an admitted canonical record

Integration Runtime Operator · Trigger: A record passes its canonical admission contract.

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

A record will have a verifiable publication outcome and retained failure evidence where acceptance fails.

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.
satisfied
Operates onPUBL-001uns/rgh/heat/1Publication· OPTIMON-IND / Raigarh Melt Shop
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.
not yet satisfied
Operates onPUBL-008uns/shf/qc/8Publication· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
stateretireddeliveryHealthfailedentitlementreview
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-015Corporate visibility → uns/hal/defectSubscription· OPTIMON-IND / Halol Packaging Line
stateactiveacceptanceacceptedentitlementreview
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: state = active

Exception path

Transport submission alone will not be labelled canonical acceptance.
Alternate path. The consumer did not accept: request redelivery; consumption history is preserved.
not yet satisfied
Operates onSUBS-001Yield app → uns/rgh/heatSubscription· OPTIMON-IND / Raigarh Melt Shop
stateactiveacceptanceacceptedentitlementgranted
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: acceptance = partial

Workflow as specified

CoreSync will publish through the approved backbone with authenticated scope, contract version, provenance and a receipt identifying the durable acceptance boundary.

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.