46 lines
1.4 KiB
Markdown
46 lines
1.4 KiB
Markdown
# M6 Handoff Summary — Codex Autonomy Pack
|
|
|
|
## What M6 adds
|
|
|
|
M6 adds the documents and prompts needed to let Codex execute the first build passes with minimal manual steering.
|
|
|
|
## New capabilities in the repo preparation
|
|
|
|
- Codex autonomy boundaries.
|
|
- Quality gates per layer.
|
|
- Self-review checklist.
|
|
- Failure recovery playbook.
|
|
- Gap registry.
|
|
- Next-day execution checklist.
|
|
- Final handoff template.
|
|
- Sequential Codex prompt pack.
|
|
- GitHub issue and PR templates.
|
|
- CI smoke workflow.
|
|
- Codex preflight and pass-end scripts.
|
|
|
|
## How to use tomorrow
|
|
|
|
1. Extract the full M6 zip.
|
|
2. Start a git repo if not already initialized.
|
|
3. Run `bash scripts/codex_preflight.sh`.
|
|
4. Give Codex `prompts/codex/PASS_00_REPO_AUDIT.md`.
|
|
5. Only after the audit, continue with `PASS_01_BACKEND_FOUNDATION.md`.
|
|
6. After every pass, require the handoff format in `docs/M6_FINAL_HANDOFF_TEMPLATE.md`.
|
|
7. Commit only after smoke checks pass.
|
|
|
|
## Recommended first objective
|
|
|
|
Do not try to finish GeoIntel tomorrow. The ideal first Codex day should aim for:
|
|
|
|
- backend foundation;
|
|
- database foundation;
|
|
- project/area API;
|
|
- dataset upload foundation;
|
|
- first frontend shell if backend is stable.
|
|
|
|
That already creates a serious base without architecture drift.
|
|
|
|
## Current maturity
|
|
|
|
Preparation maturity after M6: high for autonomous foundation building, medium for AI-heavy implementation, intentionally deferred for live external data providers and full training/LiDAR modules.
|