Jens
faeb58ef6d
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
51 lines
1.9 KiB
Markdown
51 lines
1.9 KiB
Markdown
# GeoIntel Constitution
|
|
|
|
This document defines the product laws. It has priority over ordinary specs when there is ambiguity.
|
|
|
|
## Article 1 — GeoAI Workbench First
|
|
|
|
GeoIntel is a GeoAI Workbench. It must prioritize geospatial processing, AI outputs, QA/QC and GIS exports over generic dashboards or visual polish.
|
|
|
|
## Article 2 — Correct Data Beats Pretty UI
|
|
|
|
When there is a tradeoff between visual presentation and correct geospatial processing, correct processing wins.
|
|
|
|
## Article 3 — Every Output Must Be Traceable
|
|
|
|
Every detection, segmentation, metric, export or QA score must be traceable to:
|
|
|
|
- source dataset;
|
|
- processing parameters;
|
|
- model/version if applicable;
|
|
- analysis run;
|
|
- timestamp;
|
|
- CRS and geometry assumptions.
|
|
|
|
## Article 4 — AI Never Owns the Truth
|
|
|
|
AI models produce candidate observations. Reference data, QA/QC and explicit metrics determine confidence and usefulness.
|
|
|
|
## Article 5 — Reproducibility Is Mandatory
|
|
|
|
An analysis run must be reproducible from stored metadata, parameters and input references.
|
|
|
|
## Article 6 — Async Processing Is the Default for Heavy Work
|
|
|
|
Raster operations, vector batch operations, detection, segmentation, QA/QC and exports should be implemented as background jobs when non-trivial.
|
|
|
|
## Article 7 — No Permanent Mock-Only Features
|
|
|
|
Demo fixtures are allowed, but every feature must expose a path toward real data operation. UI must not pretend unavailable functionality is complete.
|
|
|
|
## Article 8 — The Kempen Use Case Drives V1
|
|
|
|
Generic worldwide support is secondary. V1 must make the Geel/Mol/Turnhout/Kempen workflows excellent.
|
|
|
|
## Article 9 — Architecture Must Stay Extensible
|
|
|
|
Sentinel, DHMV, LiDAR, training, QGIS plugin and MLOps are future modules. V1 architecture may not block these.
|
|
|
|
## Article 10 — Documentation Is Part of the Product
|
|
|
|
Codex must update docs when contracts, behavior, workflows or limitations change.
|