Files
geointel/prompts/codex/M10_MASTER_AUTONOMOUS_PROMPT.md
T
Codex 6ea3586a3e
GeoIntel CI / docs-smoke (push) Has been cancelled
GeoIntel CI / contract-smoke (push) Has been cancelled
Initial GeoIntel V1 foundation
2026-06-16 23:36:32 +02:00

44 lines
1.5 KiB
Markdown

# M10 Master Autonomous Prompt for Codex
You are working on GeoIntel Kempen.
GeoIntel is a GeoAI Workbench for the Kempen. It must demonstrate GIS, remote sensing, raster/vector processing, AI object detection, segmentation architecture, QA/QC against reference geodata, and geospatial export.
Your job is to build the project in strict, reviewable passes.
## First Actions
1. Read `docs/18-ultra-prep/CODEX_START_HERE.md`.
2. Read all referenced files in order.
3. Inspect the repository state.
4. Identify the first incomplete pass from `prompts/codex/M10_PASS_SEQUENCE.md`.
5. Execute only that pass.
## Build Rules
- Backend-first where contracts or data models are involved.
- API-driven frontend only; no hidden local fake state as final behavior.
- Use durable abstractions for GIS, raster, detection, segmentation, QA/QC, and export.
- Do not overbuild future modules, but leave documented extension points.
- Every feature needs success, loading, empty, error, and unavailable states where relevant.
- Keep V1 scope frozen. LiDAR, training, MLOps, QGIS plugin are not V1.
## Freedom
You may improve implementation details, test coverage, documentation, typing, error handling, and UI clarity.
## Hard Constraints
Do not change the product identity, tech stack, database strategy, or V1 scope without explicit user approval.
## Required End-of-Pass Report
Use this format:
```md
# Codex Pass Report
## Pass
## Completed
## Changed Files
## Commands Run
## Test Results
## Known Limitations
## Risks / Follow-up
## Next Recommended Pass
```