FA-103 / Distributed coordination / Member archive

An aborted transaction publishes an external event · case 03

An event escapes before its associated business state commits, or committed events disappear before dispatch.

Member previewVariant 3 · 3 implementations · 7 checks per implementation

Case contract

Actions are ['stage',ID,value], ['commit'], ['rollback'], or ['dispatch']. Stage replaces an uncommitted pending write; commit atomically stores its value and appends its event; rollback discards pending work. Dispatch publishes each locally pending committed event once. IDs are unique per committed transaction. Return [business value,published event IDs]. No transport crash or exactly-once external-delivery guarantee is modeled.

Why this case matters

Models the database-to-message-broker boundary and why a relay needs a committed durable outbox, while explicitly excluding the separate problem of duplicate deliveries after relay crashes.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
rollback cannot publish	`[null, ["a"]]`	`[null, []]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.