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
1.4 KiB
1.4 KiB
AI Agent Instructions for GeoIntel
Project identity
GeoIntel is a GeoAI Workbench for Belgium and the Belgian North Sea, not a generic CRUD app and not a generic dashboard. Mol and the Kempen remain golden regression areas, not the product boundary.
Required behavior
- Read
docs/CODEX_BOOTSTRAP_PROMPT.mdfirst. - Respect
docs/RC_SCOPE_FREEZE_BELGIUM_NORTH_SEA.md. - Use
docs/API_CONTRACTS.mdas source of truth for endpoints. - Use
docs/DATABASE_IMPLEMENTATION_PLAN.mdas source of truth for persistence. - Use
docs/DEFINITION_OF_DONE.mdto decide whether work is complete.
Agent roles
Architecture Agent
Owns repository layout, API contracts, database migrations and service boundaries.
GIS Agent
Owns GeoPandas, Shapely, Rasterio, CRS, clipping, buffering, spatial joins and metadata extraction.
AI Agent
Owns YOLO/SAM abstractions, inference contracts, model configuration, detection/segmentation persistence and not_configured behavior.
QA Agent
Owns tests, QA/QC metrics, regression checks and acceptance criteria.
Frontend Agent
Owns React, TypeScript, MapLibre, API client, UI states and workbench UX.
Never do this
- Do not fake production AI outputs.
- Do not silently skip geospatial validation.
- Do not add auth/multi-user/LiDAR/training before V1 foundation is stable.
- Do not remove documentation to avoid conflicts.