The Gold Standard · Archaeology
Make the decision path visible
Revocation does not prevent an appeal, but an appeal should not function as temporary permission. Archaeological teams may present missing source records, a narrower population or a redesigned control. Governance must examine that evidence while uncertain joins and assemblage links remain protected from release.
The gold standard keeps three states distinct: the revoked route remains closed, the appeal tests whether the revocation decision should change, and any redesigned route earns new authority only through explicit re-entry evidence.
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 APPEAL
1. Define what the appeal can decide
State whether the appeal challenges the evidence, scope, procedure or proportionality of revocation. Name the authority, timetable and possible outcomes.
An appeal is not an informal continuation of the suspended recovery process. Its question and decision rights should be visible before evidence is submitted.
CHAPTER 2 OF 12 · FRAME THE APPEAL
2. Require materially new or newly available evidence
Identify source records, denominator reconstructions, independent tests or procedural facts that were not reasonably available at revocation. Explain why they could change the decision.
Repeating the same assurance in a different presentation does not close an evidence gap.
Evidence check
Check whether the scope, owner and decision consequence are explicit before continuing.
CHAPTER 3 OF 12 · FRAME THE APPEAL
3. Separate appeal reviewers from the failed control owner
Use reviewers who can assess archaeological consequence, model evidence and governance without depending on approval restoration. Declare interests and information limits.
Independence does not require unfamiliarity with the subject; it requires freedom to sustain, narrow or reverse the revocation.
| Ground | Evidence needed |
|---|---|
| Evidence error | Correct source record |
| Scope | Population analysis |
| Procedure | Decision trail |
| Proportionality | Risk and alternative |
CHAPTER 4 OF 12 · KEEP HOLDS REAL
4. Maintain residual release holds during review
Keep affected outputs, derivative joins and downstream interpretations from release unless an independently valid route supports them. Preserve queue order and case provenance.
Appeal status should not create a shadow approval through manual overrides or advisory labels.
CHAPTER 5 OF 12 · KEEP HOLDS REAL
5. Test whether holds reach every downstream use
Trace exports, publications, teaching sets, catalogues and partner systems that consume the bridge-model output. Confirm that the revoked result cannot re-enter through a copied dataset.
A release hold at the primary repository is incomplete if a downstream copy still presents the output as current.
Evidence check
Ask a second reviewer to reconstruct the example from the preserved evidence and stated assumptions.
CHAPTER 6 OF 12 · KEEP HOLDS REAL
6. Worked example: a recovered archive changes the denominator
An appeal locates an offline archive containing original geometry for many disputed cross-trench joins. Reconstructing the features increases the population and reveals that the earlier monitoring denominator was incomplete, but it also allows a narrower class to be validated.
Reviewers sustain revocation for the broad route, permit a new redesign application for the narrow class and keep all other joins on hold. Changed-context check: if the archive lacks reliable provenance, it may guide investigation but cannot alone support re-entry.
| Use | Control |
|---|---|
| Primary release | Block output |
| Derivative dataset | Mark withdrawn |
| Publication | Require review |
| Partner copy | Send notice |
CHAPTER 7 OF 12 · JUDGE RE-ENTRY
7. Define redesign re-entry separately from appeal success
List required population coverage, challenge cases, release-gate enforcement, reviewer workflow, provenance and monitoring. Treat the redesign as a new authority decision.
Even if the appeal finds a procedural flaw, the model does not automatically regain scientific and operational validity.
CHAPTER 8 OF 12 · JUDGE RE-ENTRY
8. Test independence from the failed pathway
Examine whether the redesign uses the same taxonomy, mapping rule, denominator query, override route or capacity bottleneck. Require direct tests of shared dependencies.
A new interface around the same unverified control is not a meaningful redesign.
Evidence check
Verify that the control still reaches the intended decision under a changed but plausible context.
CHAPTER 9 OF 12 · JUDGE RE-ENTRY
9. Use staged evidence before any restored release
Run representative retrospective tests, prospective shadow operation and live gate exercises. Reconcile disagreements with manual archaeological review before widening scope.
Shadow operation can produce evidence, but it should not authorise release while the route remains revoked.
| Criterion | Proof |
|---|---|
| Population | Stable denominator |
| Validity | Challenge performance |
| Enforcement | Gate state changes |
| Monitoring | Triggers and owner |
CHAPTER 10 OF 12 · RECORD THE OUTCOME
10. Issue a precise appeal and re-entry decision
Record whether revocation is sustained, narrowed, remitted or reversed, and separately state whether a redesign may enter testing or controlled use. Include effective time and downstream instructions.
Precise outcomes prevent a partial appeal success from being interpreted as full approval restoration.
CHAPTER 11 OF 12 · RECORD THE OUTCOME
11. State limits and misconceptions
An appeal cannot recreate lost context, eliminate judgement differences or prove every rare formation. Release holds can also create backlogs that pressure reviewers toward shortcuts.
Record unresolved classes, manual capacity and triggers that would pause any staged re-entry.
Evidence check
Confirm that versions, notices and unresolved limits remain visible in the final record.
CHAPTER 12 OF 12 · RECORD THE OUTCOME
12. Audit the full decision chain
Track appeal grounds, evidence, reviewer independence, hold coverage, affected cases, outcome, redesign criteria and later monitoring.
The gold standard allows decisions to be challenged without weakening protection. New evidence changes authority only through a recorded route with clear scope and consequences.
| Field | Purpose |
|---|---|
| Appeal result | Addresses revocation |
| Redesign state | Addresses new route |
| Effective time | Bounds authority |
| Downstream action | Directs users |
Frequently asked questions
Does filing an appeal pause revocation?
Not unless the governing authority explicitly orders that result. The protective default is to keep the revoked route closed.
Can procedural error restore the model automatically?
No. Procedure and scientific-operational validity are related but distinct questions.
May a redesign run during the appeal?
It may run in a controlled evidence-gathering mode without authorising affected releases.
What makes re-entry legitimate?
Explicit criteria, independent testing, end-to-end gate evidence, defined scope and a recorded authority decision.
Continue through verified routes
Core routes
Archaeology subject root · Gold Standard of Education · Gold Standard directory · How X Works hub
Specialist routes
- Second-suspension recovery deadlock, evidence escalation and conditional approval revocation
- Renewed conditional monitoring drift, restoration-condition breaches and second suspension
- Scope revalidation approval restoration, evidence sufficiency disputes and renewed conditional monitoring
- Control redesign validation disputes, competing success criteria and governance acceptance