50 lines
1.6 KiB
Markdown
50 lines
1.6 KiB
Markdown
# Residual Runtime Roadmap Prioritization Plan
|
|
|
|
> Date: 2026-04-19
|
|
> Parent Framework: `2026-04-19-scene-skill-102-full-coverage-framework-plan.md`
|
|
> Parent Layer: `Layer E`
|
|
> Status: Active
|
|
|
|
## Plan Intent
|
|
|
|
Select the next roadmap from the three residual inputs after official board reconciliation.
|
|
|
|
## Fixed Inputs
|
|
|
|
1. `tests/fixtures/generated_scene/scene_execution_board_2026-04-18.json`
|
|
2. `tests/fixtures/generated_scene/official_board_reconciliation_2026-04-19.json`
|
|
|
|
## Allowed Files
|
|
|
|
1. `tests/fixtures/generated_scene/residual_runtime_roadmap_prioritization_2026-04-19.json`
|
|
2. `docs/superpowers/reports/2026-04-19-residual-runtime-roadmap-prioritization-report.md`
|
|
3. selected next roadmap design
|
|
4. selected next roadmap plan
|
|
|
|
## Forbidden Files
|
|
|
|
1. `src/generated_scene/analyzer.rs`
|
|
2. `src/generated_scene/generator.rs`
|
|
3. `tests/fixtures/generated_scene/scene_execution_board_2026-04-18.json`
|
|
|
|
## Tasks
|
|
|
|
1. Load official board residual records.
|
|
2. Group residuals by next action.
|
|
3. Score local-doc runtime, host-bridge runtime, and bootstrap target normalization.
|
|
4. Select exactly one next roadmap.
|
|
5. Publish prioritization JSON.
|
|
6. Publish prioritization report.
|
|
7. Create design/plan for the selected roadmap only.
|
|
|
|
## Completion Criteria
|
|
|
|
1. All `7` residual records are represented.
|
|
2. Exactly one selected roadmap exists.
|
|
3. Non-selected roadmaps are deferred with reasons.
|
|
4. No implementation file is modified.
|
|
|
|
## Stop Statement
|
|
|
|
Stop after prioritization assets and the selected next roadmap design/plan are published. Do not execute the selected roadmap under this plan.
|