Initial GeoIntel V1 foundation

2026-06-16 23:36:32 +02:00
commit 6ea3586a3e
605 changed files with 45284 additions and 0 deletions
@@ -0,0 +1,122 @@
+# START HERE — GeoIntel Architect Canonical Entry Point
+
+This is the single canonical entry point for Codex, reviewers and future contributors.
+Older handoff files are historical. If documents conflict, follow the precedence order in this file.
+
+## Current milestone
+
+**M14 — Build Launch Package**
+
+The repository is no longer only a documentation bundle. It is now a specification-controlled engineering repo for building GeoIntel Kempen as a GeoAI Workbench.
+
+## Product one-liner
+
+GeoIntel Kempen is a GeoAI Workbench for the Belgian Kempen that processes raster data, vector data and AI outputs into geospatially correct detections, segmentations, QA/QC metrics and exports.
+
+## Non-negotiable product identity
+
+GeoIntel is:
+
+- a GeoAI Workbench;
+- a geospatial data processing product;
+- a platform for raster/vector/AI/QA workflows;
+- a portfolio-grade implementation of GIS, remote sensing, computer vision and data engineering.
+
+GeoIntel is not primarily:
+
+- a generic dashboard;
+- a reporting-only tool;
+- a chatbot;
+- a QGIS clone;
+- a mock demo app.
+
+## Canonical read order for Codex
+
+Read these files in order before coding:
+
+1. `docs/00-start/START_HERE.md`
+2. `docs/governance/GEOINTEL_CONSTITUTION.md`
+3. `docs/governance/ARCHITECTURE_INVARIANTS.md`
+4. `docs/governance/FORBIDDEN_DECISIONS.md`
+5. `docs/governance/DECISION_PRECEDENCE.md`
+6. `docs/specs/CANONICAL_DOMAIN_MODELS.md`
+7. `docs/specs/GIS_STANDARDS.md`
+8. `docs/specs/RASTER_STANDARDS.md`
+9. `docs/specs/STATE_MACHINES.md`
+10. `docs/workflows/GOLDEN_PATHS.md`
+11. `docs/build/BUILD_ORDER_DEPENDENCY_GRAPH.md`
+12. `docs/build/CODEX_OPERATING_SYSTEM.md`
+13. `docs/40-build-launch/SPRINT_1_SCOPE_FREEZE.md`
+14. `docs/40-build-launch/BUILD_SUCCESS_DEFINITION.md`
+15. `docs/40-build-launch/CODEX_STOP_RULES.md`
+16. `prompts/codex/m14/CODEX_FIRST_DAY_MASTER_PROMPT.md`
+
+## Canonical first implementation target
+
+The first vertical slice is:
+
+**Project + Area + Dataset + Raster/Vector metadata + Reference polygons + Detection result import + QA/QC + GeoJSON export.**
+
+Do not start with full AI inference if the foundation is not stable. The first goal is to prove the data lifecycle and geospatial correctness.
+
+## Canonical V1 golden path
+
+1. Create project.
+2. Create/select an Area in the Kempen.
+3. Upload or load a raster/vector dataset.
+4. Extract and persist metadata.
+5. Load reference polygons, initially demo GRB-like buildings.
+6. Import or generate predicted building detections.
+7. Convert outputs to valid geospatial features.
+8. Run QA/QC against the reference layer.
+9. Show results on the map and in metrics panels.
+10. Export GeoJSON.
+
+## What Codex may improve autonomously
+
+Codex may improve:
+
+- implementation quality;
+- test coverage;
+- type safety;
+- error handling;
+- UI clarity;
+- documentation clarity;
+- internal helper abstractions;
+- performance within defined budgets.
+
+Codex may not change:
+
+- product identity;
+- core stack;
+- CRS policy;
+- database choice;
+- async job architecture;
+- API envelope shape;
+- state machine names;
+- golden path priority;
+- forbidden decisions.
+
+## Conflict resolution
+
+If any older document conflicts with this M14 launch layer, follow this order:
+
+1. Constitution and architecture invariants.
+2. Forbidden decisions.
+3. State machines and canonical models.
+4. API/database contracts.
+5. Build order dependency graph.
+6. M14 build-launch docs for first-run scope and stop rules.
+7. Older milestone handoff documents.
+
+## Required pass ending
+
+Every Codex pass must end with:
+
+- files changed;
+- commands run;
+- tests passed/failed;
+- known limitations;
+- whether golden paths still pass;
+- whether any architecture invariant was touched;
+- next recommended pass.