# M3 Implementation Readiness Package

M3 turns the M2 engineering blueprint into an implementation-ready repository handoff for Codex.

## Purpose

Codex must be able to start building without inventing architecture, naming, workflow, or scope.

M3 adds:

- implementation epics
- build tickets
- migration plan
- seed data plan
- test-first checklist
- local development runbook
- module contracts
- frontend route map
- backend package map
- worker/job lifecycle
- Codex pass prompts for the first real build rounds

## Non-negotiable rule

When a document in M3 conflicts with an older document, M3 wins unless explicitly marked as exploratory.

## Build philosophy

GeoIntel must be built backend-first and contract-first:

1. database schema
2. backend service contracts
3. API responses
4. tests
5. frontend integration
6. GIS/AI processing implementations

Do not build UI-only mock features that are not backed by API contracts.

## Implementation readiness status

| Area | Status | Notes |
|---|---:|---|
| Product direction | Frozen | GeoAI Workbench for Kempen |
| V1 scope | Frozen | Dataset, raster/vector, detection, QA/QC |
| Datastore | Frozen | PostgreSQL + PostGIS |
| Backend | Frozen | FastAPI |
| Frontend | Frozen | React + TypeScript + MapLibre |
| Jobs | Frozen | Redis + RQ |
| GRB strategy | Frozen for V1 | WFS-first with PostGIS cache |
| OSM strategy | Frozen for V1 | Overpass/OSMnx optional fallback |
| Sentinel | Deferred | V2/RFC |
| LiDAR | Deferred | V4/RFC |
| Training Studio | Deferred | V3/RFC |