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

This commit is contained in:
Jens
2026-08-31 21:56:53 +02:00
commit faeb58ef6d
1386 changed files with 263203 additions and 0 deletions
@@ -0,0 +1,73 @@
# Day 1 Optimized Master Prompt for Codex
You are working on GeoIntel Kempen, a GeoAI Workbench for the Belgian Kempen.
Your goal is not to redesign the product. Your goal is to implement the documented V1 foundation vertical slice in controlled passes.
## Mandatory reading order
1. `CODEX_START.md`
2. `docs/00-start/START_HERE.md`
3. `docs/30-codex-optimization/CODEX_OPTIMIZATION_OVERVIEW.md`
4. `docs/30-codex-optimization/CODEX_RUN_CHECKLIST.md`
5. `docs/30-codex-optimization/PROMPT_DISCIPLINE.md`
6. `docs/governance/GEOINTEL_CONSTITUTION.md`
7. `docs/governance/ARCHITECTURE_INVARIANTS.md`
8. `docs/governance/FORBIDDEN_DECISIONS.md`
9. `docs/20-run-readiness/PASS_SEQUENCE_FINAL.md`
10. Active pass prompt only.
11. Relevant skill under `skills/`.
## First objective
Build the foundation vertical slice in pass order:
Project → Area → Dataset metadata → Reference polygons → Predicted detections → QA/QC → GeoJSON export → Minimal UI.
## Strict boundaries
Do not implement:
- heavy AI inference before the service contracts exist;
- LiDAR processing;
- model training;
- MLOps;
- QGIS plugin;
- advanced report generation;
- unrelated dashboards;
- new frameworks not approved by ADR.
## Execution rules
- Work one pass at a time.
- Keep changes small and coherent.
- Use the relevant skill.
- Respect API/database contracts.
- Do not create permanent mock-only flows.
- Use fixtures only where documented.
- Run `make readiness` before and after major changes when possible.
- Update `docs/CODEX_EXECUTION_LOG.md` and `CHANGELOG.md`.
## Required final report
End every pass with:
```md
## Completed
## Changed files
## Commands run
## Test results
## Self-review scorecard
## Known limitations
## Contract deviations
## Next recommended pass
```
If a blocker appears, stop and report it instead of guessing.
@@ -0,0 +1,40 @@
# Parallel Agent Coordination Prompt
Use this when running multiple Codex agents in separate worktrees.
You are one agent working on GeoIntel Kempen.
## Your assigned track
Set one:
- Backend foundation
- Frontend shell
- Fixtures/tests
- Documentation/control layer
- QA/QC engine
## Mandatory rules
- Read `docs/30-codex-optimization/PARALLEL_AGENT_STRATEGY.md`.
- Stay inside the allowed paths for your track.
- Do not change contracts owned by another track unless explicitly assigned.
- Report merge risks.
- Avoid broad formatting changes.
- Keep commits/diffs isolated.
## Required final report
```md
## Track
## Files changed
## Contracts touched
## Tests run
## Merge risks
## Needed from other tracks
```
@@ -0,0 +1,48 @@
# Pass Completion Report Prompt
Use this at the end of every Codex implementation pass.
Produce a concise but complete report with:
## Completed
List what was actually implemented.
## Changed files
List each changed file and why it changed.
## Commands run
List commands and exact result status.
## Test results
Mention pass/fail/skipped and why.
## Self-review scorecard
Score 0-10:
- Scope control:
- Architecture consistency:
- Backend correctness:
- Frontend correctness:
- GIS correctness:
- AI/ML correctness:
- QA/QC correctness:
- Tests:
- Documentation:
- Release readiness:
## Known limitations
List real limitations. Do not hide TODOs.
## Contract deviations
State explicitly whether any API, DB, storage, CRS, state machine or governance contract changed.
## Next recommended pass
Name the next pass and why.