docs: record frozen residual scratch accurately
GeoIntel release gates / Compile, test, contracts and builds (push) Failing after 55s
GeoIntel release gates / Python and npm vulnerability policy (push) Failing after 41s
GeoIntel release gates / GIS image, SBOM and container scan (push) Failing after 1m52s
GeoIntel release gates / AI image, SBOM and container scan (push) Skipped

This commit is contained in:
2026-08-26 22:44:16 +02:00
parent 29033b5159
commit 67b6b6285e
+15 -7
View File
@@ -10,19 +10,24 @@ guardrails without widening any data-source or AI accuracy claim.
- Guest access is opt-in instead of enabled by default.
- Configured YOLO validation-scope enforcement is opt-out only in
non-production research/development contexts.
- Production YOLO uses CUDA and an immutable validation-scope manifest; when
scope evidence is absent or invalid, inference fails closed rather than being
treated as validated.
- Production YOLO uses CUDA. Configured inference remains bound to the existing
immutable validation-scope service; absent or invalid scope evidence keeps
YOLO unavailable without taking the GIS runtime offline.
### Repository hygiene
- `.codex-input/` and `.codex-artifacts/` are forbidden tracked paths.
- New `.codex-input/` and `.codex-artifacts/` content is forbidden.
- Transient SQLite WAL/SHM files are forbidden.
- A tracked-file size budget prevents large local scratch artifacts from
silently returning; governed accuracy evidence and presentation assets have
explicit narrow allowlists.
- Cross-project DockDeck inputs and generated GeoIntel scratch artifacts are
removed from the current repository tree.
- All SQLite/WAL state, local calibration/error-review scratch, large contact
sheets and DockDeck archives were removed from the current repository tree.
- The remaining 32 DockDeck Stitch blobs could not be mass-deleted after the
platform safety layer stopped further destructive operations. They are
therefore frozen by exact path and exact Git blob SHA: they may be deleted,
but any modification, replacement or new `.codex-input` file fails the
release gate.
Historical Git objects are intentionally not rewritten by this change. Purging
old blobs requires a coordinated destructive history rewrite and force-update
@@ -47,6 +52,8 @@ into this hardening pass. ESLint 9 reached upstream end-of-life in August 2026.
- CI verifies those policies so mutable references cannot silently return.
- Both GIS and AI release images are built, SBOMed and scanned under the same
vulnerability policy.
- The Unraid Torch index default is aligned with the retained CUDA 12.8 runtime
evidence instead of silently selecting a different CUDA wheel channel.
### Deployment gating
@@ -65,7 +72,8 @@ This hardening does **not**:
- convert guest mode into tenant isolation;
- convert the PostgreSQL/in-process worker model into a distributed queue;
- purge historical Git objects;
- alter official source semantics or CRS contracts.
- alter official source semantics or CRS contracts;
- claim the 32 safety-frozen legacy Stitch blobs have already been removed.
## External repository control