FA-12336 / Battery state accounting / Open access

Balancing credits the receiver without debiting losses · case 01

Transfer loss is ignored while moving inventory between cells.

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

ROOT CAUSE

Transfer loss is ignored while moving inventory between cells.

THE FAILURE

Transfer loss is ignored while moving inventory between cells.

Unsuccessful approach: Debiting only the received amount conserves charge that the model says was lost.

Case contract

For nonnegative inventories and even transfer no greater than donor inventory, return [donor,receiver,lost]; receiver has no capacity bound in this toy model and receives half the transfer.

Why this case matters

An explicit synthetic battery bookkeeping model isolates this state-accounting error; it is not an engineering prediction or safety procedure.

1 / The failure

Exit 1

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

N = 1
observations = []
def solve(donor, receiver, transfer):
    return [donor-transfer,receiver+transfer,0]
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('partial', solve(10*N,2*N,4*N), [6*N,4*N,2*N])
check('full', solve(10*N,0,10*N), [0,5*N,5*N])
check('zero', solve(10*N,2*N,0), [10*N,2*N,0])
check('empty', solve(0,0,0), [0,0,0])
check('receiver occupied', solve(8*N,9*N,2*N), [6*N,10*N,N])
check('small transfer', solve(10*N,2*N,2), [10*N-2,2*N+1,1])
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
partial	`[6, 6, 0]`	`[6, 4, 2]`	Failed
full	`[0, 10, 0]`	`[0, 5, 5]`	Failed
zero	`[10, 2, 0]`	`[10, 2, 0]`	Passed
empty	`[0, 0, 0]`	`[0, 0, 0]`	Passed
receiver occupied	`[6, 11, 0]`	`[6, 10, 1]`	Failed
small transfer	`[8, 4, 0]`	`[8, 3, 1]`	Failed

SHA-256 / a03626ffc909c16478e4ffdab1a530f907bb11f88b6b2340442060a66e791623

2 / The unsuccessful fix

Exit 1

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

N = 1
observations = []
def solve(donor, receiver, transfer):
    return [donor-transfer//2,receiver+transfer//2,transfer//2]
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('partial', solve(10*N,2*N,4*N), [6*N,4*N,2*N])
check('full', solve(10*N,0,10*N), [0,5*N,5*N])
check('zero', solve(10*N,2*N,0), [10*N,2*N,0])
check('empty', solve(0,0,0), [0,0,0])
check('receiver occupied', solve(8*N,9*N,2*N), [6*N,10*N,N])
check('small transfer', solve(10*N,2*N,2), [10*N-2,2*N+1,1])
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
partial	`[8, 4, 2]`	`[6, 4, 2]`	Failed
full	`[5, 5, 5]`	`[0, 5, 5]`	Failed
zero	`[10, 2, 0]`	`[10, 2, 0]`	Passed
empty	`[0, 0, 0]`	`[0, 0, 0]`	Passed
receiver occupied	`[7, 10, 1]`	`[6, 10, 1]`	Failed
small transfer	`[9, 3, 1]`	`[8, 3, 1]`	Failed

SHA-256 / 8d23446ae11ffa92db15dad589d1710cce1658e96ae1282be8d1ed338606fc66

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

Integer toy accounting with declared loss rules; no electrochemistry, hardware behavior, or safety claims. 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:56.015384+00:00.

Case digest / 8af9e391a1035622cebeb4f8fce12ff096a13838e285191767d4dbf69cf28338