# Residual Runtime Roadmap Prioritization Design

> Date: 2026-04-19
> Parent Framework: `2026-04-19-scene-skill-102-full-coverage-framework-design.md`
> Parent Layer: `Layer E`
> Status: Active

## Intent

Choose the next bounded roadmap after official board reconciliation.

The official board now has `95` framework auto-pass scenes and `7` explained structured fail-closed residuals. This design compares the three residual roadmap inputs and selects exactly one next roadmap.

## 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`

## Candidate Roadmaps

1. `local-doc runtime roadmap`
2. `host-bridge runtime roadmap`
3. `bootstrap target normalization roadmap`

## Decision Criteria

1. `impact`: number of residual scenes addressed.
2. `scope clarity`: whether the required implementation boundary is clear.
3. `prerequisite weight`: whether the roadmap requires large external runtime work.
4. `risk`: likelihood of disturbing the already reconciled `95` framework auto-pass scenes.

## Boundary

This design is decision-only. It must not:

1. modify `src/generated_scene/analyzer.rs`;
2. modify `src/generated_scene/generator.rs`;
3. modify `tests/fixtures/generated_scene/scene_execution_board_2026-04-18.json`;
4. start runtime implementation;
5. add a new family.

## Acceptance Criteria

1. All `7` residual records are accounted for.
2. Exactly one next roadmap is selected.
3. Deferred roadmaps have explicit reasons.
4. A next bounded design/plan is created for the selected roadmap only.