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.2 KiB
1.2 KiB
Codex Phase 1 Prompt — Backend Foundation
You are working in the GeoIntel Kempen repository.
Read these files first:
docs/PRODUCT_BLUEPRINT.mddocs/DEVELOPMENT_RULES.mddocs/DATABASE_SCHEMA.mddocs/API_SPECIFICATION.mddocs/STORAGE_ARCHITECTURE.mddocs/IMPLEMENTATION_BACKLOG.md
Mission
Build the backend foundation for GeoIntel Kempen without implementing fake features.
Required output
- FastAPI backend skeleton.
- Config/settings module.
- Database connection to PostgreSQL/PostGIS.
- Initial models for projects, areas, datasets, layers, analysis runs, metrics, exports and jobs.
- Alembic migrations if applicable.
- Health endpoint.
- Basic project/area/dataset CRUD endpoints where safe.
- File storage service skeleton with real path handling.
- Tests for config, health and core models where feasible.
Non-negotiable rules
- Do not fake GIS processing.
- Do not create endpoints that pretend analysis was completed.
- Every geometry field must be designed for PostGIS.
- Every dataset must support metadata.
- Keep code modular.
- Update TODO/backlog after changes.
Delivery format
At the end, report:
- Files changed.
- What works.
- How to run.
- Tests run.
- Remaining tasks.