geointel/prompts/codex/m14/CODEX_FIRST_DAY_MASTER_PROMPT.md

CODEX FIRST DAY MASTER PROMPT — M14 BUILD LAUNCH

You are implementing GeoIntel Kempen.

GeoIntel is a GeoAI Workbench for the Belgian Kempen. It is not a generic dashboard, chatbot, QGIS clone or report-only app. The product kernel is:

data -> processing -> geospatial output -> QA/QC -> export

Mandatory read order before coding

1. CODEX_START.md
2. docs/00-start/START_HERE.md
3. docs/governance/GEOINTEL_CONSTITUTION.md
4. docs/governance/ARCHITECTURE_INVARIANTS.md
5. docs/governance/FORBIDDEN_DECISIONS.md
6. docs/40-build-launch/SPRINT_1_SCOPE_FREEZE.md
7. docs/40-build-launch/BUILD_SUCCESS_DEFINITION.md
8. docs/40-build-launch/BUILD_ORDER_GRAPH.md
9. docs/40-build-launch/CODEX_STOP_RULES.md
10. docs/40-build-launch/MODULE_ACCEPTANCE_CRITERIA.md
11. docs/specs/GIS_STANDARDS.md
12. docs/specs/STATE_MACHINES.md
13. docs/30-codex-optimization/PROMPT_DISCIPLINE.md

First implementation mission

Build Sprint 1 only.

Sprint 1 goal:

Project -> Area -> Dataset upload/registration -> Metadata extraction -> PostGIS persistence -> Minimal map display -> GeoJSON export baseline

Build exactly this first

1. Backend foundation.
2. Database/PostGIS foundation.
3. Project API.
4. Area API.
5. Dataset API for GeoJSON.
6. Storage service.
7. Metadata extraction for GeoJSON.
8. Frontend shell.
9. MapLibre map.
10. Minimal dataset/area UI.
11. Readiness/smoke tests.

Do not build yet

• YOLO live inference.
• SAM live segmentation.
• GRB live WFS.
• Sentinel automation.
• LiDAR.
• Training Studio.
• AI Copilot.
• Full report generator.
• Multi-user auth.

If you encounter a task that belongs to a later module, add it to backlog/open issues and continue Sprint 1.

Quality rules

• Do not introduce undocumented technologies.
• Do not commit secrets.
• Do not hardcode machine-specific paths.
• Do not use permanent mock data.
• Golden fixtures are allowed for tests and initial UI development.
• Keep API responses canonical.
• Keep geometry rules consistent with GIS standards.
• Add tests/smoke checks where practical.
• Update docs/status/changelog when behavior changes.

Stop rules

Stop and report instead of continuing if:

• build breaks;
• tests fail and cannot be fixed within the active scope;
• architecture invariant would be violated;
• API contract conflict appears;
• a new dependency seems required but is not in ADRs;
• Sprint 1 scope would be exceeded.

Required final response after implementation pass

Report:

• files changed;
• implementation summary;
• commands run;
• test results;
• known limitations;
• architecture invariants touched or confirmed untouched;
• out-of-scope items deferred;
• next recommended pass.