geointel/prompts/codex/m13/DAY_1_OPTIMIZED_MASTER_PROMPT.md

Day 1 Optimized Master Prompt for Codex

You are working on GeoIntel Kempen, a GeoAI Workbench for the Belgian Kempen.

Your goal is not to redesign the product. Your goal is to implement the documented V1 foundation vertical slice in controlled passes.

Mandatory reading order

1. CODEX_START.md
2. docs/00-start/START_HERE.md
3. docs/30-codex-optimization/CODEX_OPTIMIZATION_OVERVIEW.md
4. docs/30-codex-optimization/CODEX_RUN_CHECKLIST.md
5. docs/30-codex-optimization/PROMPT_DISCIPLINE.md
6. docs/governance/GEOINTEL_CONSTITUTION.md
7. docs/governance/ARCHITECTURE_INVARIANTS.md
8. docs/governance/FORBIDDEN_DECISIONS.md
9. docs/20-run-readiness/PASS_SEQUENCE_FINAL.md
10. Active pass prompt only.
11. Relevant skill under skills/.

First objective

Build the foundation vertical slice in pass order:

Project → Area → Dataset metadata → Reference polygons → Predicted detections → QA/QC → GeoJSON export → Minimal UI.

Strict boundaries

Do not implement:

• heavy AI inference before the service contracts exist;
• LiDAR processing;
• model training;
• MLOps;
• QGIS plugin;
• advanced report generation;
• unrelated dashboards;
• new frameworks not approved by ADR.

Execution rules

• Work one pass at a time.
• Keep changes small and coherent.
• Use the relevant skill.
• Respect API/database contracts.
• Do not create permanent mock-only flows.
• Use fixtures only where documented.
• Run make readiness before and after major changes when possible.
• Update docs/CODEX_EXECUTION_LOG.md and CHANGELOG.md.

Required final report

End every pass with:

## Completed

## Changed files

## Commands run

## Test results

## Self-review scorecard

## Known limitations

## Contract deviations

## Next recommended pass

If a blocker appears, stop and report it instead of guessing.