The Gold Standard · Experimental Design
Make the decision path visible
Source-platform decommissioning can be technically complete and scientifically fragile. A retained disk may outlive the exception that justified it, documentation may still point to a retired runtime, or a later reviewer may discover that the destination cannot reconstruct a material figure from the frozen record. The old platform is gone, but the evidence boundary has drifted.
The gold standard separates media retention, security disposition and scientific reconstruction. It expires exceptions deliberately, preserves the smallest justified evidence set and opens a controlled recovery route when reconstruction fails, without treating the retired source as an informal fallback.
Choose the route closest to your decision
Chapter contents
Chapters 1–3
Chapters 4–6
Chapters 7–9
Chapters 10–12
CHAPTER 1 OF 12 · DEFINE EVIDENCE AFTER RETIREMENT
1. Define decommissioning evidence assurance
Record what proves identities, jobs, routes and live storage are retired, and what frozen data, code, environment and metadata preserve the study.
Security closure and scientific reconstructability are related but distinct outcomes.
CHAPTER 2 OF 12 · DEFINE EVIDENCE AFTER RETIREMENT
2. Bound retained-media exceptions
Give each retained medium an owner, purpose, contents, location, access rule, review date, expiry and planned disposition.
Retention without a current purpose becomes unmanaged capability and uncertain evidence.
Evidence check
Check whether the scope, owner and decision consequence are explicit before continuing.
CHAPTER 3 OF 12 · DEFINE EVIDENCE AFTER RETIREMENT
3. Set a reconstruction-failure route
Define who may declare failure, preserve diagnostics, approve bounded recovery, access retained evidence, compare results and decide claim consequence.
The route should make recovery possible without silently restoring ordinary source-platform authority.
| Layer | Evidence |
|---|---|
| Identity | Denial test |
| Jobs | Scheduler closed |
| Storage | Disposition record |
| Study | Reconstruction packet |
CHAPTER 4 OF 12 · DETECT DRIFT AND FAILURE
4. Recognise evidence drift after decommissioning
Look for expired exceptions, unreadable media, missing keys, undocumented exports, broken environment manifests, destination changes and reconstruction tests that no longer pass.
Evidence drift often appears long after the platform appears successfully retired.
CHAPTER 5 OF 12 · DETECT DRIFT AND FAILURE
5. Test retained media and destination independently
Verify media identity, integrity, readability and access controls, then reconstruct a selected material output on the approved destination from documented inputs.
A readable disk does not prove the study is reproducible, and a working destination does not justify indefinite media retention.
Evidence check
Ask a second reviewer to reconstruct the example from the preserved evidence and stated assumptions.
CHAPTER 6 OF 12 · DETECT DRIFT AND FAILURE
6. Worked example: retained snapshot expires as reconstruction fails
A research team retains an encrypted source snapshot for twelve months while validating the destination. The exception expires unnoticed. Eighteen months later, a material figure cannot be rebuilt because a package lockfile and calibration export are absent from the destination.
Governance quarantines the snapshot, records the expired exception and authorises read-only extraction of the two missing artefacts in an isolated environment. Changed-context check: the medium should be sanitised without reopening when the missing output is non-material and the approved record already supports every published claim.
| Field | Requirement |
|---|---|
| Purpose | Named evidence need |
| Contents | Verified inventory |
| Access | Bounded readers |
| Expiry | Review and disposition |
CHAPTER 7 OF 12 · RECOVER WITHOUT REVIVAL
7. Contain expired media and failed outputs
Suspend routine access, preserve chain-of-custody and diagnostics, quarantine disputed outputs and prevent the retained medium from reconnecting to current data or production destinations.
Containment protects both confidentiality and the evidential value of the recovery attempt.
CHAPTER 8 OF 12 · RECOVER WITHOUT REVIVAL
8. Recover the minimum reconstruction evidence
Extract only approved missing artefacts, verify hashes and provenance, update the frozen manifest and rebuild the output on the destination. Document every transformation.
Recovery should shrink uncertainty without recreating a broad historical environment.
Evidence check
Verify that the control still reaches the intended decision under a changed but plausible context.
CHAPTER 9 OF 12 · RECOVER WITHOUT REVIVAL
9. Review scientific consequence
Compare recovered, destination and published outputs. Classify claims as unchanged, qualified, corrected or unresolved, and preserve the reasoning behind the decision.
A reconstruction failure is not automatic proof that the original result was false, but it is evidence that assurance needs repair.
| Step | Control |
|---|---|
| Declare | Material output named |
| Diagnose | Logs preserved |
| Extract | Minimum artefacts |
| Rebuild | Destination only |
CHAPTER 10 OF 12 · CLOSE WITH TESTED ASSURANCE
10. Decide media disposition and exception closure
After recovery, choose sanitisation, documented archival retention or a renewed bounded exception. Require independent approval and a new expiry for any retained medium.
An exception cannot be renewed merely because a deletion decision feels uncomfortable.
CHAPTER 11 OF 12 · CLOSE WITH TESTED ASSURANCE
11. State limits and common misconceptions
Some obsolete software cannot be made durable, infrastructure administrators may retain unavoidable capability and sanitisation proves data-access treatment rather than methodological validity.
Record residual dependencies and separate confidentiality evidence from scientific evidence.
Evidence check
Confirm that versions, notices and unresolved limits remain visible in the final record.
CHAPTER 12 OF 12 · CLOSE WITH TESTED ASSURANCE
12. Monitor post-decommissioning assurance
Retest material reconstructions after destination, identity, storage or retention changes. Review exceptions before expiry and track unresolved outputs and media disposition.
The gold standard keeps the source retired while ensuring the evidence needed to understand the study remains usable and governed.
| Result | Disposition |
|---|---|
| Exact reproduction | Assurance restored |
| Immaterial variance | Explain tolerance |
| Material change | Correct or qualify |
| Still unresolved | Keep review open |
Frequently asked questions
What is decommissioning evidence drift?
It is divergence between the evidence and controls originally used to justify retirement and the current ability to prove closure and reconstruct material study outputs.
May expired retained media be opened?
Only through a newly authorised, bounded route when a justified evidence need outweighs the risk and current controls prevent broader revival.
Does reconstruction failure invalidate the study?
Not automatically. It requires a documented review of the missing evidence, output variance and consequence for each material claim.
When can retained media be sanitised?
When retention duties and justified reconstruction needs are satisfied, disposition is approved and the evidence required for future understanding is preserved elsewhere.
Continue through verified routes
Core routes
Experimental Design subject root · Gold Standard of Education · Gold Standard directory · How X Works hub
Specialist routes
- Final-isolation surveillance drift, emergency access and source-platform decommissioning assurance
- Historical-environment final isolation, migration survival and dormant credentials
- Historical-environment drift, export-control breaches and re-containment
- Exception-register expiry, orphaned owners and reauthorisation evidence