The Gold Standard · Anthropology
Make the decision path visible
A disclosure review board can order the right correction and still leave the wrong record in use. A downloaded attachment, quoted paragraph, case-management cache or briefing note may continue to shape decisions after the official page changes. Publishing version two is therefore the start of repair, not its end.
The gold standard maps where the superseded release travelled, sends a correction that identifies the controlling version, confirms replacement at important decision points and reopens only those decisions that may have changed. It preserves history without allowing history to masquerade as current 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 · MAP THE SPREAD
1. Identify the controlling and superseded releases
Assign immutable version identifiers, dates, titles and checksums. State which version is current and whether the correction changes evidence, interpretation or only presentation.
Readers need a reliable way to distinguish two files with similar names. A quiet replacement at the same URL does not establish control.
CHAPTER 2 OF 12 · MAP THE SPREAD
2. Build a dissemination map
List direct recipients, shared drives, case systems, email attachments, portals, exports, printed bundles, briefing notes and downstream reports.
Begin with known distribution and then search for references, filenames, identifiers and quoted phrases. The map will be incomplete, so record confidence and high-consequence unknowns.
Evidence check
Check whether the scope, owner and decision consequence are explicit before continuing.
CHAPTER 3 OF 12 · MAP THE SPREAD
3. Link each copy to the decision it may influence
Record who used the release, for what purpose, at what stage and whether the contested passage was material.
A cached copy in an inactive archive needs different treatment from one attached to a pending appeal or operational restriction.
| Location | Question |
|---|---|
| Portal | Which version is visible? |
| Case file | Which copy governs review? |
| Who received attachments? | |
| Briefing | Which claims were repeated? |
CHAPTER 4 OF 12 · PROPAGATE CORRECTION
4. Issue a correction notice that can travel with the file
Name the superseded and controlling versions, correction category, affected section, practical consequence and route to the replacement.
Do not repeat protected details. The notice should be useful even when separated from the original email or portal page.
CHAPTER 5 OF 12 · PROPAGATE CORRECTION
5. Use more than one channel for consequential recipients
Update the canonical page, send direct notice, replace controlled repositories and flag affected case records. Require acknowledgement where the decision consequence is high.
A broadcast message alone is weak evidence that the corrected record reached the person who can act on it.
Evidence check
Ask a second reviewer to reconstruct the example from the preserved evidence and stated assumptions.
CHAPTER 6 OF 12 · PROPAGATE CORRECTION
6. Worked example: a cached extract remains in the appeal file
Suppose a board corrects an extract that had hidden the expiry of an authority mandate. The portal shows the new release, but the appeal officer’s case bundle still contains a downloaded copy and a briefing note that repeats the earlier conclusion.
The correction owner replaces the bundle, adds a visible supersession marker, issues an amended briefing note and asks the officer to confirm whether the expired mandate changes the provisional decision. Changed-context check: if the cached copy was never opened and no briefing or decision relied on it, the propagation failure still needs closure, but full decision reconsideration may be unnecessary.
| Field | Purpose |
|---|---|
| Version IDs | Identify old and new |
| Change category | Explain correction |
| Decision effect | Prompt review |
| Replacement route | Reach controlling copy |
CHAPTER 7 OF 12 · REPAIR DECISIONS
7. Test materiality before reopening a decision
Ask whether the corrected information could reasonably change authority, credibility, chronology, burden, remedy or outcome. Document the counterfactual, not merely whether the final result happens to remain the same.
Use an independent reviewer for consequential or disputed materiality calls.
CHAPTER 8 OF 12 · REPAIR DECISIONS
8. Reconsider decisions without erasing the original path
Preserve the earlier decision and evidence set, then create a linked reconsideration record using the corrected release.
This shows what changed and avoids rewriting history. A confirmed outcome still needs reasons demonstrating that the correction was considered.
Evidence check
Verify that the control still reaches the intended decision under a changed but plausible context.
CHAPTER 9 OF 12 · REPAIR DECISIONS
9. Contain under-redaction while propagating correction
If the first release exposed protected information, stop further distribution, restrict repositories, notify recipients of handling duties and assess whether incident response is needed.
Do not send the sensitive value again in the correction notice. Use version identifiers and controlled contact routes.
| Area | Question |
|---|---|
| Authority | Who could act? |
| Chronology | Did sequence change? |
| Evidence | Was weight distorted? |
| Outcome | Could remedy differ? |
CHAPTER 10 OF 12 · CLOSE THE LOOP
10. Confirm replacement at critical control points
Verify the canonical repository, case file, reviewer bundle, cited report and any automated import. Record who checked, when and what remains unresolved.
Receipt is not the same as replacement. A recipient may acknowledge the notice while continuing to use a locally saved copy.
CHAPTER 11 OF 12 · CLOSE THE LOOP
11. Preserve a complete propagation ledger
Retain distribution evidence, correction notices, acknowledgements, repository changes, materiality reviews, reconsiderations and unresolved recipients.
The ledger should make it possible to reconstruct which version governed each decision without exposing the protected source broadly.
Evidence check
Confirm that versions, notices and unresolved limits remain visible in the final record.
CHAPTER 12 OF 12 · CLOSE THE LOOP
12. Audit reach, speed and repeat leakage
Measure time to notify, acknowledgement, replacement, decision repair, rediscovery of stale copies and recurring cache locations.
The gold standard follows the correction to the point of use. A re-release is complete only when material decisions can no longer unknowingly depend on the superseded record.
| Measure | Warning |
|---|---|
| Unacknowledged notice | Recipient not reached |
| Stale rediscovery | Cache unresolved |
| Repair latency | Decision exposure |
| Repeat location | Systemic distribution gap |
Frequently asked questions
Is updating the website enough?
No. Consequential downloaded, cached, printed or quoted copies may still influence decisions.
Must every decision be reopened?
No. Reopen decisions for which the corrected information could materially change reasoning, authority, remedy or outcome.
Should the superseded release be deleted?
Preserve it under controlled retention and mark it clearly as superseded so historical decisions remain reconstructable.
How can a privacy correction avoid repeating sensitive information?
Refer to version identifiers, affected sections and handling instructions without restating the protected value.
Continue through verified routes
Core routes
Anthropology subject root · Gold Standard of Education · Gold Standard directory · How X Works hub
Specialist routes
- Redaction disputes, disclosure review boards and corrective re-release
- Redaction quality, context loss and re-identification risk
- Decision explanations and reversing automated links
- Evidence asymmetry and independent review