FAILURE MAP
← Case archive

FA-744 / Queues / Member archive

Accept a durable queue publication: A fenced producer continues publishing · case 04

The queue publish operation is admitted even though a fenced producer continues publishing.

Member previewVariant 4 · 3 implementations · 9 checks per implementation

Case contract

Return a Boolean admission decision for accept a durable queue publication. The record r must satisfy all of: len(r['message_size'][0]) <= r['message_size'][1]; r['queue_capacity'][0]+r['queue_capacity'][1] <= r['queue_capacity'][2]; bool(r['routing_target']); r['producer_epoch'][0] == r['producer_epoch'][1]; r['sequence_next'][0] == r['sequence_next'][1]+1. Extra tracing fields are ignored; validation does not mutate the record.

Why this case matters

A deterministic local contract for queues. Each negative fixture violates exactly one invariant. No transport timing, persistence, cryptographic verification, or full protocol implementation is claimed.

One recorded failure

Sample boundary fixture

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

Boundary fixtureActualExpectedOutcome
A fenced producer continues publishingtruefalseFailed

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.

Sign in to the archive ↗