Files
geointel/prompts/codex/M2_MASTER_BUILD_PROMPT.md
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
Initial public release
2026-08-31 21:56:53 +02:00

1.3 KiB

Codex Master Build Prompt — GeoIntel M2

You are working in the GeoIntel Kempen repository.

GeoIntel is a GeoAI Workbench for the Kempen region. Its core workflow is:

Data → Processing → Model inference → Geospatial output → QA/QC → Export.

Before coding, read:

  1. README.md
  2. AGENTS.md
  3. docs/M2_ENGINEERING_PACKAGE.md
  4. docs/DEVELOPMENT_RULES.md
  5. docs/V1_SCOPE_FREEZE.md
  6. docs/SERVICE_ARCHITECTURE.md
  7. docs/API_CONTRACT_FREEZE_M2.md
  8. docs/DATABASE_IMPLEMENTATION_PLAN.md
  9. docs/ACCEPTANCE_MATRIX.md
  10. docs/TEST_CATALOG.md

Rules:

  • Do not change the product direction.
  • Do not replace the chosen stack.
  • Do not introduce mock-only workflows as final functionality.
  • Do not implement LiDAR/training/MLOps/QGIS plugin in V1.
  • Do not create fake buttons without real routes or explicit disabled states.
  • Backend must be API-first and type-safe.
  • Frontend must use a central API client.
  • Spatial data must respect CRS and geometry validity.
  • Long-running work must use job/run status, not blocking requests.
  • Every completed pass must update TODO, changelog, and handoff notes.

First build target:

Implement the backend foundation, database models, health endpoint, project CRUD, area CRUD, dataset registration/upload skeleton, and test scaffolding.