claw/docs/superpowers/plans/2026-04-19-boundary-fail-closed-decision-plan.md

Boundary Fail-Closed Decision Plan

Date: 2026-04-19 Status: Draft Parent Framework Plan: docs/superpowers/plans/2026-04-19-scene-skill-102-full-coverage-framework-plan.md Parent Route: Route 5: boundary-family fail-closed Parent Layer: Layer C + Layer D Upstream Design: docs/superpowers/specs/2026-04-19-boundary-fail-closed-decision-design.md

Plan Intent

Publish a decision for the remaining boundary-family fail-closed buckets after mainline routes are complete or deferred.

Fixed Input Bucket

1. local_doc_pipeline = 5
2. host_bridge_workflow = 1
3. page_state_eval/bootstrap_target = 1

Allowed Files

1. boundary decision JSON assets
2. boundary decision report assets
3. optional next bounded boundary plan docs

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. freeze the Route 5 bucket state
2. inspect each boundary subgroup
3. decide defer/hold/open-slice
4. publish Route 5 decision report

Expected Coverage Delta

Decision-only delta:

1. unresolved boundary ambiguity should go to zero

Completion Criteria

1. every Route 5 subgroup has a named decision
2. any follow-up bounded plan is explicit and optional

Stop Statement

Stop after the Route 5 decision report is published.

Do not begin boundary implementation under this plan.