The Gold Standard · Archaeology
Make the decision path visible
A version graph may be repaired once and still drift later. A mirror resumes an old export schedule, a relation is mapped in the wrong direction or a corrected status reaches the landing page but not the citation feed. A secondary author then asks to reinstate a citation that appears current through one route and withdrawn through another.
The gold standard treats reconciliation as a distributed evidence problem. It measures renewed lag, rebuilds the reader journey and permits only the wording supported by the current record.
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 · DETECT RECONCILIATION DRIFT
1. Restate the reconciled version graph
List the canonical record, specific versions, corrections, withdrawals, replacements, mirrors, exports and identifiers that the earlier reconciliation covered. Preserve the expected direction and status of every material relation.
A graph is more than a set of links. It is a claim about sequence, authority and permitted present use, so each route must display compatible meaning.
CHAPTER 2 OF 12 · DETECT RECONCILIATION DRIFT
2. Define reconciliation drift
Compare current relation direction, status labels, resolver targets, export metadata and mirror displays with the reconciled baseline. Drift is material when a careful reader can reach a different current claim through another ordinary route.
A stale timestamp alone may be harmless. A stale status that changes whether an interpretation appears usable is not.
Evidence check
Check whether the scope, owner and decision consequence are explicit before continuing.
CHAPTER 3 OF 12 · DETECT RECONCILIATION DRIFT
3. Predefine the reinstatement review
Record the exact secondary proposition, source version, route used, publication stage and inference affected. Outcomes may be confirmation of withdrawal, narrower wording, corrected citation, conditional reinstatement or historical-only use.
Reasonable reliance affects responsibility and remedy, but it cannot make unsupported archaeology current. Agree this distinction before reviewing the author.
| Node | Expected state |
|---|---|
| Canonical | Current relation |
| Earlier version | History retained |
| Correction | Visible consequence |
| Mirror | Compatible status |
CHAPTER 4 OF 12 · RECONSTRUCT CORRECTION LAG
4. Reconstruct the renewed correction timeline
Capture primary changes, export events, mirror imports, cache expiry, resolver results and author access dates. Identify when each route first displayed and then lost the reconciled state.
The sequence distinguishes a temporary delay from recurrence caused by a broken mapping, schedule or ownership handoff.
CHAPTER 5 OF 12 · RECONSTRUCT CORRECTION LAG
5. Test relation direction and reader consequence
Follow previous/new, version-of, correction, withdrawal and replacement relations from each public entry point. Record the wording a reader sees without privileged repository knowledge.
A technically present relation may still fail if it is reversed, hidden behind a dead resolver or omitted from the format used by citation software.
Evidence check
Ask a second reviewer to reconstruct the example from the preserved evidence and stated assumptions.
CHAPTER 6 OF 12 · RECONSTRUCT CORRECTION LAG
6. Worked example: a corrected graph drifts through a resumed feed
A repository repairs a withdrawn bridge-model claim and its mirror agrees. Months later, a legacy weekly feed is re-enabled after maintenance and overwrites the mirror relation, making the older interpretation appear current for ten days.
The review accepts that a secondary author relied on the visible route but delays reinstatement until the feed is fixed and the supported wording is adopted. Changed-context check: a historical essay may retain the earlier citation when it clearly describes the development of interpretation and does not present the withdrawn claim as current evidence.
| Event | Evidence |
|---|---|
| Primary change | Timestamp |
| Export | Issue time |
| Mirror import | Display time |
| Reader route | Observed status |
CHAPTER 7 OF 12 · REVIEW REINSTATEMENT
7. Reconcile every material route again
Correct the canonical relation, mirror mapping, feed, landing-page notice, resolver target and citation export. Preserve the old version and its history rather than deleting the node that explains the correction.
A local fix is incomplete when the route that caused the appeal can recreate the misleading status on its next run.
CHAPTER 8 OF 12 · REVIEW REINSTATEMENT
8. Decide secondary citation reinstatement proportionately
Restore only the proposition supported by the current evidence and version. Require correction where a present conclusion relies materially on the withdrawn wording, and permit labelled historical reference where that is the genuine scholarly purpose.
Do not widen a bounded claim merely because the author acted reasonably. Scientific scope follows the repaired evidence, not the fairness finding.
Evidence check
Verify that the control still reaches the intended decision under a changed but plausible context.
CHAPTER 9 OF 12 · REVIEW REINSTATEMENT
9. Publish status that readers can use
Show the current version, relevant correction, relation to earlier versions and the practical consequence for citation. Provide a stable route for authors to question or report conflicting metadata.
A repository note should explain enough for a reader to act without exposing internal blame or demanding that they reconstruct the entire incident.
| Outcome | Condition |
|---|---|
| Withdrawn | No support |
| Narrowed | Bounded support |
| Corrected | Version changed |
| Historical | Past use labelled |
CHAPTER 10 OF 12 · STABILISE THE GRAPH
10. Exercise the next correction cycle
Issue a controlled status change, run exports and mirror imports, clear representative caches and test repository search, resolvers and citation managers. Confirm that earlier history remains reachable while present use changes consistently.
Include the maintenance or recovery path that re-enabled the old feed, because recurrence often sits outside the ordinary publishing workflow.
CHAPTER 11 OF 12 · STABILISE THE GRAPH
11. State limits and common misconceptions
Graph consistency does not validate the underlying archaeological method, and mirror disagreement does not prove that the canonical repository is scientifically correct. The review still examines evidence and claim scope.
No audit can find every offline bibliography or private dataset. State the routes sampled, the dates observed and the residual citation risk.
Evidence check
Confirm that versions, notices and unresolved limits remain visible in the final record.
CHAPTER 12 OF 12 · STABILISE THE GRAPH
12. Monitor lag, relations and claim expansion
Track export age, mirror freshness, relation direction, resolver targets, notice visibility and new secondary wording. Reopen review when lag exceeds the agreed window or a reinstated claim expands beyond its evidence.
The gold standard closes when materially used routes agree, the author receives a proportionate outcome and the graph can survive the next ordinary correction cycle.
| Route | Pass condition |
|---|---|
| Search | Current status |
| Resolver | Correct target |
| Citation export | Relation preserved |
| Mirror | Lag within limit |
Frequently asked questions
What is version-graph reconciliation drift?
It is divergence between the relation and status state that was reconciled and what materially used routes display later.
Can correction lag justify citation reinstatement?
It can change responsibility and remedy, but current wording still requires current archaeological support.
Should withdrawn versions be deleted?
No. Preserve them with visible status and relations so history and correction remain intelligible.
What prevents correction-lag recurrence?
Repairing the generating feed and mappings, then exercising repository, mirror, resolver and citation routes together.
Continue through verified routes
Core routes
Archaeology subject root · Gold Standard of Education · Gold Standard directory · How X Works hub
Specialist routes
- Mirror correction lag and version-graph reconciliation
- Version-graph repair drift and mirror-relation regression
- Replacement claim re-withdrawal appeal and version-graph repair
- Citation correction propagation and residual claim review