# M3 Handoff Summary

M3 prepares the repository for the first implementation sprint.

## Added in M3

- implementation epics
- ticket-level build plan
- migration plan
- seed data plan
- local development runbook
- backend package map
- frontend route map
- module contracts
- job lifecycle
- Codex pass matrix
- Codex prompts for passes 05 through 12
- known limitations

## Recommended next action

Start Codex with:

1. `prompts/codex/M2_MASTER_BUILD_PROMPT.md`
2. `docs/CODEX_PASS_MATRIX_M3.md`
3. `prompts/codex/PASS_01_BACKEND_FOUNDATION.md`

Then continue pass-by-pass.

## Most important build target

A complete V0.1 should prove:

- project creation
- area creation
- dataset upload
- raster/vector metadata
- fixture detection
- QA/QC against reference buildings
- GeoJSON export

This is enough to demonstrate the core GeoAI workflow before heavy AI integrations are added.