Initial public release
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
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
This commit is contained in:
@@ -0,0 +1,31 @@
|
||||
# Next Pass After Day 1
|
||||
|
||||
If Day 1 succeeds, the next priority is not broad feature expansion. The next priority is the first true GeoAI/GIS capability.
|
||||
|
||||
## Preferred Day 2 sequence
|
||||
|
||||
1. GRB/reference adapter scaffold.
|
||||
2. Raster tiling interface.
|
||||
3. Detection model registry scaffold.
|
||||
4. Deterministic detection fixture adapter.
|
||||
5. Detection output as GeoJSON.
|
||||
6. QA/QC overlap metrics against reference fixture.
|
||||
7. Map overlay display.
|
||||
|
||||
## Why this sequence
|
||||
|
||||
It creates the first portfolio-relevant technical loop:
|
||||
|
||||
```text
|
||||
Raster/Dataset -> Detection -> Geospatial output -> Reference comparison -> QA metrics -> Export
|
||||
```
|
||||
|
||||
## Do not jump directly to
|
||||
|
||||
- full SAM integration;
|
||||
- real Sentinel downloads;
|
||||
- LiDAR processing;
|
||||
- training studio;
|
||||
- complex report generation.
|
||||
|
||||
Those need the Day 1 foundation and Day 2 detection/QA loop first.
|
||||
Reference in New Issue
Block a user