FA-12361 / Manufacturing workflow integrity / Open access
An in-process lot silently adopts a revised route · case 01
An in-process lot silently adopts a revised route.
ROOT CAUSE
The route resolver always chooses the newest engineering revision.
THE FAILURE
The route resolver always chooses the newest engineering revision.
Unsuccessful approach: Always using the frozen revision ignores an authorized migration.
Case contract
Given a revision-to-route mapping, frozen revision and optional migration revision, return that exact route or None if absent. No fallback is allowed.
Why this case matters
A deterministic manufacturing record model isolates this workflow defect before equipment or enterprise integration.
1 / The failure
Exit 1"""Failure Map reference implementation. Python standard library only."""
import json
N = 1
observations = []
def solve(routes, frozen, migration):
return routes[max(routes)] if routes else None
def check(label, actual, expected):
observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
r = {N: ['wash'], N+1: ['wash', 'inspect']}
check('frozen route', solve(r, N, None), ['wash'])
check('explicit migration', solve(r, N, N+1), ['wash', 'inspect'])
check('missing migration', solve(r, N, N+2), None)
check('missing frozen revision', solve(r, N-1, None), None)
check('current frozen', solve(r, N+1, None), ['wash', 'inspect'])
check('no revisions', solve({}, N, None), None)
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 |
|---|---|---|---|
| frozen route | ['wash', 'inspect'] | ['wash'] | Failed |
| explicit migration | ['wash', 'inspect'] | ['wash', 'inspect'] | Passed |
| missing migration | ['wash', 'inspect'] | None | Failed |
| missing frozen revision | ['wash', 'inspect'] | None | Failed |
| current frozen | ['wash', 'inspect'] | ['wash', 'inspect'] | Passed |
| no revisions | None | None | Passed |
SHA-256 / 18ee572080616e5af957a50eb6c81295a6ada8003681be4fcb97bf715b412755
2 / The unsuccessful fix
Exit 1"""Failure Map reference implementation. Python standard library only."""
import json
N = 1
observations = []
def solve(routes, frozen, migration):
return routes.get(frozen)
def check(label, actual, expected):
observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
r = {N: ['wash'], N+1: ['wash', 'inspect']}
check('frozen route', solve(r, N, None), ['wash'])
check('explicit migration', solve(r, N, N+1), ['wash', 'inspect'])
check('missing migration', solve(r, N, N+2), None)
check('missing frozen revision', solve(r, N-1, None), None)
check('current frozen', solve(r, N+1, None), ['wash', 'inspect'])
check('no revisions', solve({}, N, None), None)
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 |
|---|---|---|---|
| frozen route | ['wash'] | ['wash'] | Passed |
| explicit migration | ['wash'] | ['wash', 'inspect'] | Failed |
| missing migration | ['wash'] | None | Failed |
| missing frozen revision | None | None | Passed |
| current frozen | ['wash', 'inspect'] | ['wash', 'inspect'] | Passed |
| no revisions | None | None | Passed |
SHA-256 / 3eaf2b832daff7c5abe78c1617a3beaef2af004b47e21a758f75c01d36db5bcf
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
Offline policy model only; no physical equipment, regulatory certification, or concurrent transaction 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.211539+00:00.
Case digest / 8930ae1dfd59d7eacef0c9d357fa382224699fea3e9dc459063f85b6f8696c7d