docs(roadmap): order next household work by return - #961
Conversation
Keep the in-flight P0 loop in NOW. Put charge modes, house reserve, freeze, fuse tree and plan quality in NEXT in that order. Leave tariff, heat, OCPP and grid limits behind their existing gates.
Dashboard render budget and ledger write batching stay in LATER until the Raspberry Pi traces and parity tests exist.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d2ced19cc8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Entry gate: NOW is complete. These tracks run in the listed order. A later | ||
| track may start only when the earlier track has exit evidence, or when it | ||
| does not share control or UI state with an unfinished predecessor. |
There was a problem hiding this comment.
This newly added section explicitly orders six implementation tracks, defines sequencing dependencies, and supplies task-level exit criteria, making it the kind of planning document/task breakdown that repository guidance requires keeping out of tracked files. Move these implementation details to the PR description or issues rather than expanding docs/roadmap.md with them.
AGENTS.md reference: AGENTS.md:L93-L96
Useful? React with 👍 / 👎.
1 participant
Summary
This supersedes draft #884.
Test plan
make verifyvia pre-commit