The Gold Standard · Archaeology
Make the decision path visible
After alert fatigue appears, teams often suppress recurring signals. That can be sensible when several rules describe one known episode or when a maintenance period makes a detector temporarily uninformative. It becomes dangerous when suppression outlives its evidence, masks a new range-specific shift or can be applied by the same person whose work is under review.
The gold standard makes every suppression explicit, bounded and reversible; preserves the raw signal; defines override conditions before they are needed; and gives an independent reviewer power to challenge a quiet dashboard.
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 · DEFINE SUPPRESSION
1. Distinguish grouping, suppression and deletion
Grouping presents correlated signals as one episode. Suppression withholds a notification under a stated rule while retaining the observation. Deletion removes evidence and should not be disguised as workload management.
Use different labels and permissions so later reviewers can reconstruct both what happened and what people saw.
CHAPTER 2 OF 12 · DEFINE SUPPRESSION
2. Name the operational reason and scientific risk
A rule may mute duplicate messages during a confirmed instrument fault, planned recalibration or known data replay. Record the reason, affected ranges and what change could still occur during that interval.
Operational familiarity does not eliminate scientific risk. A known global fault can coexist with a new local bridge shift.
Practical check
Write the decision, evidence and limit in three separate sentences. If one sentence depends on an unstated assumption, name it before continuing.
CHAPTER 3 OF 12 · DEFINE SUPPRESSION
3. Preserve the raw signal and counterfactual queue
Store every triggering statistic, rule version, input and time. Maintain a shadow view showing which alerts would have appeared without suppression.
Without the counterfactual queue, teams cannot measure the cost of silence or test whether a suppression rule remained appropriate.
| Action | Evidence status |
|---|---|
| Group | All signals visible in one episode |
| Suppress | Signal retained, notification withheld |
| Override | Suppressed signal surfaced |
| Delete | Evidence removed; generally prohibited |
CHAPTER 4 OF 12 · BOUND THE RULE
4. Bound suppression by range, cause and time
Specify the matrix, concentration or isotope range, instrument, bridge version, rule family, start, expiry and responsible owner.
Never use open-ended labels such as until stable. Define the evidence that ends or extends the rule and require a fresh decision at expiry.
CHAPTER 5 OF 12 · BOUND THE RULE
5. Predefine escalation overrides
An override should surface a suppressed episode when consequence, persistence, independent confirmation or pattern changes exceed a threshold.
Overrides need a direct route to someone authorised to pause results. If the alert must pass through the suppression owner, the safeguard can fail exactly when conflict matters.
Practical check
Write the decision, evidence and limit in three separate sentences. If one sentence depends on an unstated assumption, name it before continuing.
CHAPTER 6 OF 12 · BOUND THE RULE
6. Worked example: maintenance muting hides a boundary shift
Suppose a detector baseline fault creates repeated low-range warnings, and the team suppresses that rule for forty-eight hours during maintenance. Four overlap specimens near a provenance boundary also move coherently, but their alerts share the muted rule family.
The shadow queue detects independent specimens in a consequential range and triggers an override. A reviewer separates the known low-range baseline fault from the boundary-specific residual pattern, pauses affected classifications and orders confirmation. Changed-context check: if all four warnings derive from one duplicated import, the override still preserves review, but the episode closes as a pipeline error after provenance checks.
| Field | Example |
|---|---|
| Scope | Named range and instrument |
| Cause | Confirmed maintenance fault |
| Expiry | Date or evidence trigger |
| Owner | Approver and reviewer |
CHAPTER 7 OF 12 · CHALLENGE SAFELY
7. Separate suppression authority from review authority
The person proposing a rule should document the evidence. A different authorised reviewer should approve high-consequence or long-lived suppression and inspect renewals.
Emergency action may require immediate temporary muting, but retrospective independent review should occur within a defined period.
CHAPTER 8 OF 12 · CHALLENGE SAFELY
8. Use challenge channels that bypass the ordinary queue
Laboratory staff, archaeologists and data users should be able to flag a suspicious absence, changed claim or external inconsistency.
A challenge is not proof of drift. It is a request to reveal the shadow evidence and test whether the quiet dashboard reflects stability or filtering.
Practical check
Write the decision, evidence and limit in three separate sentences. If one sentence depends on an unstated assumption, name it before continuing.
CHAPTER 9 OF 12 · CHALLENGE SAFELY
9. Escalate by evidence and consequence, not volume
One high-consequence independent signal may justify action, while hundreds of duplicate messages may not. Combine statistical strength, persistence, independence and claim impact.
Do not reward a suppression rule for reducing message count. Measure whether important episodes were detected and resolved.
| Trigger | Response |
|---|---|
| Independent specimens | Surface episode |
| Consequential range | Priority review |
| Cause mismatch | End suppression |
| External disagreement | Independent confirmation |
CHAPTER 10 OF 12 · RESTORE CONFIDENCE
10. Reopen suppressed episodes when assumptions fail
Triggers include a changed cause, expired maintenance window, new affected range, external reference disagreement or later evidence that the muted rule carried unique information.
Reopening should preserve the earlier operational context and review every downstream claim materially exposed during the silent period.
CHAPTER 11 OF 12 · RESTORE CONFIDENCE
11. Communicate corrections without erasing the surveillance record
Mark which results were provisional, paused, restated or unchanged. Link the suppression rule, override and confirmation evidence to the revised bridge version.
A correction should not imply that every result in the window was invalid. Bound the affected claims and explain the test used.
Practical check
Write the decision, evidence and limit in three separate sentences. If one sentence depends on an unstated assumption, name it before continuing.
CHAPTER 12 OF 12 · RESTORE CONFIDENCE
12. Audit the governance of silence
Track active suppressions, age, renewals, shadow-alert yield, override use, independent challenges and material findings first detected outside the monitoring system.
The gold standard permits quiet only when it remains observable, bounded and challengeable. A silent system with no shadow record is not controlled surveillance.
| Measure | Question |
|---|---|
| Shadow yield | What was hidden? |
| Renewal count | Did temporary become permanent? |
| Challenge outcome | Could outsiders surface risk? |
| Affected claims | What needed repair? |
Frequently asked questions
Is alert suppression always unsafe?
No. Bounded suppression can reduce duplicate work when raw signals and shadow evidence remain available.
Who may override a suppression?
A named role with direct access to the monitoring evidence and authority to escalate without the suppression owner’s permission.
Should a maintenance window suppress every rule?
No. Scope the rule to signals made uninformative by the known cause and preserve other ranges and independent checks.
What makes a challenge independent?
The reviewer is not responsible for defending the suppressed workflow and can inspect the raw and shadow records.
Continue through verified routes
Core routes
Archaeology subject root · Gold Standard of Education · Gold Standard directory · How X Works hub
Specialist routes
- Bridge-model surveillance alert fatigue and tiered investigation
- Bridge-model surveillance false alarms and escalation rules
- Bridge-model decision-limit surveillance and reopening claims
- Bridge-model revision and versioned reanalysis