Apply workflow task requests with repeat handling
What It Does
The service route gives workflow callers a bounded set of task operations without an HTTP interface. Creation uses an action-origin reference for deduplication. Other commands use current-state repeat checks, so their behavior differs from global exactly-once delivery.
The Flow
The numbered hops specify the request, persistence and integration boundaries in order. Each hop identifies its evidence anchor, synchronization seam and observable failure outcome. Branches distinguish optional and delegated paths.
When Something Fails
Local errors and coded refusals return to the workflow caller. Already-satisfied service requests return before change-only locking and lifecycle restrictions. The external executor’s retry policy and interpretation of refused actions remain integration evidence requirements.
Open Design Questions
The registered caller allowlist and executor behavior need external proof before workflow readiness is accepted.