claw/docs/superpowers/specs/2026-04-18-scene-skill-real-sample-validation-roadmap-design.md

sgClaw Scene Skill Real Sample Validation Roadmap Design

Status: Draft Date: 2026-04-18 Author: Codex Upstream Plan: 2026-04-18-scene-skill-post-roadmap-execution-plan.md

Problem Statement

The completed 60-to-90 roadmap established repo-local promoted baselines for G2, G1-E, and G3, but the next quality barrier is no longer family promotion.

It is now real-sample validation:

1. G2 already has a real mismatch anchor.
2. G1-E already has a real pass anchor.
3. G3 is now selected into the real-sample queue but still lacks an executed real-run record.
4. G6/G7/G8 remain boundary families until runtime gaps are explicitly closed.

The next roadmap must therefore be validation-first instead of asset-first.

Goal

Define the next bounded roadmap around three immediate goals:

1. convert current selected real samples into formal pass/mismatch/fail-closed records
2. use validation pressure to decide whether boundary families or deferred families should enter implementation
3. keep execution-board work subordinate to validation rather than growing into a new asset program

Scope

This roadmap includes:

1. real-sample execution for currently selected G2/G1-E/G3 anchors
2. validation-result-driven scope decisions for G6/G7/G8
3. entry decisions for G4/G5 only after explicit criteria are met

This roadmap does not include:

1. reopening completed repo-local compiler work for G1/G2/G3
2. unlimited fixture expansion
3. full 102-scene runtime rollout
4. direct implementation of all runtime gaps in one round

Design Principles

1. Real-sample validation is the primary execution axis.
2. Execution-board changes must only exist to support validation records.
3. Boundary-family expansion must be justified by validation pressure, not drift.
4. Deferred-family entry must be decided explicitly before implementation begins.

Workstream Model

1. WS1 Mainline Real Sample Execution
2. WS2 Validation Result Triage And Scope Decisions
3. WS3 Boundary Runtime Enablement Decision
4. WS4 Deferred Family Entry Decision

Completion Criteria

This roadmap is complete when:

1. G2, G1-E, and G3 each have executed real-sample records
2. the next implementation scope is selected from validation evidence
3. boundary-family and deferred-family entry decisions are documented before new implementation begins