# M12 Run Readiness Final Audit

## Purpose

This document converts the large GeoIntel preparation set into a practical final execution layer for Codex. The repo contains many useful milestone documents, but the implementation run must follow one canonical path.

## Final readiness status

GeoIntel is ready to start implementation when Codex follows the canonical path below and does not treat older milestone documents as competing instructions.

## Canonical control stack

1. Product identity: `docs/governance/GEOINTEL_CONSTITUTION.md`
2. Architecture invariants: `docs/governance/ARCHITECTURE_INVARIANTS.md`
3. Forbidden decisions: `docs/governance/FORBIDDEN_DECISIONS.md`
4. Decision precedence: `docs/governance/DECISION_PRECEDENCE.md`
5. Domain models: `docs/specs/CANONICAL_DOMAIN_MODELS.md`
6. GIS standards: `docs/specs/GIS_STANDARDS.md`
7. Raster standards: `docs/specs/RASTER_STANDARDS.md`
8. State machines: `docs/specs/STATE_MACHINES.md`
9. Golden paths: `docs/workflows/GOLDEN_PATHS.md`
10. Build dependency graph: `docs/build/BUILD_ORDER_DEPENDENCY_GRAPH.md`
11. Final pass sequence: `docs/20-run-readiness/PASS_SEQUENCE_FINAL.md`
12. Day 1 master prompt: `prompts/codex/final/DAY_1_MASTER_PROMPT.md`

## Older milestone documents

Older M0-M11 documents remain valuable as supporting context. They are not deleted because they contain useful details, but they must not override the canonical control stack.

When in doubt, Codex must follow:

`CODEX_START.md` → `START_HERE.md` → M12 run-readiness docs → governance/specs → implementation prompts.

## Final V1 scope

V1 is the foundation GeoAI Workbench vertical slice.

V1 includes:

- backend skeleton;
- database models and migrations;
- project CRUD;
- area CRUD with geometry validation;
- dataset registration/upload metadata;
- vector import using fixtures first;
- raster metadata extraction where libraries are available;
- reference polygon loading;
- predicted detection import;
- QA/QC matching against reference polygons;
- metric persistence;
- GeoJSON export;
- minimal frontend workbench;
- status/error handling;
- smoke tests.

V1 excludes:

- live production GRB sync as a blocker;
- heavy model training;
- full SAM/YOLO production inference as a blocker;
- LiDAR processing;
- MLOps registry implementation;
- QGIS plugin;
- multi-user permissions;
- advanced PDF report generation.

## Implementation policy

Codex may improve implementation details, UX clarity, tests, types, helper abstractions and documentation. Codex must not alter product identity, stack, state machines, response envelope, database choice, CRS policy or golden path priority without an ADR proposal.

## Final release target

The first release target is not a complete GeoAI platform. It is a stable, demonstrable vertical slice proving that GeoIntel can move geospatial data through the core pipeline:

`data → processing → geospatial output → QA/QC → export`.