Find your next learning step
An amended remote-sensing product is not closed when the replacement file is uploaded. Closure depends on whether affected users can find the change, whether important derivatives were rerun or qualified, and whether unresolved work has an owner. User acknowledgement provides evidence that the notice reached the right dependency points. Residual derivative debt keeps incomplete reanalysis visible without holding every low-consequence historical object open forever.
Open the chapter contents · Remote Sensing root · Gold Standard of Education · How X Works
Chapter contents
Choose the route closest to the decision, or read from Chapter 1. The chapters remain open; these grouped routes are a navigable index.
Route 1 · Define the decision
Route 2 · Work the ledgers
Route 3 · Transfer the method
Route 4 · Check limits and evidence
Route 5 · Ask and continue
CHAPTER 1 OF 12 · DEFINE THE DECISION
1. Define closure as a system state
List the source amendment, affected assets, downstream dependencies, consequence classes, required notices, reruns, exemptions and closure authority. A technically corrected pixel product is only one node in that state.
Use objective completion evidence: replacement published, manifests updated, high-consequence derivatives resolved, affected owners notified and residual items entered in an owned debt ledger.
CHAPTER 2 OF 12 · DEFINE THE DECISION
2. Separate receipt, understanding and action
A delivered email shows transmission, not understanding. An acknowledgement should identify the object used, the version affected and the user’s chosen action: rerun, replace, qualify, exempt or retire.
Scale acknowledgement to consequence. A public notice may suit a low-risk archive, while an operational flood dashboard needs named owner confirmation and evidence that its pipeline changed.
CHAPTER 3 OF 12 · WORK THE LEDGERS
3. Build an amendment-closure register
A coastal classification amendment affects 42 scenes and five known derivative families.
| Derivative family | Consequence | Owner acknowledgement | Repair evidence | Closure state |
|---|---|---|---|---|
| Annual mosaic | High | Named and dated | Replacement checksum | Closed |
| Habitat trend model | High | Named and dated | Rerun report | Closed |
| Planning dashboard | Medium | Named | Release queued | Debt |
| Archived field reports | Low | Repository notice | Amendment attached | Qualified |
| Unknown local copies | Uncertain | None | Search completed | Residual risk |
The programme can close the amendment event while carrying the dashboard and unknown-copy work as explicit residual debt.
CHAPTER 4 OF 12 · WORK THE LEDGERS
4. Work a residual derivative-debt budget
The team scores consequence from 1–4, dependency confidence from 1–3 and effort from 1–3. Priority is consequence plus confidence; effort schedules the work rather than cancelling it.
| Residual item | Consequence | Confidence | Effort | Priority | Disposition |
|---|---|---|---|---|---|
| Planning dashboard | 3 | 3 | 2 | 6 | Next release |
| Two training notebooks | 1 | 3 | 1 | 4 | Replace links |
| Unregistered local exports | 2 | 1 | 3 | 3 | Targeted notice |
| Historical poster | 1 | 2 | 1 | 3 | Attach note |
| Retired pilot model | 1 | 3 | 3 | 4 | Document no rerun |
Each item receives an owner, due date, evidence requirement and escalation rule. A debt item without those fields is only a forgotten task.
CHAPTER 5 OF 12 · WORK THE LEDGERS
5. Set closure gates and reopen triggers
Require all high-consequence nodes resolved, medium-consequence nodes repaired or scheduled, notices published, acknowledgement exceptions escalated, identifiers linked and the residual ledger accepted by named authority.
Reopen if a new affected scene appears, a user reports an untracked derivative, the replacement is revised again or a supposedly exempt analysis changes materially under sensitivity testing.
CHAPTER 6 OF 12 · TRANSFER THE METHOD
6. Preserve versioned historical interpretation
Do not overwrite an old report to imply it used corrected data. Attach the amendment, link the original and replacement versions, and state whether the conclusion was rerun, qualified or unchanged.
For major content changes, persistent identifiers and explicit version relations help users cite the correct object. Keep asset manifests and processing dates when collection-level labels alone are too broad.
CHAPTER 7 OF 12 · TRANSFER THE METHOD
7. Changed-context transfer: wildfire severity maps
Transfer the method to a wildfire-severity product amended after cloud-shadow masks change. Recovery plans, ecological trend models and classroom maps depend on it differently.
Operational recovery layers are rerun and acknowledged by named owners. Classroom copies receive a repository notice. A retired demonstration remains unchanged with a visible version label. Closure records the residual local-copy risk rather than claiming universal replacement.
CHAPTER 8 OF 12 · TRANSFER THE METHOD
8. Connect propagation, reprocessing and verification closure
Start with amendment propagation and citation-version governance. Use reopened-stratum repair and historical product amendment to recover the correction’s evidence.
Return to delayed-label backfill, debt amortisation and verification-window closure when residual derivatives depend on late labels.
CHAPTER 9 OF 12 · CHECK LIMITS AND EVIDENCE
9. Limits and common misconceptions
Acknowledgement is not agreement that an amendment matters, and silence is not evidence of no dependency. Conversely, closure does not require rerunning a demonstrably unaffected or retired object.
A public landing-page update cannot reach every downloaded copy. Residual debt is not permission to ignore repair; it is a controlled representation of incomplete work, uncertainty and consequence.
CHAPTER 10 OF 12 · CHECK LIMITS AND EVIDENCE
10. Practical evidence and communication checks
Archive source and replacement identifiers, change scope, scene or tile list, manifests, dependency inventory, consequence classification, notices, recipients, acknowledgement status, repair evidence and exemptions.
For debt and closure, record owner, due date, priority logic, unresolved copies, non-rerun rationale, escalation, closure decision, reopen triggers and the recommended citation for each version.
CHAPTER 11 OF 12 · ASK AND CONTINUE
11. Frequently asked questions
Must every user reply before closure?
No. Define consequence-based acknowledgement rules and escalate missing high-consequence owners rather than waiting indefinitely for every low-risk recipient.
Can an amendment close with derivative debt?
Yes, when critical work is resolved and residual items have accepted owners, dates, evidence requirements and reopen triggers.
What counts as acknowledgement?
A dated record tying the user or system owner to the affected version and a documented action or justified exemption.
CHAPTER 12 OF 12 · ASK AND CONTINUE
12. Sources and next reading
USGS states on its Landsat Collection 2 page that users should consider replacing reprocessed data and subsequently derived products. The Collection 2 Reprocessing Events page identifies affected events. DataCite’s versioning guidance recommends metadata updates and new DOIs for major changes. The closure register and debt budget are original teaching examples.
Continue through the Remote Sensing root, the Gold Standard of Education and How X Works.
Top · Contents · Previous · How X Works