FAILURE MAP
← Case archive

FA-12276 / Power metering accounting / Open access

Reactive export quadrants are charged to the import register · case 01

Reactive export quadrants are charged to the import register.

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

ROOT CAUSE

Reactive sign alone is used without the active-power quadrant.

THE FAILURE

Reactive sign alone is used without the active-power quadrant.

Unsuccessful approach: Including nonnegative active power still assigns zero-active intervals to the import quadrant.

Case contract

Rows [active, reactive] are signed interval energies. Return positive reactive energy only from strictly positive active-import rows. Active zero belongs to no import quadrant. This is an explicit simplified quadrant tariff.

Why this case matters

Meter settlement depends on explicit register and tariff policies; this controlled model makes that policy observable.

1 / The failure

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

N = 1
observations = []
def solve(rows):
    return sum(max(q,0) for p,q in rows)
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('export quadrant excluded', solve([[-N,4*N]]),0)
check('zero active excluded', solve([[0,4*N]]),0)
check('import inductive included', solve([[N,4*N]]),4*N)
check('negative reactive excluded', solve([[N,-4*N]]),0)
check('mixed quadrants', solve([[N,N],[-N,N],[0,N],[N,-N]]),N)
check('empty', solve([]),0)
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 fixtureActualExpectedOutcome
export quadrant excluded40Failed
zero active excluded40Failed
import inductive included44Passed
negative reactive excluded00Passed
mixed quadrants31Failed
empty00Passed

SHA-256 / 756f80451dbda130be0a7d77c4d4654bab170bd47f941e6c32881f0ff2b3d0af

2 / The unsuccessful fix

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

N = 1
observations = []
def solve(rows):
    return sum(max(q,0) for p,q in rows if p>=0)
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('export quadrant excluded', solve([[-N,4*N]]),0)
check('zero active excluded', solve([[0,4*N]]),0)
check('import inductive included', solve([[N,4*N]]),4*N)
check('negative reactive excluded', solve([[N,-4*N]]),0)
check('mixed quadrants', solve([[N,N],[-N,N],[0,N],[N,-N]]),N)
check('empty', solve([]),0)
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 fixtureActualExpectedOutcome
export quadrant excluded00Passed
zero active excluded40Failed
import inductive included44Passed
negative reactive excluded00Passed
mixed quadrants21Failed
empty00Passed

SHA-256 / c32230a48237711744d11d14382f9c4e63993a0628a0dbe2637ad2e61a99a35b

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.

Sign in to the archive ↗

Verification & scope

Simplified integer-energy accounting model; no hardware protocol, legal tariff, measurement uncertainty, or live grid behavior is represented. 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:55.521403+00:00.

Case digest / 19065ca31d222ce499b0a407a987f52dc2f80f71f1572aac9709a73660390c0e