FA-6001 / Linear algebra / Open access

Vector dot product · case 01

The product of sums introduces cross-coordinate products.

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

ROOT CAUSE

The product of sums introduces cross-coordinate products.

THE FAILURE

The product of sums introduces cross-coordinate products.

Unsuccessful approach: Corresponding coordinates are added rather than multiplied.

Case contract

Integer matrix/vector entries, rectangular rows, compatible multiplication dimensions, and square matrices for determinant, trace, inverse, symmetry and characteristic-polynomial operations. Rational matrix outputs are reduced Fraction strings. Vector dot product. Exact operational definition: sum(x*y for x,y in zip(a,b))

Why this case matters

Small exact fixtures expose this error without platform timing, external services, or probabilistic observations. Linear algebra results depend on the stated convention.

1 / The failure

Exit 1

"""Failure Map reference implementation. Python standard library only."""
import json
import math
import calendar
import statistics
import itertools
from fractions import Fraction
from datetime import date, datetime, timedelta, timezone
from decimal import Decimal, ROUND_HALF_UP, ROUND_DOWN, ROUND_CEILING, ROUND_FLOOR

N = 1
observations = []
def solve(a, b):
    return sum(a)*sum(b)
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('fixture 1: ([1, 2], [3, 4])', solve(*([1, 2], [3, 4])), 11)
check('fixture 2: ([1, -1], [1, 1])', solve(*([1, -1], [1, 1])), 0)
check('fixture 3: ([], [])', solve(*([], [])), 0)
check('fixture 4: ([0, 2], [5, 0])', solve(*([0, 2], [5, 0])), 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 fixture	Actual	Expected	Outcome
fixture 1: ([1, 2], [3, 4])	`21`	`11`	Failed
fixture 2: ([1, -1], [1, 1])	`0`	`0`	Passed
fixture 3: ([], [])	`0`	`0`	Passed
fixture 4: ([0, 2], [5, 0])	`10`	`0`	Failed

SHA-256 / e563699893836623addaaeb495d3da302303488fe9168695dc44ca125546ce2f

2 / The unsuccessful fix

Exit 1

"""Failure Map reference implementation. Python standard library only."""
import json
import math
import calendar
import statistics
import itertools
from fractions import Fraction
from datetime import date, datetime, timedelta, timezone
from decimal import Decimal, ROUND_HALF_UP, ROUND_DOWN, ROUND_CEILING, ROUND_FLOOR

N = 1
observations = []
def solve(a, b):
    return sum(x+y for x,y in zip(a,b))
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('fixture 1: ([1, 2], [3, 4])', solve(*([1, 2], [3, 4])), 11)
check('fixture 2: ([1, -1], [1, 1])', solve(*([1, -1], [1, 1])), 0)
check('fixture 3: ([], [])', solve(*([], [])), 0)
check('fixture 4: ([0, 2], [5, 0])', solve(*([0, 2], [5, 0])), 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 fixture	Actual	Expected	Outcome
fixture 1: ([1, 2], [3, 4])	`10`	`11`	Failed
fixture 2: ([1, -1], [1, 1])	`2`	`0`	Failed
fixture 3: ([], [])	`0`	`0`	Passed
fixture 4: ([0, 2], [5, 0])	`7`	`0`	Failed

SHA-256 / 587370f6aa3a432028c0bceb2fba5b4ffd92bf57891643729ae24df49dcd07e7

HELD IN THE MEMBER ARCHIVE

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

This mechanism has 4 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

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:37:56.244780+00:00.

Case digest / 391016b32a958a5284ec8f88aebb4d0b65b919b713aac1256ef38254c3a8ad3a