claw/docs/superpowers/specs/2026-04-19-scene-skill-102-full-coverage-child-plan-sequence-design.md

Scene Skill 102 Full Coverage Child Plan Sequence Design

Date: 2026-04-19 Status: Draft Parent Framework Design: docs/superpowers/specs/2026-04-19-scene-skill-102-full-coverage-framework-design.md Parent Framework Plan: docs/superpowers/plans/2026-04-19-scene-skill-102-full-coverage-framework-plan.md

Intent

Turn the parent 102 full-coverage framework into a fixed downstream child-plan sequence.

This design does not implement any bucket directly. It defines:

1. the ordered bounded plans that must be created and executed next
2. which bucket each bounded plan owns
3. which layer and route each bounded plan belongs to
4. which plans are implementation plans and which plans are policy/reconciliation plans
5. what later plans are not allowed to skip

The main purpose is to stop later work from drifting into ad hoc micro-plans.

Current Parent Baseline

The parent framework freezes the current integrated state as:

Status	Count
auto-pass	48
fail-closed-known	47
adjudicated-valid-host-bridge	4
raw source-unreadable	3
Total	102

The timeout hygiene layer additionally shows:

Hygiene interpretation	Count
timeout-as-pass-candidate	2
timeout-as-fail-closed-candidate	1
timeout-still-unreadable	0

Child Sequence Principles

Every child plan in this sequence must follow the parent framework requirements:

1. one child plan belongs to exactly one route
2. one child plan belongs to exactly one layer
3. one child plan owns one fixed input bucket
4. one child implementation slice should target one repeated recoverable pattern
5. child plans must not silently absorb neighboring buckets
6. a child plan must stop after its declared delta is measured

Ordered Child Routes

The child plan sequence begins at Route 2, because Route 1 has already been completed at the parent-framework level.

Route 2

Layer C + Layer D

Target:

G3 / paginated_enrichment structured fail-closed bucket

Current bucket size:

34

Fixed bounded child-plan order inside Route 2:

1. G3 enrichment-request closure
2. G3 export-plan closure
3. G3 residual contract closure

The residual plan only begins after the first two plans have either:

1. produced measurable delta, or
2. been explicitly closed as deferred

Route 3

Layer C + Layer D

Target:

G2 / multi_mode_request structured fail-closed bucket

Current bucket size:

4

Fixed bounded child-plan order inside Route 3:

1. G2 remaining fail-closed closure

No Route 3 follow-up plan may begin until Route 2 has been completed or explicitly deferred.

Route 4

Layer C + Layer D

Target:

G1-E / single_request_enrichment structured fail-closed bucket

Current bucket size:

2

Fixed bounded child-plan order inside Route 4:

1. G1-E remaining fail-closed closure

No Route 4 follow-up plan may begin until Route 3 has been completed or explicitly deferred.

Route 5

Layer C + Layer D

Target:

Boundary-family fail-closed buckets:

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

Fixed bounded child-plan order inside Route 5:

1. boundary fail-closed decision

This route is decision-first by design. It must not start implementation correction before mainline routes have been reduced or deferred.

Route 6

Layer E

Target:

Promotion thresholds and board reconciliation policy.

Fixed bounded child-plan order inside Route 6:

1. promotion and board reconciliation policy

This route must start only after Routes 2 through 5 have stable post-delta reporting.

Required Child Plan Fields

Every bounded child plan in this sequence must declare:

1. parent framework reference
2. parent route name
3. parent layer name
4. fixed input bucket
5. allowed file set
6. forbidden file set
7. expected coverage delta
8. stop statement

If one of these is missing, the plan is not valid under this sequence.

Implementation vs Policy Split

The child sequence intentionally separates implementation plans from policy plans.

Implementation-oriented plans:

1. G3 enrichment-request closure
2. G3 export-plan closure
3. G3 residual contract closure
4. G2 remaining fail-closed closure
5. G1-E remaining fail-closed closure

Decision or policy-oriented plans:

1. boundary fail-closed decision
2. promotion and board reconciliation policy

Expected Coverage Movement

This sequence does not promise auto-pass growth on every child plan.

Expected valid deltas include:

1. fail-closed-known reduction
2. stronger structured fail-closed naming
3. bucket shrinkage within one archetype
4. policy-recognized status strengthening

Invalid deltas include:

1. scene-name hardcoding
2. silent gate relaxation
3. route changes that are not measured against current canonical and real-sample anchors

Stop Rules

This child-plan sequence forbids:

1. opening a child implementation plan outside Routes 2 through 6
2. creating route-local semantics micro-plans that do not reduce a measured bucket
3. mixing timeout hygiene with contract recovery in the same bounded implementation plan
4. updating scene_execution_board_2026-04-18.json inside any Route 2 through Route 5 implementation plan
5. starting Route 6 before post-Route-5 status is stable enough for policy design

Completion Condition

This child-plan sequence remains active until all of these are true:

1. the Route 2 child plans are completed or deferred
2. the Route 3 child plan is completed or deferred
3. the Route 4 child plan is completed or deferred
4. the Route 5 decision plan is completed
5. the Route 6 policy plan is completed

At that point, the parent framework may either:

1. remain active with no open child routes, or
2. be revised into a new parent framework revision