# Scene Skill 102 Deterministic Invocation Readiness Plan

> Date: 2026-04-20
> Design: `2026-04-20-scene-skill-102-deterministic-invocation-readiness-design.md`

## Plan Intent

Make the materialized scene skills ready for sgClaw deterministic invocation using natural-language instructions ending with `。。。`.

This plan does not prove production execution. It only prepares and verifies registry/dispatch readiness.

## Fixed Inputs

1. `examples/scene_skill_102_final_materialization_2026-04-19`
2. `examples/scene_skill_102_final_materialization_2026-04-19/scene_skill_102_index.json`
3. `tests/fixtures/generated_scene/scene_execution_board_2026-04-18.json`

## Allowed Files

1. `examples/scene_skill_102_final_materialization_2026-04-19/skills/*/scene.toml`
2. `tests/fixtures/generated_scene/scene_skill_102_deterministic_invocation_readiness_2026-04-20.json`
3. `tests/fixtures/generated_scene/scene_skill_102_deterministic_invocation_samples_2026-04-20.json`
4. `docs/superpowers/reports/2026-04-20-scene-skill-102-deterministic-invocation-readiness-report.md`

## Forbidden Files

1. `src/compat/scene_platform/dispatch.rs`
2. `src/compat/scene_platform/resolvers.rs`
3. `src/generated_scene/analyzer.rs`
4. `src/generated_scene/generator.rs`
5. generated `scripts/*`
6. `tests/fixtures/generated_scene/scene_execution_board_2026-04-18.json`

## Phase 0: Freeze Invocation Readiness Boundary

### Tasks

1. Confirm final materialization root exists.
2. Confirm human-readable index exists.
3. Confirm this plan excludes browser execution and runtime changes.

### Acceptance Criteria

1. Scope is deterministic invocation readiness only.
2. `sweep-012-scene` remains outside complete-package normalization.

## Phase 1: Normalize Deterministic Manifest Metadata

### Tasks

1. For each complete package, set `[deterministic].suffix = "。。。"`.
2. Preserve scene id, skill, tool, bootstrap, params, artifact, and postprocess sections.
3. Generate include keywords from:
   - full scene name;
   - meaningful scene-name tokens;
   - archetype/family hints when available.
4. Keep exclude keywords.

### Acceptance Criteria

1. All complete packages use suffix `。。。`.
2. Every complete package has non-empty include keywords.
3. Skill directories and scripts are unchanged.

## Phase 2: Build Invocation Samples

### Tasks

For each complete package, generate at least:

1. full-name sample: `<sceneName>。。。`
2. keyword sample: `<bestKeyword>。。。`
3. parameterized sample when params exist.

### Acceptance Criteria

1. Sample asset contains all complete packages.
2. Failed package is listed as excluded.

## Phase 3: Dispatch Dry-Run

### Tasks

1. Run registry-backed dispatch checks without browser execution.
2. Verify full-name sample selects the expected scene.
3. Record ambiguous or unsupported dispatch results.
4. Record required-param prompts separately from dispatch misses.

### Acceptance Criteria

1. Every complete package has a dispatch result.
2. Results distinguish selected, prompt, ambiguous, and no-match.

## Phase 4: Publish Readiness Report

### Tasks

1. Publish readiness JSON.
2. Publish invocation sample JSON.
3. Publish superpowers report.

### Acceptance Criteria

1. Report states deterministic-ready count.
2. Report states gap count and gap categories.
3. Report states whether runtime dispatch changes are needed.

## Stop Statement

Stop after readiness assets and report are published. Do not start browser execution, static validation, production validation, or runtime dispatch implementation under this plan.