The Gold Standard · Anthropology
Make the decision path visible
An appeal can appear closed because a recognised delegate acknowledged the correction. Yet that delegate may have forwarded the record, assigned action to a subdelegate or relied on a shared mailbox whose users never saw the later revocation. Removing the first person’s authority does not by itself repair every downstream claim of closure.
The gold standard maps the delegation chain, sends a precise revocation through each material route, verifies where authority and copies actually moved and reconciles conflicting closure records into one defensible current state.
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 CHAIN
1. Define the object being revoked
Name the acknowledgement, appeal, record version, original authority, effective time and the closure claim it supported. State whether the change withdraws all authority or only a role, copy, decision or period.
A broad message saying the acknowledgement is no longer valid can cause recipients to discard evidence that remains historically true. A precise revocation changes current force while preserving the original event.
CHAPTER 2 OF 12 · MAP THE CHAIN
2. Map principal, delegate and subdelegate relationships
Identify who conferred authority, who accepted it, whether further delegation was permitted and which services acted for a role rather than a named person. Include shared mailboxes, repository stewards and decision owners.
Draw the chain as actual control points. An organisational chart is not enough when one team owns the inbox, another controls the file and a third signs the closure record.
Evidence check
Check whether the scope, owner and decision consequence are explicit before continuing.
CHAPTER 3 OF 12 · MAP THE CHAIN
3. Define the propagation population
Combine delegation registers, assignment logs, forwarded messages, repository access, distribution lists, exports and decisions citing the acknowledgement. Rank routes by consequence and reversibility.
The population is not every person who ever saw the appeal. It is every holder whose authority, copy or decision can still make the revoked closure operational.
| Field | Question |
|---|---|
| Principal | Who conferred authority? |
| Delegate | What could be done? |
| Subdelegate | Was onward assignment allowed? |
| Control point | Who owns the copy or decision? |
CHAPTER 4 OF 12 · SEND THE CHANGE
4. Write a notice that can travel without losing meaning
State the governing identifier, effective time, changed authority, affected scope, required action, deadline and route for uncertainty. Include a stable link or fingerprint so forwarded notices remain bound to the correct record.
Avoid relying on a subject line such as revocation update. Downstream users need enough context to distinguish the changed acknowledgement from related corrections that remain current.
CHAPTER 5 OF 12 · SEND THE CHANGE
5. Use layered propagation rather than one broadcast
Notify the principal, current delegate, subdelegates, repository owners and consequential decision holders through their accountable channels. Add system flags or release gates where a human message alone cannot stop use.
A broadcast can create awareness, but accountable propagation requires evidence that the change reached the control points capable of continuing the old closure.
Evidence check
Ask a second reviewer to reconstruct the example from the preserved evidence and stated assumptions.
CHAPTER 6 OF 12 · SEND THE CHANGE
6. Worked example: two downstream reviewers inherit different authority
A principal authorises a liaison to acknowledge correction of a proxy record. The liaison assigns repository replacement to one reviewer and appeal closure to another. The principal later revokes the liaison’s mandate after discovering that the repository scope was misstated.
The correction owner preserves the first receipt, notifies both reviewers, pauses reliance on the closure record and verifies the repository version separately. The repository reviewer had completed valid replacement before revocation; the closure reviewer acted afterwards and must reopen the appeal. Changed-context check: if both downstream services act under an enduring institutional mandate recorded independently of the liaison, revoking the liaison may require relinking authority rather than undoing their completed actions.
| Element | Purpose |
|---|---|
| Identifier | Bind the right record |
| Effective time | Set the boundary |
| Required action | Replace, pause or review |
| Reply route | Resolve uncertainty |
CHAPTER 7 OF 12 · RECONCILE CLOSURE
7. Reconcile acknowledgements by time, scope and authority
Compare each receipt with its sender’s authority at that time, the copy or action it covered and the effective revocation boundary. Mark receipts as historically valid, currently controlling, superseded, out of scope or unresolved.
Do not collapse all receipts into valid or invalid. Different parts of the chain can hold different evidential states for legitimate reasons.
CHAPTER 8 OF 12 · RECONCILE CLOSURE
8. Reconcile duplicated closure records
Find case-system status, shared spreadsheets, repository labels, email summaries and downstream decision logs. Choose one authoritative current closure state and link contradictory historical records to the reconciliation decision.
Deleting an inconsistent record removes the evidence needed to understand why two teams acted differently. Preserve it, label its status and prevent it from governing new work.
Evidence check
Verify that the control still reaches the intended decision under a changed but plausible context.
CHAPTER 9 OF 12 · RECONCILE CLOSURE
9. Repair materially affected decisions
Identify decisions made after the relevant authority changed or from a copy whose control was unproved. Reconsider only where the changed acknowledgement could alter evidence, procedure or outcome.
A revocation can expose a decision without proving that its conclusion is wrong. Record both changed and stable outcomes after review.
| State | Meaning |
|---|---|
| Historically valid | True when issued |
| Current | Governs now |
| Superseded | Preserved, not controlling |
| Unresolved | Needs an owner and trigger |
CHAPTER 10 OF 12 · MAKE IT DURABLE
10. Close with a chain-level evidence bundle
Closure should include the revocation record, delegation map, propagation log, current authority, repository evidence, affected-decision review and unresolved limits. Assign an owner for any residual route.
A collection of delivered emails is not a closure bundle if it does not show who could still act and which state now governs.
CHAPTER 11 OF 12 · MAKE IT DURABLE
11. Run a changed-context propagation test
Test a contractor exit, renamed team, shared-mailbox migration, unavailable principal and offline copy. Confirm that identifiers, required actions and escalation paths survive each transfer.
The purpose is not to prove every future route. It is to discover where authority information or revocation status disappears when context changes.
Evidence check
Confirm that versions, notices and unresolved limits remain visible in the final record.
CHAPTER 12 OF 12 · MAKE IT DURABLE
12. Audit chain gaps and reconciliation quality
Track unreachable delegates, unknown subdelegations, notices without action evidence, conflicting closure states, time to authoritative reconciliation, exposed decisions and repeat propagation failures.
The gold standard ends false closure by making the whole authority chain visible, while keeping claims proportionate to the evidence actually recovered.
| Measure | Warning |
|---|---|
| Unknown subdelegate | Population incomplete |
| Delivered only | Action unproved |
| Two current closures | Authority conflicted |
| Repeat chain gap | Design repair failed |
Frequently asked questions
Does revoking a delegate invalidate every action they took?
No. Evaluate authority, timing and scope. Earlier actions may remain historically valid even when later reliance must stop.
Is notifying the principal enough?
No, not when delegates, repositories or decision owners can continue the old closure independently.
Should conflicting closure records be deleted?
No. Preserve and label them, designate the authoritative current state and block superseded records from new decisions.
What proves propagation is complete?
Evidence that every material control point received the change, performed the required action or is explicitly bounded as residual exposure.
Continue through verified routes
Core routes
Anthropology subject root · Gold Standard of Education · Gold Standard directory · How X Works hub
Specialist routes
- Acknowledgement revocation, changed authority and reopening false closure
- Correction acknowledgement authenticity, delegated receipts and false closure
- Correction acknowledgement failures, unreachable recipients and residual exposure
- Corrective re-release propagation, cached copies and decision reconsideration