Context
When a Cluster B error is discovered after data has been uploaded to the FAO Appwrite bucket, there is no documented procedure for correction. The data delivery chain has stages beyond the code:
- Clear stale disk cache
- Re-run pipeline with corrected shapefiles/code
- Re-upload corrected files to Appwrite
- Notify UN FAO that previous delivery was affected
- FAO retracts or replaces old data in their systems
Steps 3-5 have no documented procedure, no automation, and no mechanism to identify which prior deliveries are affected.
Requirements
Write a correction procedure document (docs/standards/data_correction_procedure.md or similar) that specifies:
- How to identify affected deliveries (which file_ids, which time periods)
- How to re-upload corrected data to Appwrite
- How to notify the FAO technical team
- Who is responsible for each step
- Whether the correction is a new upload or a replacement of the existing file
Risk Register
C-22 (Tier 3). Part of Cluster B (operational impact dimension).
Note
This is a process documentation task, not a code change. It requires input from whoever manages the FAO relationship and the Appwrite infrastructure.
Context
When a Cluster B error is discovered after data has been uploaded to the FAO Appwrite bucket, there is no documented procedure for correction. The data delivery chain has stages beyond the code:
Steps 3-5 have no documented procedure, no automation, and no mechanism to identify which prior deliveries are affected.
Requirements
Write a correction procedure document (
docs/standards/data_correction_procedure.mdor similar) that specifies:Risk Register
C-22 (Tier 3). Part of Cluster B (operational impact dimension).
Note
This is a process documentation task, not a code change. It requires input from whoever manages the FAO relationship and the Appwrite infrastructure.