Files
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.5 KiB

BUILD ORDER GRAPH — M14 Launch

Codex must follow this dependency graph for implementation.

Graph

Repository readiness
  -> Environment/config
  -> Backend app foundation
  -> Database/PostGIS foundation
  -> Domain models/schemas
  -> Migrations
  -> Project API
  -> Area API
  -> Dataset API
  -> Storage service
  -> Metadata extraction
  -> Frontend shell
  -> Frontend API client
  -> Map workbench shell
  -> Dataset UI
  -> Fixture layer display
  -> Export baseline
  -> Tests and readiness

Blocked until foundation is stable

The following are blocked until the above graph is green:

  • Detection Lab.
  • Segmentation Lab.
  • QA/QC engine beyond fixture/schema validation.
  • Remote Sensing Lab.
  • GRB live adapter.
  • OSM live adapter.
  • LiDAR Workbench.
  • Training Studio.

Rule

If a later module requires missing foundation work, Codex must complete the foundation work first instead of building around it.

Preferred first implementation passes

Pass 1 — Backend and config

  • Create app structure.
  • Add config/settings.
  • Add health endpoint.
  • Add response envelope and error handling.

Pass 2 — Database and domain

  • Add database connection.
  • Add migrations.
  • Add core models.
  • Enable PostGIS.

Pass 3 — Project/Area/Dataset API

  • Implement CRUD.
  • Validate geometry.
  • Extract metadata.

Pass 4 — Frontend shell and map

  • React app.
  • Layout.
  • MapLibre.
  • API client.

Pass 5 — Fixture-driven integration

  • Load demo area/reference layer.
  • Display layers.
  • Run smoke tests.