Initial public release
GeoIntel release gates / Compile, test, contracts and builds (push) Successful in 1m49s
GeoIntel release gates / Python and npm vulnerability policy (push) Successful in 21s
GeoIntel release gates / Production AI image, SBOM and container scan (push) Successful in 5m39s
GeoIntel release gates / Deploy exact gated revision to Unraid (push) Failing after 58m43s
GeoIntel release gates / Compile, test, contracts and builds (push) Successful in 1m49s
GeoIntel release gates / Python and npm vulnerability policy (push) Successful in 21s
GeoIntel release gates / Production AI image, SBOM and container scan (push) Successful in 5m39s
GeoIntel release gates / Deploy exact gated revision to Unraid (push) Failing after 58m43s
This commit is contained in:
@@ -0,0 +1,82 @@
|
||||
# RISK REGISTER
|
||||
|
||||
This register captures known build and product risks before the first implementation run.
|
||||
|
||||
## R1 — Scope creep during first Codex run
|
||||
|
||||
Impact: high.
|
||||
|
||||
Mitigation:
|
||||
|
||||
- Follow `SPRINT_1_SCOPE_FREEZE.md`.
|
||||
- Use `CODEX_STOP_RULES.md`.
|
||||
- Add out-of-scope items to backlog.
|
||||
|
||||
## R2 — External data source instability
|
||||
|
||||
Impact: medium/high.
|
||||
|
||||
Mitigation:
|
||||
|
||||
- Use golden fixtures in Sprint 1.
|
||||
- Add live adapters later.
|
||||
- Cache retrieved external data.
|
||||
|
||||
## R3 — GIS CRS mistakes
|
||||
|
||||
Impact: high.
|
||||
|
||||
Mitigation:
|
||||
|
||||
- Follow `docs/specs/GIS_STANDARDS.md`.
|
||||
- Validate geometries.
|
||||
- Store SRID explicitly.
|
||||
- Test fixture bounds.
|
||||
|
||||
## R4 — Raster files too large
|
||||
|
||||
Impact: medium.
|
||||
|
||||
Mitigation:
|
||||
|
||||
- No heavy raster processing in Sprint 1.
|
||||
- Use tiling strategy later.
|
||||
- Enforce file size limits when upload is implemented.
|
||||
|
||||
## R5 — AI modules introduced too early
|
||||
|
||||
Impact: high.
|
||||
|
||||
Mitigation:
|
||||
|
||||
- Keep live inference out of Sprint 1.
|
||||
- Implement adapter boundaries only when needed.
|
||||
- Use imported demo detections before live models.
|
||||
|
||||
## R6 — Frontend becomes dashboard-first
|
||||
|
||||
Impact: medium.
|
||||
|
||||
Mitigation:
|
||||
|
||||
- Follow Constitution: data -> processing -> QA/QC -> export.
|
||||
- Map supports analysis; it is not the product by itself.
|
||||
|
||||
## R7 — Mock data becomes permanent
|
||||
|
||||
Impact: high.
|
||||
|
||||
Mitigation:
|
||||
|
||||
- Golden fixtures are contract data, not fake product behavior.
|
||||
- Mark demo/fixture paths clearly.
|
||||
- Production endpoints must use persisted data.
|
||||
|
||||
## R8 — Too many competing docs
|
||||
|
||||
Impact: medium.
|
||||
|
||||
Mitigation:
|
||||
|
||||
- Follow `CODEX_START.md` and `docs/00-start/START_HERE.md`.
|
||||
- M14 launch docs supersede older first-run plans where conflicts exist.
|
||||
Reference in New Issue
Block a user