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
1.1 KiB
1.1 KiB
Codex Autonomous Runbook M4
Use this runbook when starting an autonomous implementation session.
Before Coding
- Read
README.md. - Read
AGENTS.md. - Read
docs/DEVELOPMENT_RULES.md. - Read
docs/M4_AUTONOMOUS_BUILD_READINESS.md. - Read
docs/SPRINT_BOARD_M4.md. - Read module contract for the sprint being implemented.
Implementation Rules
- Build in the sprint order unless explicitly instructed otherwise.
- Do not skip backend tests for frontend work.
- Do not add a new dependency without updating dependency documentation.
- Do not invent new architecture where a contract already exists.
- Preserve fixture determinism.
- Update TODO and changelog after each pass.
End-of-Pass Report Format
Each Codex pass must end with:
## Completed
- ...
## Tests Run
- ...
## Changed Files
- ...
## Remaining TODO
- ...
## Risks / Blockers
- ...
Stop Conditions
Stop and ask for human direction only if:
- A required external credential is missing.
- A core architecture decision conflicts across documents.
- A dependency cannot be installed or replaced safely.
- Data license terms are unclear for a live connector.