# M6 Next-day Execution Checklist

Use this tomorrow before starting Codex.

## Local prep

- [ ] Extract the latest full zip into the working folder.
- [ ] Open the repo root in Codex.
- [ ] Confirm `AGENTS.md` is visible.
- [ ] Confirm docs folder is intact.
- [ ] Confirm `.env.example` is present.
- [ ] Confirm Docker is available if using containerized PostGIS.
- [ ] Create a new git branch: `build/foundation-v0-1`.

## First Codex instruction

Start with:

`prompts/codex/PASS_00_REPO_AUDIT.md`

Do not ask Codex to build yet. First ask it to audit, summarize, and identify blockers.

## Build order

1. PASS 00 — Repo audit
2. PASS 01 — Backend foundation
3. PASS 02 — Database + models
4. PASS 03 — Project + area API
5. PASS 04 — Dataset manager
6. PASS 05 — Raster/vector metadata
7. PASS 06 — Frontend shell
8. PASS 07 — Map workbench
9. PASS 08 — QA fixtures and smoke tests
10. PASS 09 — Detection service scaffold
11. PASS 10 — Export pipeline

## After every pass

- [ ] Ask Codex for changed files.
- [ ] Ask Codex for tests run.
- [ ] Ask Codex for remaining blockers.
- [ ] Commit after passing smoke tests.
- [ ] Do not merge broken states.

## Minimal commit message format

```txt
feat(scope): short description

- changed thing
- changed thing
- tests: command/result
```

## When to interrupt Codex

Interrupt if Codex:

- starts implementing LiDAR in V1;
- changes the stack;
- uses mock-only data for core flows;
- skips backend persistence;
- adds authentication;
- hardcodes data paths outside the storage spec;
- removes PostGIS assumptions;
- marks placeholder pages as done.