Received provider message processing

The Lifecycle

Transitions Explained

Ingress creates queued message records, and workers claim numbered attempts before verification. Verified interpretation commits events; rejected signatures and duplicates create no events. Replay is a separate creation flow using the retained body, not an outgoing transition of the original record.

What Cannot Happen

Settled message records are not processed again in place; replay creates another message. A dead record remains historical; its retained body can supply a new replay record.

Concurrency and Timing

Ingress stores bodies before committing message and dispatch records. Worker attempts are claimed by their number and terminal repeats are skipped. Replay bypasses input deduplication and can create another interpreted event after the original processing.