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,84 @@
+# M8 Tomorrow Execution Pack
+
+This package exists so Codex can start tomorrow with minimal manual steering.
+
+## Operating mode
+
+Codex must work in controlled autonomous passes. Each pass must:
+
+1. read the relevant docs before editing;
+2. implement one coherent layer only;
+3. run the documented validation commands;
+4. write a concise completion report;
+5. update TODO, CHANGELOG and CODEX_EXECUTION_LOG;
+6. stop when a blocker requires product/architecture judgement.
+
+## Non-negotiable product direction
+
+GeoIntel Kempen is a **GeoAI Workbench**, not a generic dashboard and not a CRUD demo.
+The V1 vertical slice must prove:
+
+- geospatial project/area/dataset management;
+- raster/vector metadata extraction;
+- map-based spatial workflow;
+- PostGIS-ready geometry handling;
+- controlled AI detection pipeline scaffolding;
+- QA/QC against reference geodata;
+- geospatial export.
+
+## Day-1 success condition
+
+A successful first Codex day should end with a running foundation that can be started locally and demonstrates:
+
+- backend health endpoint;
+- database connection and migrations;
+- project/area/dataset APIs;
+- frontend shell with routes;
+- map workspace placeholder wired to API state;
+- deterministic fixtures and smoke checks;
+- no uncontrolled mock-only business logic.
+
+## Recommended execution order
+
+1. `prompts/codex/day-1/00_START_HERE.md`
+2. `prompts/codex/day-1/01_REPO_AUDIT_AND_PLAN.md`
+3. `prompts/codex/day-1/02_BACKEND_FOUNDATION.md`
+4. `prompts/codex/day-1/03_DATABASE_AND_DOMAIN.md`
+5. `prompts/codex/day-1/04_PROJECT_AREA_DATASET_API.md`
+6. `prompts/codex/day-1/05_FRONTEND_SHELL.md`
+7. `prompts/codex/day-1/06_RASTER_VECTOR_METADATA.md`
+8. `prompts/codex/day-1/07_VERTICAL_SLICE_STABILIZATION.md`
+
+## What Codex may improve without asking
+
+Codex may improve naming, folder hygiene, small helper abstractions, test coverage, typing, validation, error messages, and developer ergonomics if the changes preserve the documented contracts.
+
+## What Codex may not change without explicit approval
+
+Codex may not change:
+
+- product positioning;
+- selected stack;
+- V1 scope boundaries;
+- database aggregate names;
+- API envelope conventions;
+- storage layout;
+- QA/QC metric definitions;
+- GRB as primary reference strategy;
+- incremental build discipline.
+
+## Required end-of-pass response format
+
+Every pass must end with:
+
+```text
+PASS COMPLETED: <name>
+CHANGED FILES:
+- ...
+VALIDATION RUN:
+- command: result
+OPEN ISSUES:
+- ... or none
+NEXT RECOMMENDED PASS:
+- ...
+```