The Gold Standard · Archaeology
Make the decision path visible
Reinstatement can create a second correction problem. A repository may display the replacement claim while a review article, catalogue or teaching file loses the link that explains what changed. Readers then encounter confident wording without the corrected evidence path that justified it.
The gold standard treats version links as part of interpretation, not decoration. It reconstructs the dependency graph, validates the replacement against the current archive and re-withdraws only the unsupported wording while preserving traceable scholarly 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 · MAP THE DRIFT
1. Define the replacement claim that drifted
Record its exact wording, population, period, uncertainty, source version and the reinstatement decision that authorised its use.
Compare that bounded wording with current secondary uses. Expansion from seasonal preference to permanent specialisation is a substantive change, not a stylistic paraphrase.
CHAPTER 2 OF 12 · MAP THE DRIFT
2. Inventory every version and relation
List repository records, identifiers, landing pages, mirrors, supplements, cited datasets and known derivative works. Capture relations such as is-version-of, replaces and is-corrected-by.
A generic project identifier may resolve successfully while concealing which evidence version a claim used. Link health and semantic relation are separate checks.
Evidence check
Check whether the scope, owner and decision consequence are explicit before continuing.
CHAPTER 3 OF 12 · MAP THE DRIFT
3. Predefine a re-withdrawal trigger
Trigger review when a version relation disappears, a derivative cannot identify its source, wording exceeds the validated claim or corrected evidence no longer reproduces the inference.
The trigger protects the claim boundary. It does not require deletion of the archaeological record or automatic rejection of every related conclusion.
| Field | Record |
|---|---|
| Wording | Exact proposition |
| Population | Who or what |
| Period | Time range |
| Version | Evidence used |
CHAPTER 4 OF 12 · REBUILD THE GRAPH
4. Reconstruct the claim graph from primary evidence
Start with context, chronology, inventory, transformations and uncertainty, then connect each secondary statement to the evidence version it actually used.
Mark inferred links as uncertain rather than silently choosing the newest file. A citation date or filename alone may not prove which dataset was analysed.
CHAPTER 5 OF 12 · REBUILD THE GRAPH
5. Test the replacement under current evidence
Repeat the material analysis using the preserved method and current version. Vary plausible classifications, chronologies and aggregation rules to see which wording survives.
A replacement remains defensible only within the range supported by the corrected record. Later popularity does not compensate for lost provenance.
Evidence check
Ask a second reviewer to reconstruct the example from the preserved evidence and stated assumptions.
CHAPTER 6 OF 12 · REBUILD THE GRAPH
6. Worked example: a teaching repository restores the old conclusion
A teaching repository copies a replacement dataset but drops relation metadata during migration. Its lesson describes year-round specialisation, although the validated replacement supports only seasonal preference.
The repository restores the version graph, narrows the lesson and re-withdraws the expanded sentence. Changed-context check: a new seasonal assemblage may strengthen the narrower claim, but it cannot restore year-round specialisation unless recovery, chronology and density are comparable.
| Node | Relation |
|---|---|
| Withdrawn | Replaced by |
| Corrected | Corrects |
| Replacement | Uses version |
| Derivative | Cites claim |
CHAPTER 7 OF 12 · REPAIR DERIVATIVE USE
7. Repair version links in both directions
Connect obsolete, corrected and replacement records so a reader entering through any surviving route can discover current status and the reason for change.
Where systems cannot express formal relations, use visible status notes with exact identifiers. A working hyperlink without a stated relationship is not enough.
CHAPTER 8 OF 12 · REPAIR DERIVATIVE USE
8. Prioritise consequential secondary literature
Begin with syntheses, catalogues, educational resources and derived datasets that materially rely on the expanded claim. Supply replacement wording and the uncertainty that must travel with it.
Do not demand indiscriminate citation removal. The goal is to correct dependency, preserve legitimate historical discussion and stop unsupported present-tense use.
Evidence check
Verify that the control still reaches the intended decision under a changed but plausible context.
CHAPTER 9 OF 12 · REPAIR DERIVATIVE USE
9. Verify repair through reader journeys
Test search results, identifier resolution, citations, repository mirrors and common teaching downloads. Confirm that each route exposes the current claim before a reader reuses it.
Record unreachable or externally controlled routes and notify their owners. Universal correction should not be claimed when propagation remains incomplete.
| Route | Action |
|---|---|
| Review | Narrow wording |
| Catalogue | Show status |
| Teaching | Restore relation |
| Dataset | Add provenance |
CHAPTER 10 OF 12 · DECIDE RE-WITHDRAWAL
10. Choose a proportionate re-withdrawal decision
Select narrow wording repair, qualified re-withdrawal, temporary suspension or full withdrawal. State which versions and derivative statements the decision covers.
Re-withdraw the unsupported proposition, not the author, site or entire archive. A bounded decision is easier to apply and later review.
CHAPTER 11 OF 12 · DECIDE RE-WITHDRAWAL
11. State limits and common misconceptions
Persistent identifiers improve discovery but cannot force readers to follow relations. Version graphs may be incomplete, mirrors may lag and independent archaeologists may still disagree reasonably.
A restored link does not validate a claim; evidence and method do. Conversely, one broken link does not prove that every secondary use is wrong.
Evidence check
Confirm that versions, notices and unresolved limits remain visible in the final record.
CHAPTER 12 OF 12 · DECIDE RE-WITHDRAWAL
12. Monitor renewed drift
Sample new citations, repository exports, teaching copies and derivative datasets. Reopen review when wording expands, relation metadata disappears or a material new dataset changes the evidential range.
The gold standard keeps interpretation revisable while making the path from claim to archaeological record visible enough to challenge.
| Level | Use |
|---|---|
| Repair | Correct wording |
| Qualified | Limits travel |
| Suspend | Await evidence |
| Withdraw | Do not assert |
Frequently asked questions
What is reinstatement drift?
It is movement beyond the wording, evidence version or uncertainty that justified returning a replacement claim to use.
Is a live DOI enough to prove version integrity?
No. The identifier must resolve to the intended record and expose the relationship among obsolete, corrected and replacement versions.
Must re-withdrawal erase older scholarship?
No. Historical discussion can remain discoverable while current status and unsupported wording are made explicit.
When can a re-withdrawn claim return?
When a named evidence version, reproducible method and independent review support bounded wording and its version relations are visible.
Continue through verified routes
Core routes
Archaeology subject root · Gold Standard of Education · Gold Standard directory · How X Works hub
Specialist routes
- Replacement claim validation and secondary-literature reinstatement
- Secondary-literature correction lag and interpretive withdrawal escalation
- Citation-correction propagation drift and residual claim review
- Citation residue and repository-version reconciliation