The research question
A workflow definition is copied to three laptops for collaboration. If each installation enables the same scheduled trigger, one intended customer reminder can become three messages. The duplication arises before ordinary event retry logic: each device believes it owns an independent legitimate trigger because activation was bundled with sharing the definition. Weakly connected-system research distinguishes tentative work from stabilized results. The proposed execution design adds business authorization and observable outcomes, because exchanging a record cannot by itself establish that an external action happened correctly.
A concrete design choice
The proposed package separates definition, local configuration and execution ownership. Ordinary replicas can inspect and propose changes while timers, webhooks and external credentials remain inactive. The designated executor activates a reviewed version through an explicit operation. A definition update does not automatically change a running workflow until compatibility and approval checks pass. The interface should show where the workflow is active and which version is executing. A device that becomes the executor through a controlled handover registers its own secrets and reconciles prior receipts rather than inheriting an opaque copied runtime directory.
What would demonstrate usefulness
Replicate a scheduled workflow to several devices and inspect active triggers, credential stores and resulting effects. Then update the definition while one instance is running. Confirm that only the intended executor activates the approved version and that ordinary synchronization never creates another live schedule or webhook endpoint.