geointel/docs/11-quality/SELF_REVIEW_CHECKLIST.md

Self-Review Checklist for Codex

Codex must run this checklist before ending every implementation pass.

Product Fit

• Does the work still support GeoIntel as a GeoAI Workbench?
• Did the pass avoid adding unrelated dashboard/chat features?
• Is the Kempen/GRB-first strategy preserved?

API and Backend

• Are new endpoints documented?
• Do endpoints return stable JSON shapes?
• Are errors structured and useful?
• Are validation failures explicit?
• Are long-running tasks behind a job/status boundary?

Database

• Are migrations included?
• Are geometry columns documented?
• Are timestamps and provenance fields included?
• Is source metadata preserved?

Geospatial Correctness

• Is CRS captured?
• Are metric calculations done in a projected CRS?
• Are geometries validated?
• Are bounds and area units explicit?

AI Pipeline Correctness

• Is model mode clear: real, stub or fixture?
• Is confidence not mislabeled as accuracy?
• Are generated detections georeferenced or explicitly not georeferenced?
• Are model parameters stored with the run?

Frontend

• Are loading, empty, error and success states implemented?
• Does the UI use API data instead of hardcoded business data?
• Are map layers inspectable?
• Can users understand what happened after running an analysis?

Testing

• Were relevant tests added or updated?
• Do smoke scripts still pass?
• Are fixtures deterministic?

Documentation

• Was CHANGELOG.md updated?
• Was docs/BUILD_STATUS.md updated?
• Were affected specs updated?
• Are known limitations explicit?