The Gold Standard · Archaeology
Make the decision path visible
A bridge-model team may impose a sensible interim restriction and still lose control of it. Users export data before the gate, copy a value into a spreadsheet, rerun an old script or relabel exploratory output as final because the restricted path is inconvenient.
The gold standard treats restrictions as enforceable system states. It watches alternate routes, binds release authority to evidence, records emergency exceptions and tests whether changed workflows can bypass the intended gate.
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 THE RESTRICTION
1. Translate an interim restriction into observable rules
State the bridge version, affected ranges, prohibited decisions, allowed descriptive uses, required reviewer and expiry or review trigger.
A memo saying use caution is not a control. A user must be able to tell what cannot be released and what evidence unlocks it.
CHAPTER 2 OF 12 · DEFINE THE RESTRICTION
2. Locate every route from measurement to claim
Map APIs, exports, notebooks, spreadsheets, dashboards, email attachments, cached results and manual transcription. Include paths used only during outages or fieldwork.
A release gate on the primary application protects only the work that reaches that application.
Evidence check
Check whether the scope, owner and decision consequence are explicit before continuing.
CHAPTER 3 OF 12 · DEFINE THE RESTRICTION
3. Separate exploration from authorised release
Mark exploratory outputs with version, restriction and non-release status. Prevent them from inheriting approval merely because they resemble the final format.
Exploration may continue under controlled conditions, but it cannot quietly become evidence for a consequential archaeological claim.
| Field | Example |
|---|---|
| Object | Bridge version and range |
| Limit | No threshold claim |
| Allowed | Marked exploration |
| Release | Independent approval |
CHAPTER 4 OF 12 · FIND WORKAROUNDS
4. Detect restriction drift
Compare the approved rule with actual configurations, user roles, override logs and sampled outputs. Look for renamed fields, copied values, missing warning banners and long-lived local files.
Drift can arise from misunderstanding, urgency or technical change; detection should reveal the path before assigning cause.
CHAPTER 5 OF 12 · FIND WORKAROUNDS
5. Treat workarounds as evidence about control design
Ask what need the workaround served, why the approved route was slow or unusable and which safeguard disappeared. Repair the workflow as well as the individual case.
Punishing a user without fixing a predictable bottleneck encourages the next bypass to become less visible.
Evidence check
Ask a second reviewer to reconstruct the example from the preserved evidence and stated assumptions.
CHAPTER 6 OF 12 · FIND WORKAROUNDS
6. Worked example: a seasonal result bypasses the release gate
A short excavation window ends before low-range revalidation is complete. A researcher exports instrument values, applies an older conversion workbook and places the resulting chronology in a public briefing.
The team withdraws the briefing, preserves the export and workbook, reruns the case through the restricted bridge path and requires an independent reviewer before any threshold claim is restored. Changed-context check: if the export is used only to schedule non-destructive follow-up sampling and is labelled provisional, the team may permit it under a documented operational exception that cannot authorise publication.
| Route | Risk |
|---|---|
| Spreadsheet | Old formula |
| Export | Gate omitted |
| Manual copy | Version lost |
| Cached result | Restriction stale |
CHAPTER 7 OF 12 · ENFORCE THE GATE
7. Place the release gate at the decision boundary
Require a valid bridge version, covered range, evidence package and accountable approver before a claim leaves the controlled environment. Reject missing or expired tokens rather than relying only on reminders.
The strongest gate sits where exploratory work becomes a published, operational or irreversible decision.
CHAPTER 8 OF 12 · ENFORCE THE GATE
8. Control emergency overrides
Define who may override, eligible circumstances, maximum duration, compensating review, visible marking and after-action review. Log both successful and rejected attempts.
An emergency path is a bounded exception, not a permanent parallel route for ordinary delays.
Evidence check
Verify that the control still reaches the intended decision under a changed but plausible context.
CHAPTER 9 OF 12 · ENFORCE THE GATE
9. Use independent review for disputed releases
Give the reviewer the restriction, raw evidence, bridge version, workaround history and decision consequence. Keep the requester from approving their own bypass.
Independence matters most when a deadline or sunk effort makes release feel inevitable.
| Check | Required proof |
|---|---|
| Version | Approved fingerprint |
| Range | Coverage match |
| Review | Named approver |
| Exception | Active bounded authority |
CHAPTER 10 OF 12 · RESTORE NORMAL USE
10. Retire workarounds when coverage returns
Remove obsolete workbooks and temporary roles, close override tickets, revalidate affected outputs and notify users of the restored approved path.
Leaving the workaround available after revalidation invites it to become the next default.
CHAPTER 11 OF 12 · RESTORE NORMAL USE
11. Run a changed-workflow transfer check
Move the process to a new repository, instrument, contractor or field team and attempt releases through every mapped route. Confirm that the gate follows the decision, not only the original software.
A control that survives normal use but fails during export, outage or handover has not transferred.
Evidence check
Confirm that versions, notices and unresolved limits remain visible in the final record.
CHAPTER 12 OF 12 · RESTORE NORMAL USE
12. Audit restriction effectiveness
Track bypass attempts, unmarked provisional outputs, time outside the approved path, override age, gate rejection accuracy and rediscovered legacy tools.
The gold standard measures whether restrictions shape real releases, not whether the policy document remains unchanged.
| Measure | Warning |
|---|---|
| Bypass success | Gate incomplete |
| Override age | Exception normalised |
| Unmarked output | Status unclear |
| Legacy rediscovery | Retirement weak |
Frequently asked questions
Should every export be blocked during revalidation?
No. Allow only the uses and ranges the interim rule defines, with status that cannot be mistaken for release authority.
Is a manual workaround always misconduct?
No. It may reveal a genuine operational need, but its evidence and safeguards must be assessed before any consequential claim relies on it.
Where should a release gate sit?
At the boundary where exploratory or internal output becomes public, operational, irreversible or otherwise decision-bearing.
When can an emergency override close?
After the event is reviewed, affected outputs are reconciled, temporary authority is removed and the normal path again controls release.
Continue through verified routes
Core routes
Archaeology subject root · Gold Standard of Education · Gold Standard directory · How X Works hub
Specialist routes
- Revalidation backlogs, interim restrictions and coverage-restoration priorities
- Compensating-control drift, coverage loss and revalidation
- Suppression dependency, compensating controls and single-point blindness
- Suppression renewal, stale exceptions and automatic reinstatement