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
1023 B
1023 B
M9 Gap-to-Task Conversion Rules
When Codex finds a gap, it must convert it into an actionable task instead of leaving vague notes.
Task Format
### TASK-ID: Short title
Type: backend | frontend | docs | test | devops | data | ai
Priority: P0 | P1 | P2 | P3
Status: open | in_progress | done | blocked
Owner: Codex
Context:
...
Required changes:
- ...
Acceptance criteria:
- [ ] ...
Validation commands:
- ...
Blocked by:
- none or exact blocker
Priority Rules
P0
Blocks app startup, database, API envelope, project/area/dataset foundation.
P1
Blocks V1 core workflow but not app startup.
P2
Improves quality, tests, UX, docs.
P3
Nice-to-have or future extension.
Gap Handling
- If gap is architecture-related: update docs before code.
- If gap is implementation-related: create ticket and implement if in current pass.
- If gap is dependency-related: document in dependency plan and add fallback interface.
- If gap is scope expansion: move to proposed improvements.