FA-503 / Consensus / Member archive

Accept a proposal value: A value is accepted below the promised ballot · case 03

The acceptor accept operation is admitted even though a value is accepted below the promised ballot.

Member previewVariant 3 · 3 implementations · 9 checks per implementation

Case contract

Return a Boolean admission decision for accept a proposal value. The record r must satisfy all of: tuple(r['ballot_promised'][0]) >= tuple(r['ballot_promised'][1]); r['ballot_value_unique'][0] is None or r['ballot_value_unique'][0] == r['ballot_value_unique'][1]; r['slot_untrimmed'][0] > r['slot_untrimmed'][1]; len(r['value_length'][0]) <= r['value_length'][1]; r['accept_persisted'] is True. Extra tracing fields are ignored; validation does not mutate the record.

Why this case matters

A deterministic local contract for consensus. 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 fixture	Actual	Expected	Outcome
A value is accepted below the promised ballot	`true`	`false`	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.