geointel/docs/CODEX_BOOTSTRAP_PROMPT.md

Codex Bootstrap Prompt — GeoIntel Kempen

You are building GeoIntel Kempen, a GeoAI Workbench for the Belgian Kempen region. The repository already contains the specification set. Read these documents before editing code:

1. docs/SPECIFICATION_FREEZE_M0.md
2. docs/V1_SCOPE_FREEZE.md
3. docs/DEVELOPMENT_RULES.md
4. docs/REPOSITORY_CONVENTIONS.md
5. docs/SERVICE_ARCHITECTURE.md
6. docs/API_CONTRACTS.md
7. docs/DATABASE_IMPLEMENTATION_PLAN.md
8. docs/CODEX_EXECUTION_PLAN.md
9. docs/TEST_STRATEGY.md
10. docs/DEFINITION_OF_DONE.md

Non-negotiable build rules

• Build backend-first and API-driven.
• Do not silently replace geospatial logic with fake logic.
• Mock data is allowed only as explicit fixtures in fixtures/ or tests/fixtures/.
• Every implemented endpoint must have request/response schemas.
• Every implemented service must have at least one focused test or a documented reason why it cannot yet be tested.
• Every feature must expose error states, loading states and empty states in the frontend.
• Do not introduce new major dependencies without adding them to docs/DEPENDENCY_POLICY.md and explaining why they are needed.
• Do not expand V1 scope beyond docs/V1_SCOPE_FREEZE.md.
• Preserve existing docs and update them when implementation diverges.

First build objective

Create a runnable foundation with:

• FastAPI backend skeleton.
• React + TypeScript frontend skeleton.
• Docker Compose with PostGIS, backend and frontend.
• Health endpoints.
• Project and Area CRUD.
• Dataset metadata model.
• Repository/service structure matching docs/REPOSITORY_CONVENTIONS.md.
• Initial tests and lint commands.

Required handoff after every pass

Update docs/CODEX_EXECUTION_LOG.md with:

• What changed.
• What was tested.
• What remains open.
• Known limitations.
• Next recommended pass.