Jens/geointel
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Operationalize RC10 data retention
GeoIntel release gates / Compile, test, contracts and builds (push) Canceled after 0s
Details
GeoIntel release gates / Python and npm vulnerability policy (push) Canceled after 0s
Details
GeoIntel release gates / GIS image, SBOM and container scan (push) Canceled after 0s
Details

Browse Source
This commit is contained in:
Codex
2026-07-18 06:58:10 +02:00
parent bf867f8f4f
commit 7b96037853
22 changed files with 1306 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
backend/README.md
+14
View File
@@ -1920,3 +1920,17 @@ file. It never imports provider data or writes directly to database tables.
Explicit demo seeding also reactivates its own archived technical project.
This keeps the opt-in fixture workflow selectable without changing the normal
active-project lifecycle.
## Data operations and retention
The runtime packages `audit_data_operations.py`,
`cleanup_storage_artifacts.py` and the shared release-backup guard. The audit
is read-only and combines disk pressure, storage lifecycle, persisted path
integrity, failed-work counts and national/regional/maritime source-family
inventory. Cleanup is limited to old unreferenced derived/cache/export files.
Unknown paths, official source material, uploads, models and release/operator
evidence are protected by default. Apply mode requires an exact confirmation,
an explicit candidate ceiling and a recent checksum-verified database plus
SHA-256 storage backup mounted read-only under `/app/backups`. See
`docs/DATA_OPERATIONS_RUNBOOK.md`.