[!info] Source-mirrored document — auto-generated Original: data-quality-incident-review.docx · edit the original, never this mirror. This L1 projection is machine-owned; use annotation sidecars for commentary and governed L2 views for synthesis.
%% AUTO-GENERATED BELOW — DO NOT EDIT %%
Extracted content
SYNTHETIC OPERATIONS RECORD
Illustrative Data Quality Incident Review
A worked example of how a stale public-source reference should fail safely without overwriting authoritative evidence.
| SCENARIO | A catalogue resource URL changes while the prior committed CSV snapshot remains readable. |
Impact
The workspace can still reproduce prior historical findings, but it cannot claim that the source is current. Refresh claims and dependent publication are paused. No live Ontario outage is asserted.
Timeline
| Step | Observation | Action |
| 1 | Resource lookup does not resolve to the recorded file | Mark source refresh blocked |
| 2 | Committed source hash is unchanged | Preserve snapshot and existing mirrors |
| 3 | Current license metadata is not yet reverified | Keep new ingestion disabled |
| 4 | Downstream findings cite the older snapshot | Add visible freshness warning |
Root cause and learning
The fictional failure is a mismatch between reachability, freshness, and authorization state. Treating those as one green/red field would hide important evidence. The workspace therefore tracks them separately.
Corrective actions
- Resolve the current authoritative catalogue resource and compare metadata.
- Review file list, headers, source notes, units, and coverage before replacement.
- Rerun contracts, fixture tests, mirror sync, lint, and no-data checks.
- Review every affected curated conclusion instead of carrying it forward automatically.
| CLOSURE | Close only after evidence is current, licensed, reproducible, and independently reviewed. |