Make two runs prove they used the same evidence
one move: name every cause
Open the code pane immediately, then use the Spec tab, optional design question, tests, and artifact when you want them.
Finish each move before carrying the artifact forward.
An experiment is evidence only when configuration, seed, data identity, and code version can be reconstructed.
Deliverable: State the invariant in one sentence.Create a stable run key from a config object, ordered dataset IDs, and a random seed without relying on process hash order.
Deliverable: Type the smallest deterministic implementation.Equivalent inputs produce the same key; changing one cause changes the key and leaves inputs untouched.
Deliverable: Record a normal case and a boundary case.Reorder config keys, change one hyperparameter, and use a different dataset split.
Deliverable: Name the failure signal and the guard you would add.A reproducibility manifest and a one-cause-at-a-time experiment table.
Deliverable: Save the contract, evidence, and handoff note.Equivalent inputs produce the same key; changing one cause changes the key and leaves inputs untouched.
Reorder config keys, change one hyperparameter, and use a different dataset split.
A reproducibility manifest and a one-cause-at-a-time experiment table.
Deriva-authored extension beyond the supplied PDF. The five moves are Deriva’s implementation contract for this project.