Most identifiers belong to one method

Code deposits are common. Shared data are not. An identifier that appears in only one study leaves the next study with an output, not a task it can inherit. Registering the state profiles, perturbation representations, and reference networks a method was fitted on is what lets a later method start from the same objects.

A network reused across studies, such as the T-LGL network cited by several Class C3 methods, can circulate without a persistent identifier. The same gap sits under the inverse-task benchmark: a frozen source–target pair needs a dataset more than one method can be scored on. Per-method validation evidence and code deposits are on each method page and on the reproducibility audit.