# Codex Handoff Briefing

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

## Read first

1. `README.md`
2. `AGENTS.md`
3. `docs/V1_SCOPE_FREEZE.md`
4. `docs/SERVICE_ARCHITECTURE.md`
5. `docs/REPOSITORY_CONVENTIONS.md`
6. `docs/15-tomorrow-execution/M8_TOMORROW_EXECUTION_PACK.md`
7. `docs/15-tomorrow-execution/DAY_1_EXECUTION_TIMELINE.md`
8. the current pass prompt under `prompts/codex/day-1/`

## Build philosophy

Build thin but real vertical slices. Do not hide missing functionality behind convincing UI. A small working API with tests is better than a beautiful mock.

## The first usable vertical slice

The first vertical slice is:

```text
Project -> Area -> Dataset registration -> Metadata -> Map/Workbench display -> Export-ready internal structure
```

Object detection, segmentation and QA/QC are important, but they must sit on a stable foundation.

## Common failure modes to avoid

- Creating frontend-only mock data that bypasses API state.
- Mixing geometry parsing into random route handlers.
- Adding AI dependencies before the data model is stable.
- Hardcoding local file paths.
- Ignoring CRS metadata.
- Creating database models that cannot handle future PostGIS geometries.
- Implementing upload without storage policy.
- Writing TODOs instead of completing the requested pass.

## Improvement freedom

You may add helper modules, stricter validation, better tests, and cleaner component structure. You may not change the product scope or stack.