GeoIntel release gates / Compile, test, contracts and builds (push) Successful in 1m49s
GeoIntel release gates / Python and npm vulnerability policy (push) Successful in 21s
GeoIntel release gates / Production AI image, SBOM and container scan (push) Successful in 5m39s
GeoIntel release gates / Deploy exact gated revision to Unraid (push) Failing after 58m43s
1.4 KiB
1.4 KiB
M4 Autonomous Build Readiness
This milestone converts GeoIntel from an implementation-ready blueprint into an autonomous-build package for Codex.
Goal
Codex must be able to start from the repository root, read the contracts, build the foundation, and keep moving through backend, frontend, GIS processing, AI pipeline stubs, QA/QC, tests and documentation without making new product or architecture decisions.
M4 Adds
- Sprint board with sequential implementation lanes.
- Module-level build contracts.
- Acceptance-test catalog per module.
- Frontend state and page contracts.
- Backend service IO contracts.
- Example API responses and error shapes.
- Job lifecycle contract.
- Model registry seed contract.
- Demo fixture manifest.
- Codex prompts per autonomous build pass.
- Final readiness checklist.
Golden Rule
When code conflicts with documentation, documentation wins unless an explicit ADR is added.
Build Priority
- Running local stack.
- Database models and migrations.
- API contracts.
- Dataset manager.
- Map workspace.
- Raster/vector metadata flows.
- Analysis run lifecycle.
- Detection/segmentation job shells with deterministic demo mode.
- QA/QC engine.
- Exports.
- Polish, tests and documentation.
Do Not Build Yet
- Full LiDAR workbench.
- Full training studio.
- QGIS plugin.
- Cloud deployment.
- Real production-grade model training.
- Complex user auth.