Commit authorization with dispatch intent and queue a record pointer

Context

Application delivery occurs outside the transaction that authorizes it.

Decision

Retain authorization and a dispatch entry together, then publish a pointer that the worker resolves from current records.

Alternatives Considered

Publish while authorization is being committed. Publication during authorization can outlive rollback of the authorization transaction.

Store the delivery payload in each queue item. A retained payload can become stale; the current pointer lets the worker load present records.

Dispatch only when a nudge succeeds. A lost nudge needs another dispatch opportunity from the schedule.

Consequences

Dispatch tolerates duplicate publication. The minute schedule supplements a failed nudge without establishing a maximum delay. Platform-standard authority remains unverified.