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,13 @@
|
||||
# Definition of Ready
|
||||
|
||||
A task is ready for Codex implementation only when:
|
||||
|
||||
- The module is described in docs.
|
||||
- The expected input/output is known.
|
||||
- The API contract exists or the task explicitly creates it.
|
||||
- The data model is defined or the task explicitly creates it.
|
||||
- Acceptance criteria exist.
|
||||
- Error behavior is defined.
|
||||
- The task does not require hidden external credentials.
|
||||
|
||||
If these conditions are not met, Codex must update the specification before implementing code.
|
||||
Reference in New Issue
Block a user