Workflow task requests use service invocation and current-state repeat handling

Context

Workflow callers need a bounded way to act on task work. Their external delivery and retry policy is outside the inspected CRM implementation.

Decision

The service dispatcher validates a declared operation set. Creation carries an action-origin reference; later changed requests use row serialization and already-satisfied checks. Workflow creation omits queue, status and client record identifier inputs.

Alternatives Considered

The structured alternatives describe concrete competing designs and their tradeoffs. Where the origin records an existing ruling, it remains the authority; an observed implementation does not establish Product’s rejection of every alternative.

Consequences

Creation deduplication is limited to retained origin references. Later commands do not promise exactly-once effects across intervening changes, and end-to-end executor behavior remains unverified.