The Gold Standard · Experimental Design
Make the decision path visible
Late provenance evidence can reopen an adjudication and produce a new finding. The next problem is not merely to publish the better answer. Analysts, repositories and decision owners need to know which ruling now governs, which statements changed, which remain valid and what downstream work must be repaired.
The gold standard preserves the earlier adjudication, issues a linked superseding record, maps affected uses and verifies that corrected reasoning reaches every material decision without rewriting history.
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 · BUILD THE SUPERSEDING RECORD
1. Define the authority to supersede
Identify the adjudication body, reopening basis, governing procedure and effective date. State whether the new record replaces, narrows, confirms or partly reverses the earlier finding.
A later date alone does not create authority; the version relation must come from the recognised decision process.
CHAPTER 2 OF 12 · BUILD THE SUPERSEDING RECORD
2. Preserve the prior ruling as a historical version
Keep its evidence set, reasoning, confidence, dissent and decisions that relied on it. Mark it superseded for current use without making it disappear.
The earlier record explains why past actors acted as they did and supports later reconstruction.
Evidence check
Check whether the scope, owner and decision consequence are explicit before continuing.
CHAPTER 3 OF 12 · BUILD THE SUPERSEDING RECORD
3. Write a precise change statement
List each provenance claim, confidence category, uncertainty-set implication and decision limit that changed, plus findings that remain stable.
Avoid a broad corrected label that forces every reader to compare two long records unaided.
| Field | Record |
|---|---|
| Authority | Who decided? |
| Relation | Replace, narrow or confirm |
| Effective date | When current? |
| Prior version | Preserved link |
CHAPTER 4 OF 12 · MAP CONSEQUENCES
4. Map downstream uses of the earlier finding
Search reports, approvals, analyses, code parameters, model registries, dashboards, citations and decision logs. Include copied summaries that no longer link to the source.
The superseding record repairs decisions only if it reaches the places where the earlier conclusion acquired authority.
CHAPTER 5 OF 12 · MAP CONSEQUENCES
5. Prioritise by materiality and reversibility
Repair first where the changed finding can alter treatment comparisons, inclusion, policy, safety or other consequential choices. Lower-risk descriptive references may receive staged annotation.
Do not confuse visibility with consequence: a small internal control can matter more than a widely read historical note.
Evidence check
Ask a second reviewer to reconstruct the example from the preserved evidence and stated assumptions.
CHAPTER 6 OF 12 · MAP CONSEQUENCES
6. Worked example: the production weight package changes
The first adjudication judged package B best supported. Reopened review proves that production used package A, which expands the admissible uncertainty set and changes one subgroup decision while leaving the overall conclusion stable.
The superseding record states all three effects separately, reruns the subgroup analysis, corrects the decision brief and preserves the stable overall result. Changed-context check: if packages A and B produce identical material intermediates and conclusions, the record still corrects provenance but may not require a new decision outcome.
| Element | State |
|---|---|
| Provenance claim | Changed or stable |
| Confidence | Raised, lowered or same |
| Decision limit | Revised or retained |
| Dissent | Resolved or preserved |
CHAPTER 7 OF 12 · REPAIR DECISIONS
7. Rerun only the affected analytical chain
Use preserved inputs, validated code and the corrected package to reproduce changed intermediates and decision outputs. Keep a manifest linking old and new runs.
A full rerun may be prudent, but the repair record should still identify which assumptions were actually affected.
CHAPTER 8 OF 12 · REPAIR DECISIONS
8. Issue targeted downstream notifications
Tell each holder the governing version, changed finding, required action and deadline. Distinguish replacement, rerun, reconsideration and annotation.
A generic update notice can create unnecessary work while failing to repair the one decision that changed.
Evidence check
Verify that the control still reaches the intended decision under a changed but plausible context.
CHAPTER 9 OF 12 · REPAIR DECISIONS
9. Preserve dissent and residual uncertainty
Carry forward minority reasoning that remains relevant and explain whether the new evidence resolved or merely shifted the competing narratives.
Supersession improves the record; it does not manufacture certainty beyond the evidence.
| Use | Action |
|---|---|
| Model input | Rerun |
| Decision brief | Reconsider |
| Historical citation | Annotate |
| Current dashboard | Replace |
CHAPTER 10 OF 12 · SUSTAIN VERSION CONTROL
10. Detect mixed-version decision paths
Search for citations, hashes, package identifiers, copied language and output fingerprints from both adjudication versions. Block combinations that use the new conclusion with old assumptions.
Mixed versions can produce a result that neither ruling authorised.
CHAPTER 11 OF 12 · SUSTAIN VERSION CONTROL
11. Run a cross-system transfer check
Move the superseding record through a repository, analysis notebook, partner brief and archived report. Confirm that status, version relation and required action remain visible.
A supersession flag that disappears during export cannot control downstream use.
Evidence check
Confirm that versions, notices and unresolved limits remain visible in the final record.
CHAPTER 12 OF 12 · SUSTAIN VERSION CONTROL
12. Audit repair completion and future reopening
Track affected uses found, reruns, changed decisions, acknowledgement quality, stale citations, mixed-version outputs and unresolved holders. Define the evidence that would justify another reopening.
The gold standard makes correction durable by connecting versioned findings to the decisions they govern.
| Measure | Warning |
|---|---|
| Stale citation | Old ruling active |
| Mixed output | Versions combined |
| Unreconciled decision | Repair incomplete |
| Missing prior record | History erased |
Frequently asked questions
Should the old adjudication be deleted?
No. Preserve it as the historical record, clearly marked as superseded for current use and linked to the governing version.
Does a new provenance finding always change the final decision?
No. Recompute material intermediates and state separately which conclusions change and which remain stable.
What is the difference between correction and supersession?
Correction changes a finding; supersession also defines which version now governs and how the earlier record remains available.
How can mixed-version use be detected?
Search version identifiers, hashes, copied wording and output fingerprints, then trace them through repositories and decision records.
Continue through verified routes
Core routes
Experimental Design subject root · Gold Standard of Education · Gold Standard directory · How X Works hub
Specialist routes
- Late provenance evidence, adjudication reopening and correcting reconstruction records
- Reconstruction confidence, competing provenance narratives and independent adjudication
- Mixed-version provenance gaps, retroactive reconstruction and decision repair
- Version-reconciliation audit trails, reproducible cutovers and rollback