The Gold Standard · Experimental Design
Make the decision path visible
Exception closure often focuses on the medium everyone can see. A drive is sanitised, a certificate is verified and the reconstruction archive passes its test—yet a cloud snapshot, portable export or supplier recovery copy may remain outside the disposition record.
The gold standard treats discovery as a bounded challenge, not proof that every earlier action failed. It identifies the residual object, preserves necessary evidence, checks scientific and confidentiality consequences and closes each copy through a traceable authority decision.
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 · FRAME THE RESIDUAL-COPY CHALLENGE
1. Restate what reconstruction exception closure decided
Record the scientific need, preserved minimum, retained media, sanitised targets, certificates, residual exceptions and final authority.
A closure decision can be valid for the objects it knew. Later discovery asks whether scope changes, not whether every previous reviewer acted wrongly.
CHAPTER 2 OF 12 · FRAME THE RESIDUAL-COPY CHALLENGE
2. Define the newly discovered copy
Capture object identifier, location, owner, creation path, data classes, encryption, access history, relation to the experiment and current custody.
Terms such as old backup are insufficient. The decision depends on whether the object is identical, partial, transformed or linked to missing provenance.
Evidence check
Check whether the scope, owner and decision consequence are explicit before continuing.
CHAPTER 3 OF 12 · FRAME THE RESIDUAL-COPY CHALLENGE
3. Predefine challenge and containment rules
Isolate a copy when access, authority or scope is uncertain. Preserve metadata and logs before modifying content, and name who can decide retention, extraction or sanitisation.
Containment should prevent use without destroying evidence needed to understand how the copy escaped the original graph.
| Field | Evidence |
|---|---|
| Object | Unique identifier |
| Location | Custody |
| Creation | Source path |
| Content | Data class |
CHAPTER 4 OF 12 · RECONSTRUCT THE COPY GRAPH
4. Reconstruct the complete copy graph
Trace source platform, snapshots, backups, exports, removable media, supplier recovery stores, legal holds and validated archives.
For each edge, record who created it, why, when, through which tool and whether the destination inherited deletion or retention rules.
CHAPTER 5 OF 12 · RECONSTRUCT THE COPY GRAPH
5. Test the sanitisation record against its actual scope
Verify target identity, method, execution, review and certificate while distinguishing objects the certificate never claimed to cover.
A valid drive certificate should remain valid when an unrelated cloud copy is found. The governance gap is the missing object, not necessarily a false certificate.
Evidence check
Ask a second reviewer to reconstruct the example from the preserved evidence and stated assumptions.
CHAPTER 6 OF 12 · RECONSTRUCT THE COPY GRAPH
6. Worked example: a cloud snapshot survives a verified drive disposal
A portable drive is correctly sanitised and its certificate matches the device. Months later, a cloud administrator finds a snapshot created during reconstruction; it contains raw data and an obsolete environment image.
The snapshot is isolated, hashed and compared with the validated archive before disposition. Changed-context check: a storage-provider replica governed by the same logical sanitisation process may not be an independent residual copy when coverage and completion are verifiable; an unmanaged export is.
| Edge | Question |
|---|---|
| Snapshot | Policy inherited? |
| Export | Destination owned? |
| Supplier copy | Disposition bound? |
| Archive | Minimum validated? |
CHAPTER 7 OF 12 · DECIDE PRESERVATION AND DISPOSITION
7. Assess scientific value without assuming retention
Ask whether the copy contains material data, code, parameters, environment information or provenance absent from the validated archive.
Run the smallest safe reconstruction test. A copy that merely duplicates verified evidence does not gain scientific necessity from being surprising.
CHAPTER 8 OF 12 · DECIDE PRESERVATION AND DISPOSITION
8. Choose the least irreversible corrective action
Use controlled extraction, archive repair, time-limited retention, legal hold, appropriate sanitisation or documented deletion according to evidence and authority.
Do not reopen the entire historical platform when one missing provenance file can repair the archive.
Evidence check
Verify that the control still reaches the intended decision under a changed but plausible context.
CHAPTER 9 OF 12 · DECIDE PRESERVATION AND DISPOSITION
9. Close every linked exception
Update inventories, retention and disposition records for snapshots, exports, supplier copies and derived media. Give remaining exceptions owners and expiries.
Closing the newly discovered object while leaving the process that created it unchanged invites recurrence.
| Need | Response |
|---|---|
| Missing provenance | Controlled extraction |
| Duplicate evidence | Sanitise |
| Legal duty | Bounded hold |
| Unclear scope | Temporary isolation |
CHAPTER 10 OF 12 · VERIFY FINAL CLOSURE
10. Verify confidentiality and reconstruction separately
Have an independent reviewer sample the copy graph, certificates, exception records and archive reconstruction. Confirm that retired copies cannot serve data and preserved evidence still supports material results.
Neither test substitutes for the other. A secure archive may be scientifically incomplete, and a complete archive may expose unnecessary data.
CHAPTER 11 OF 12 · VERIFY FINAL CLOSURE
11. State limits and common misconceptions
No inventory proves that unknown copies never existed. Sanitisation makes target data infeasible to recover under a defined method; it does not validate the experiment.
A hash proves identity, not meaning. Discovery of one residual copy does not by itself invalidate every certificate or require permanent retention.
Evidence check
Confirm that versions, notices and unresolved limits remain visible in the final record.
CHAPTER 12 OF 12 · VERIFY FINAL CLOSURE
12. Monitor copy creation and future closure drift
Track snapshot policy, export logs, supplier recovery stores, inventory discrepancies, renewed exceptions and reconstruction after archive migration.
The gold standard closes both object and pathway: the residual copy is decided, the copy graph is repaired and genuinely new evidence retains a route back to review.
| Goal | Pass condition |
|---|---|
| Identity | Objects reconciled |
| Confidentiality | Retired copies unavailable |
| Science | Material result reconstructs |
| Governance | Exceptions current |
Frequently asked questions
What is reconstruction-exception closure drift?
It is divergence between the objects and pathways covered by the final closure decision and the copies or retention routes that later exist.
Does a residual cloud copy invalidate a drive certificate?
Not automatically. A certificate can be valid for its named target while the copy graph remains incomplete.
Must every discovered copy be retained for science?
No. Retention requires a bounded scientific, legal or records purpose that the validated archive cannot already satisfy.
What closes residual-copy discovery?
A reconciled copy graph, tested preservation minimum, appropriate disposition, independent verification and a repaired rule for future copies.
Continue through verified routes
Core routes
Experimental Design subject root · Gold Standard of Education · Gold Standard directory · How X Works hub
Specialist routes
- Sanitisation certificate verification and reconstruction exception closure
- Reconstruction evidence challenge and final sanitisation authority
- Provenance gaps and retained-media disposition appeal
- Retained-media exception expiry and reconstruction failure recovery