133 lines
3.4 KiB
Markdown
133 lines
3.4 KiB
Markdown
# Scene Skill 102 Full Coverage Child Plan Sequence Plan
|
|
|
|
> Date: 2026-04-19
|
|
> Status: Draft
|
|
> Parent Framework Plan: `docs/superpowers/plans/2026-04-19-scene-skill-102-full-coverage-framework-plan.md`
|
|
> Upstream Design: `docs/superpowers/specs/2026-04-19-scene-skill-102-full-coverage-child-plan-sequence-design.md`
|
|
|
|
## Plan Intent
|
|
|
|
Create the full bounded child-plan sequence for `Route 2` through `Route 6` under the `102` full-coverage parent framework.
|
|
|
|
This plan only creates the downstream plan tree. It does not implement any bucket directly.
|
|
|
|
## Scope Guardrails
|
|
|
|
1. do not modify `analyzer.rs`
|
|
2. do not modify `generator.rs`
|
|
3. do not modify `ir.rs`
|
|
4. do not update `scene_execution_board_2026-04-18.json`
|
|
5. do not rerun `102` sweep
|
|
6. do not open new families
|
|
7. do not collapse multiple buckets into one child implementation plan
|
|
|
|
## Workstreams
|
|
|
|
1. `WS1` Route 2 child plans
|
|
2. `WS2` Route 3 child plans
|
|
3. `WS3` Route 4 child plans
|
|
4. `WS4` Route 5 child plans
|
|
5. `WS5` Route 6 child plans
|
|
|
|
## Phase 0: Freeze Sequence Inputs
|
|
|
|
### Objective
|
|
|
|
Freeze the parent baseline and route order before generating child plans.
|
|
|
|
### Tasks
|
|
|
|
1. freeze parent framework references
|
|
2. freeze current bucket sizes
|
|
3. freeze route order from Route 2 through Route 6
|
|
|
|
### Deliverables
|
|
|
|
1. child-plan sequence design
|
|
2. child-plan sequence plan
|
|
|
|
### Acceptance Criteria
|
|
|
|
1. all later child plans can reference the same parent baseline
|
|
2. route order is explicit and cannot drift
|
|
|
|
## Phase 1: Route 2 Child Plans
|
|
|
|
### Objective
|
|
|
|
Create the first three bounded child plans under the largest remaining mainline bucket.
|
|
|
|
### Tasks
|
|
|
|
1. create `G3 enrichment-request closure` design and plan
|
|
2. create `G3 export-plan closure` design and plan
|
|
3. create `G3 residual contract closure` design and plan
|
|
|
|
### Deliverables
|
|
|
|
1. Route 2 child designs
|
|
2. Route 2 child plans
|
|
|
|
### Acceptance Criteria
|
|
|
|
1. each Route 2 child plan owns a narrower fixed bucket
|
|
2. Route 2 plans declare allowed and forbidden file sets
|
|
3. Route 2 plans declare expected deltas separately
|
|
|
|
## Phase 2: Route 3 and Route 4 Child Plans
|
|
|
|
### Objective
|
|
|
|
Create the bounded plans for the smaller remaining mainline buckets.
|
|
|
|
### Tasks
|
|
|
|
1. create `G2 remaining fail-closed closure` design and plan
|
|
2. create `G1-E remaining fail-closed closure` design and plan
|
|
|
|
### Deliverables
|
|
|
|
1. Route 3 child design and plan
|
|
2. Route 4 child design and plan
|
|
|
|
### Acceptance Criteria
|
|
|
|
1. Route 3 and Route 4 remain downstream of Route 2
|
|
2. neither plan absorbs Route 2 issues
|
|
|
|
## Phase 3: Route 5 and Route 6 Child Plans
|
|
|
|
### Objective
|
|
|
|
Create the policy and decision plans that follow mainline contract-recovery work.
|
|
|
|
### Tasks
|
|
|
|
1. create `boundary fail-closed decision` design and plan
|
|
2. create `promotion and board reconciliation policy` design and plan
|
|
|
|
### Deliverables
|
|
|
|
1. Route 5 child design and plan
|
|
2. Route 6 child design and plan
|
|
|
|
### Acceptance Criteria
|
|
|
|
1. Route 5 is decision-first, not implementation-first
|
|
2. Route 6 is policy-only
|
|
|
|
## Completion Criteria
|
|
|
|
This plan is complete when:
|
|
|
|
1. Route 2 through Route 6 all have bounded child designs and plans
|
|
2. every child plan declares parent route, parent layer, input bucket, allowed files, forbidden files, expected delta, and stop statement
|
|
3. later work can proceed without inventing new unanchored micro-plans
|
|
|
|
## Stop Statement
|
|
|
|
Stop after the bounded child-plan sequence for Route 2 through Route 6 has been created.
|
|
|
|
Do not implement any route from this sequence under this plan.
|
|
|