FAILURE MAP
← Case archive

FA-99238 / Checkpoint tensor mapping / Member archive

Checkpoint mapping: restoration plan ignores dependencies between aliases · case 03

restoration plan ignores dependencies between aliases.

Member previewVariant 3 · 3 implementations · 6 checks per implementation

Case contract

Steps are [name,depends_on]; return names in stable topological order, choosing lexical available names; cycle returns [].

Why this case matters

A bounded offline model of checkpoint tensor bookkeeping in a training workflow.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixtureActualExpectedOutcome
cycle["a", "b"][]Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

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

Sign in to the archive ↗