The Gold Standard · Ecology
Make the decision path visible
An exception can expire on paper while living on in dashboards, field instructions, model defaults and old approval letters. If those legacy uses continue to generate current decisions, the system still has two standards even when the exception register says closed.
The gold standard retires the authority, migrates every active use, marks historical records without rewriting them and tests that new decisions resolve to one controlling rule. Unresolved legacy paths are either converted, restricted or withdrawn.
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 · INVENTORY LEGACY USE
1. Define retirement as an operational state
State the exact authority ending, its last permitted use date and the controlling replacement rule.
Retirement is not complete merely because no new exception letters are issued. Current systems must stop making decisions under the old terms.
CHAPTER 2 OF 12 · INVENTORY LEGACY USE
2. Inventory every legacy dependency
Search approvals, datasets, dashboards, APIs, models, field protocols, templates, reports and training materials for exception identifiers and distinctive rules.
Include informal spreadsheets and recurring manual work. Legacy use often survives outside the canonical register.
Evidence check
Check whether the scope, owner and decision consequence are explicit before continuing.
CHAPTER 3 OF 12 · INVENTORY LEGACY USE
3. Classify historical, active and latent uses
Historical records explain past decisions; active uses shape current outputs; latent uses can be reactivated by a template, cache or seasonal workflow.
Treat these classes differently. Historical preservation is compatible with retirement, but silent operational reuse is not.
| Use | Question |
|---|---|
| Approval | Still authorising work? |
| Dataset | Status label current? |
| Model | Rule embedded? |
| Template | Can old path restart? |
CHAPTER 4 OF 12 · PLAN MIGRATION
4. Choose a migration route for each active use
Convert to the controlling rule, collect supplementary evidence, restrict scope, replace the output or withdraw the use.
Assign an owner, due date, validation evidence and consequence if migration fails.
CHAPTER 5 OF 12 · PLAN MIGRATION
5. Protect continuity without preserving obsolete authority
Link old and new versions, translate identifiers and document where scientific meaning changes.
A bridge may be needed for trend interpretation, but it must not let an obsolete approval test govern new ecological claims.
Evidence check
Ask a second reviewer to reconstruct the example from the preserved evidence and stated assumptions.
CHAPTER 6 OF 12 · PLAN MIGRATION
6. Worked example: the exception closes but the dashboard still labels data approved
Suppose a seasonal exception expires after wet-season validation is completed. The approval register is updated, yet a dashboard continues using an old status table and presents new observations under the exception label. Users cannot tell whether the controlling rule was applied.
The team freezes promotion, rebuilds status from the current approval service, links historical exception periods and validates that all post-retirement observations use the normal rule. Changed-context check: if the dashboard is a preserved historical snapshot clearly labelled with its effective period and non-current status, it may remain accessible without undermining migration.
| Route | Use |
|---|---|
| Convert | Normal rule met |
| Supplement | Evidence gap closable |
| Restrict | Bounded safe use |
| Withdraw | Cannot control risk |
CHAPTER 7 OF 12 · RETIRE SAFELY
7. Validate conversion under the controlling rule
Reassess active sites, parameters and outputs using the normal evidence and approval criteria. Document any additional safeguards or exclusions.
Do not assume evidence collected during the exception automatically satisfies the replacement rule; test fitness for the intended current use.
CHAPTER 8 OF 12 · RETIRE SAFELY
8. Withdraw uses that cannot migrate safely
Stop publication or operational reliance where evidence is insufficient and no bounded restriction can control risk.
Explain the affected scope, preserve the record and provide a route for future re-entry when requirements are met.
Evidence check
Verify that the control still reaches the intended decision under a changed but plausible context.
CHAPTER 9 OF 12 · RETIRE SAFELY
9. Communicate final status to every user group
Tell site teams, reviewers, model owners and downstream recipients which standard now controls, what changed and where historical exceptions remain visible.
Use plain effective dates and descriptive links. Avoid labels such as legacy accepted that can be mistaken for current approval.
| Check | Evidence |
|---|---|
| Authority | Effective date recorded |
| Systems | Old path disabled |
| Outputs | Current version visible |
| Users | Controlling rule understood |
CHAPTER 10 OF 12 · PROVE ONE STANDARD
10. Disable reactivation paths
Remove old options from templates, permissions, APIs and automated jobs; expire caches and update training.
Preserve authorised archives, but make the operational path to the old rule visibly unavailable.
CHAPTER 11 OF 12 · PROVE ONE STANDARD
11. Run one-standard verification tests
Sample new decisions, trace their rule version, inspect outputs for exception identifiers and ask users to identify the controlling standard.
Test seasonal and rarely used workflows as well as daily systems. Dormant paths often evade ordinary closure checks.
Evidence check
Confirm that versions, notices and unresolved limits remain visible in the final record.
CHAPTER 12 OF 12 · PROVE ONE STANDARD
12. Audit residual use until retirement is stable
Track old-rule calls, stale labels, unresolved migrations, withdrawal status, user confusion and reactivation attempts.
The gold standard preserves historical truth while ending current dual governance. Retirement is proven by decisions, not declarations.
| Measure | Warning |
|---|---|
| Old-rule call | Path still active |
| Stale label | User confusion |
| Unmigrated case | Dual standard persists |
| Reactivation | Retirement control weak |
Frequently asked questions
Can historical exception records remain public?
Yes, when their effective period and superseded status are clear and they cannot be mistaken for current approval.
Must every legacy use be converted?
No. Uses that cannot meet the controlling rule may be restricted, replaced or withdrawn.
What proves that one standard now governs?
New decisions trace to the controlling rule, operational old paths are disabled and residual-use checks find no hidden exceptions.
Should old identifiers be deleted?
No. Preserve identifiers and links needed to reconstruct historical decisions while preventing operational reuse.
Continue through verified routes
Core routes
Ecology subject root · Gold Standard of Education · Gold Standard directory · How X Works hub
Specialist routes
- Transition exceptions, sunset review and ending dual standards
- Reconciliation transition and dual-rule cutovers
- Precedent drift and exception creep
- Precedent conflict and authoritative reconciliation