FA-12706 / Auction allocation rules / Open access

A block request receives a forbidden partial allocation · case 01

A block request receives a forbidden partial allocation.

Verified by executionVariant 1 · 6 checks per implementationDownload source bundle ↓JSON ↗

ROOT CAUSE

Capacity is consumed by clipping an indivisible request.

THE FAILURE

Capacity is consumed by clipping an indivisible request.

Unsuccessful approach: Stopping at the first oversized block prevents later smaller blocks from fitting.

Case contract

Process positive block sizes in submitted priority order. Accept a whole block if it fits remaining nonnegative capacity; otherwise skip it. Return accepted input indices.

Why this case matters

Deterministic teaching model for reviewing auction allocation software; not a representation of any venue or financial advice.

1 / The failure

Exit 1

"""Failure Map reference implementation. Python standard library only."""
import json

N = 1
observations = []
def solve(sizes, capacity):
    result=[]
    for i,size in enumerate(sizes):
     if capacity>0:
      result.append(i); capacity-=min(size,capacity)
    return result
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('skip oversized first', solve([10+N,2,1], 3), [1,2])
check('exact capacity', solve([2,3], 5), [0,1])
check('later smaller fits', solve([3,4,1], 4), [0,2])
check('no capacity', solve([1], 0), [])
check('empty', solve([], 5), [])
check('all too large', solve([5,6], 4), [])
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)

Boundary fixture	Actual	Expected	Outcome
skip oversized first	`[0]`	`[1, 2]`	Failed
exact capacity	`[0, 1]`	`[0, 1]`	Passed
later smaller fits	`[0, 1]`	`[0, 2]`	Failed
no capacity	`[]`	`[]`	Passed
empty	`[]`	`[]`	Passed
all too large	`[0]`	`[]`	Failed

SHA-256 / 785cd756cf4547831fe460757b932b19e6289085313f560139f4fbda01db33a7

2 / The unsuccessful fix

Exit 1

"""Failure Map reference implementation. Python standard library only."""
import json

N = 1
observations = []
def solve(sizes, capacity):
    result=[]
    for i,size in enumerate(sizes):
     if size>capacity: break
     result.append(i); capacity-=size
    return result
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('skip oversized first', solve([10+N,2,1], 3), [1,2])
check('exact capacity', solve([2,3], 5), [0,1])
check('later smaller fits', solve([3,4,1], 4), [0,2])
check('no capacity', solve([1], 0), [])
check('empty', solve([], 5), [])
check('all too large', solve([5,6], 4), [])
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)

Boundary fixture	Actual	Expected	Outcome
skip oversized first	`[]`	`[1, 2]`	Failed
exact capacity	`[0, 1]`	`[0, 1]`	Passed
later smaller fits	`[0]`	`[0, 2]`	Failed
no capacity	`[]`	`[]`	Passed
empty	`[]`	`[]`	Passed
all too large	`[]`	`[]`	Passed

SHA-256 / eaccb06a32e6b826357d3beba68c97ccfc35dce0f5d6445ae5d611af44f42ee6

HELD IN THE MEMBER ARCHIVE

The verified repair and its recorded checks are member-only.

This mechanism has 6 recorded checks per implementation. The open-access tier publishes the failure and the unsuccessful fix; the repaired source that passes every check, and the observations that prove it, are available to members.

Every case sharing this mechanism uses the same contract and the same repair, so this one record is held back for all of them.

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

Verification & scope

Offline toy model with explicit integer inputs; no strategic behavior or real market execution. This reproducer isolates one failure mechanism. Results cover the supplied fixtures. Variants within a family share a test contract and should remain grouped when constructing evaluation splits. Related mechanisms with a shared evaluation_group must also remain together; these controlled models are not independent production incidents.

Observations recorded using Python 3.12.14 at 2026-09-29T14:38:59.429330+00:00.

Case digest / 92e975c8d67374c1ab65a7921ea9b9a0271d82c33c343ed0b54a690a32c59bfc