1.8 KiB
Residual Runtime Roadmap Prioritization Report
Date: 2026-04-19 Plan:
docs/superpowers/plans/2026-04-19-residual-runtime-roadmap-prioritization-plan.mdStatus: Completed
Scope
This is a decision-only step after official board reconciliation. It compares the three residual roadmap inputs and selects exactly one next roadmap.
This plan did not modify analyzer/generator logic and did not update the official execution board.
Inputs
tests/fixtures/generated_scene/scene_execution_board_2026-04-18.jsontests/fixtures/generated_scene/official_board_reconciliation_2026-04-19.json
Candidate Roadmaps
| Candidate | Residual count | Score | Decision |
|---|---|---|---|
local-doc runtime roadmap |
5 | 51 | selected |
bootstrap target normalization roadmap |
1 | 11 | deferred |
host-bridge runtime roadmap |
1 | 8 | deferred |
Selected Roadmap
local-doc runtime roadmap is selected because it covers the largest residual bucket: five local_doc_pipeline scenes.
Selected next roadmap files:
docs/superpowers/specs/2026-04-19-local-doc-runtime-roadmap-design.mddocs/superpowers/plans/2026-04-19-local-doc-runtime-roadmap-plan.md
Deferred Roadmaps
host-bridge runtime roadmap is deferred because it currently covers one residual and carries higher risk of affecting existing host-bridge auto-pass paths.
bootstrap target normalization roadmap is deferred because it currently covers one residual and should remain isolated until the higher-impact local-doc bucket is handled.
Output Asset
tests/fixtures/generated_scene/residual_runtime_roadmap_prioritization_2026-04-19.json
Conclusion
The next bounded roadmap is local-doc runtime. Do not start host-bridge runtime or bootstrap normalization until this selected roadmap is closed or explicitly superseded.