Pranay Prakash 3064b8f13d Key the fence's sibling credit on a per-invocation writerId ...

Storm forensics (fence_count audit column) attributed every corrupted run
to a credit hole, not engine nondeterminism: two invocations that loaded
the identical prefix present byte-identical stateCursor+stateEventCount,
so the snapshot-keyed credit admitted both writers' decision batches and
their interleaved sets baked an order no replay derives (correlation
ordinals inverted against commit order at seqs the writers' fence_counts
prove they never saw).

The runtime now mints a random writerId per invocation delivery and sends
it with every precondition snapshot; the world's credit compares writerId
(falling back to stateCursor only for runtimes that don't send one). A
second writer with the same snapshot 412s and restarts against the
corrected log. Also adds the fence_count forensics column and a
WORKFLOW_POSTGRES_EVENT_FENCE=tail|decision experiment switch.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-29 17:10:46 -07:00

..

event-ordering.test.ts

Key the fence's sibling credit on a per-invocation writerId

2026-07-29 17:10:46 -07:00

spec.test.ts

Disable postgres world tests running in win32, fix container setup for ubuntu (#215)

2025-11-04 18:27:08 -08:00

storage.test.ts

Assign commit-ordered event positions in world-postgres and fence stale writers

2026-07-29 15:11:18 -07:00