The Gold Standard · Archaeology
Make the decision path visible
A redesign can be good enough for bounded use while important uncertainty remains. Conditional approval makes that boundary explicit: which release contexts are permitted, which protections must remain active and what evidence will turn acceptance into rejection. Without those terms, temporary safeguards can fade while the word approved survives.
The gold standard translates validation findings into operational obligations, assigns each condition to an owner, monitors real performance and re-escalates before residual risk becomes normal practice.
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 · WRITE CONDITIONS
1. Define conditional approval precisely
Identify the redesign version, permitted archaeological contexts, necessary controls, excluded cases, monitoring period and authority. State whether the decision expires automatically.
Conditional approval is not partial confidence expressed vaguely. It is executable permission inside a documented boundary.
CHAPTER 2 OF 12 · WRITE CONDITIONS
2. Turn residual findings into obligations
For every unresolved issue, name the safeguard, owner, evidence, frequency and breach response. Link each obligation to the protected release or provenance claim.
An obligation such as review difficult cases needs a definition of difficult, a queue, a reviewer and a receipt.
Evidence check
Check whether the scope, owner and decision consequence are explicit before continuing.
CHAPTER 3 OF 12 · WRITE CONDITIONS
3. Separate entry conditions from ongoing conditions
Entry conditions must pass before deployment, such as provenance completeness or independent review. Ongoing conditions include coverage, workload, bypass detection and periodic challenge.
Monitoring cannot compensate for a failed entry protection. Some evidence is necessary before any use is safe.
| Field | Example |
|---|---|
| Version | Validated redesign |
| Scope | Ordinary contexts |
| Exclusion | Complex joins |
| Expiry | Scheduled review |
CHAPTER 4 OF 12 · DEPLOY WITHIN LIMITS
4. Restrict use to validated contexts
Encode permitted site types, complexity bands, data quality and release consequences where possible. Route out-of-scope cases to the prior control or independent review.
Training alone is weak when the system can accept any case. Technical and decision-gate constraints make the boundary visible.
CHAPTER 5 OF 12 · DEPLOY WITHIN LIMITS
5. Establish an obligation register
Record each condition, owner, due date, evidence location, current state, exception route and dependency. Show relationships so failure of one control does not leave others falsely marked healthy.
The register should support action, not merely compliance reporting. A missed obligation must reach someone who can restrict or suspend use.
Evidence check
Ask a second reviewer to reconstruct the example from the preserved evidence and stated assumptions.
CHAPTER 6 OF 12 · DEPLOY WITHIN LIMITS
6. Worked example: approve ordinary trenches but not complex joins
Validation shows the redesigned bridge-model control preserves provenance for ordinary single-trench sequences, but cross-trench joins remain underrepresented. Governance approves ordinary cases only, requires independent review for joins and demands 90 days of coverage evidence.
Operations later routes a complex join through the ordinary queue to meet a deadline. The condition breach pauses that release and triggers review of similar cases. Changed-context check: if a new validation set demonstrates the join safeguard across representative sites, governance may expand scope through a new acceptance decision rather than an informal exception.
| Field | Purpose |
|---|---|
| Condition | Required safeguard |
| Owner | Accountability |
| Evidence | Proof of operation |
| Breach action | Immediate response |
CHAPTER 7 OF 12 · MONITOR THE BARGAIN
7. Monitor indicators tied to each obligation
Track population coverage, excluded cases, provenance defects, override attempts, reviewer delay and unresolved findings. Preserve denominators and context so improving rates cannot hide disappearing cases.
Use thresholds to prompt review, not to replace judgment. Rare high-consequence failures may require action before a rate crosses its boundary.
CHAPTER 8 OF 12 · MONITOR THE BARGAIN
8. Respond proportionately to a breached condition
Contain affected releases, preserve evidence, test materiality and decide whether to correct, narrow, suspend or revoke approval. Record any temporary compensating control.
One administrative delay may not invalidate the redesign, but a failed necessary protection should stop the relevant use immediately.
Evidence check
Verify that the control still reaches the intended decision under a changed but plausible context.
CHAPTER 9 OF 12 · MONITOR THE BARGAIN
9. Reconcile decisions made during non-compliance
Find releases processed while a condition was unmet and determine whether the missing safeguard could change their archaeological interpretation or provenance confidence.
Re-review material cases while preserving stable outcomes. The aim is decision repair, not symbolic invalidation of all work.
| Indicator | Question |
|---|---|
| Coverage | Who is included? |
| Defects | What protection failed? |
| Overrides | Is bypass growing? |
| Delay | Is the safeguard usable? |
CHAPTER 10 OF 12 · CLOSE OR RENEW
10. Run the scheduled governance review
Compare promised obligations with operational evidence, unresolved risk and changed contexts. Choose full acceptance, renewed conditions, narrowed scope, further validation or rejection.
Renewal should not occur because the monitoring period ended quietly. It needs affirmative evidence that the protected claim remains defensible.
CHAPTER 11 OF 12 · CLOSE OR RENEW
11. State the limits of post-acceptance monitoring
Monitoring samples real use and can miss rare contexts, informal bypasses or shared assumptions. A period without detected failure is not proof of universal performance.
Keep these limits beside the acceptance record and preserve an escalation path for unexpected archaeological evidence.
Evidence check
Confirm that versions, notices and unresolved limits remain visible in the final record.
CHAPTER 12 OF 12 · CLOSE OR RENEW
12. Audit acceptance from decision to retirement
Track versions, conditions, breaches, exceptions, reconciled releases, scope changes, renewals and final disposition. Compare the original rationale with later evidence.
The gold standard keeps conditional approval honest: permission remains tied to obligations, and governance can see when the bargain no longer holds.
| Outcome | Meaning |
|---|---|
| Accept | Conditions satisfied |
| Renew | Residual evidence needed |
| Narrow | Scope reduced |
| Revoke | Use stops |
Frequently asked questions
Is conditional approval the same as a temporary exception?
No. It is a formal bounded acceptance with explicit obligations, evidence and governance authority.
Can post-acceptance monitoring replace validation?
No. Necessary entry protections must pass before deployment; monitoring addresses residual uncertainty in real use.
What happens when a condition is breached?
Contain affected use, assess materiality and let the designated authority correct, narrow, suspend or revoke the approval.
When can conditions be removed?
Only after new evidence supports a fresh governance decision; operational convenience is not enough.
Continue through verified routes
Core routes
Archaeology subject root · Gold Standard of Education · Gold Standard directory · How X Works hub
Specialist routes
- Control redesign validation disputes, competing success criteria and governance acceptance
- Regression root-cause disputes, independent review and control redesign
- Remediation regression, control-drift signals and re-escalation
- Override remediation effectiveness, repeat-use triggers and governance escalation