Shared workflow action configuration service
What the Service Owns
This service owns reusable action and workflow templates, calendars, declarations and automation configuration. Runtime execution belongs to each host; shared views make host-owned runs and timers available for inspection.
Operations
The operation rows define the callable boundary, its access class, exact permission declarations and planning coverage. Configuration and operational administration are not published as intake captures. Public health and provider callbacks retain their declared access boundaries.
Consistency and Failure
Registry replacement commits the complete manifest or retains the previous registry. A refused replacement changes no registry entries.
Publication locks the rule and draft, freezes the version and changes the current pointer atomically. A failed publish leaves the prior rule and draft intact.
Choosing a default calendar clears competing defaults within the same transaction. A failed edit retains the prior default selection.
Hosts load current configuration on their next read; already-computed timers retain their scheduled instants. Configuration edits do not reschedule existing timers.
Events and Jobs
The declarations distinguish application events, incoming requests, queue work and direct host reads. These are different transport boundaries; registering a declaration does not by itself publish an application event.
Open Questions
There is no connected workflow configuration screen in this scope. Cross-host view rebuilding omits hosts whose declared views are absent; inspection does not dynamically recover those rows. No scoped operation calls a language model.