Make the deployment independent of your workstation
What This Concept Is
A clean-room run starts from a declared baseline without relying on hidden local caches, credentials or manually created resources. It tests reproducibility of the documented path, not just the author’s memory.
Why It Matters Here
The original empty-state exercise needs a precise boundary: a fresh checkout is not necessarily a fresh runtime or state backend.
Concrete Example
A second operator receives a revision, dependency/tool versions, synthetic seed procedure and scoped access process. They must not receive the author’s home directory. A missing environment variable or preexisting database reveals an undocumented dependency. Record failure and repair before the successful rerun.
Common Confusion / Misconception
Reproducibility does not require publishing secrets. A cached image that bypasses the build can conceal missing dependencies; a reused database can conceal missing migrations.
How To Use It
Declare what is preinstalled, what is provisioned, what is retrieved and what is intentionally external. Record the exact revision/digest and all deviations. Use a separate disposable target; never reset a shared environment to claim cleanliness.
Check Yourself
What hidden state remains? Which credentials are provisioned through a controlled path? Can the second operator identify the target?
Mini Drill or Application
Ask the original reviewer/operator to follow the runbook. Preserve one friction point and fix it. If no operator is available, mark independent reproduction pending.
Read This Only If Stuck
Building Secure and Reliable Systems provides selective operational reasoning. Use the module sources below for current tool behavior; do not read a whole book before attempting the exercise.