Handing the analysis to someone else, including future you

1 · Learn the move · Red-team audit

The area's done-check is blunt: a colleague reproduces one figure from the repository alone. Not the repository plus a phone call, plus the path only you know. The red-team audit finds the gaps before the colleague does: the model plays a competent scientist who cloned your repo cold - same field, zero context - and walks the reproduction step by step, failing loudly at every wall. Absolute paths that exist on one laptop. Data the manifest names but nothing says how to obtain. An environment file missing or stale. A README whose steps skip the one you do by muscle memory. Each failure becomes a fix; the audit repeats until the walkthrough runs clean. This is the PI answer in miniature: a chat transcript defends nothing, but a repository that survives this audit is a methods section that runs.

Red-team my repository for cold reproduction. You are a scientist in my field who cloned [repo] with zero context - here is the file listing and README: [paste]. Walk the attempt to regenerate [figure/result] step by step, in order, and fail loudly at each wall: missing environment, unobtainable data, absolute paths, undocumented steps, scripts whose order is unstated. For each failure: what you hit, what information you lacked, the smallest fix. Rank fixes by what blocks first. Do not be polite about muscle-memory steps I forgot to write down - finding them is the job.