Files
geointel/docs/18-ultra-prep/CRITICAL_PATH_TO_V1.md
Jens faeb58ef6d
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
Initial public release
2026-08-31 21:56:53 +02:00

1.2 KiB

Critical Path to V1

This is the shortest reliable path to a portfolio-ready V1.

V1 Critical Path

  1. Repo foundation and dev environment.
  2. Database and PostGIS schema.
  3. Project and area CRUD.
  4. Dataset upload and metadata extraction.
  5. Vector import and display.
  6. Raster import and metadata display.
  7. Map workbench with layer management.
  8. OSM/GRB reference ingest interface or stubbed real-data connector with honest unavailable state.
  9. Detection pipeline architecture with YOLO adapter.
  10. Detection result storage as geospatial features.
  11. QA/QC comparison engine against reference polygons.
  12. GeoJSON export.
  13. Demo scenario page.
  14. Smoke tests and documentation.

V1 Can Be Portfolio-Ready Without

  • full Sentinel automation;
  • actual production GRB WFS credentials or final endpoint if unavailable;
  • LiDAR processing;
  • model training;
  • multi-user auth;
  • perfect visual polish.

V1 Cannot Be Portfolio-Ready Without

  • a working map-driven workflow;
  • actual geospatial data models;
  • real CRS/geometry handling;
  • honest dataset status handling;
  • at least one end-to-end detection/QA workflow, even if it uses a small local demo fixture/model adapter first;
  • clear export output.