Files
claw/docs/superpowers/specs/2026-04-21-generated-scene-runtime-semantics-rematerialization-execution-design.md

56 lines
1.8 KiB
Markdown

# Generated Scene Runtime Semantics Rematerialization Execution Design
Date: 2026-04-21
Parent dependency plan:
- `docs/superpowers/plans/2026-04-20-generated-scene-runtime-semantics-rematerialization-refresh-plan.md`
## Purpose
Execute the rematerialization refresh required after the source-first runtime semantics hardening routes.
This design exists because the parent dependency plan explicitly forbids executing rematerialization inside itself.
## Fixed Inputs
1. Hardened generator implementation after these completed routes:
- `resolver_request_mapping_hardening`
- `runtime_url_classification_hardening`
- `embedded_dictionary_extraction_hardening`
- `parameter_default_semantics_recovery_hardening`
- `alias_generation_hardening`
2. Current source mapping from `generated_scene_source_evidence_cross_scan_2026-04-20.json`.
3. Current final materialization directory:
- `examples/scene_skill_102_final_materialization_2026-04-19`
## Execution Target
Create a refreshed final materialization directory using the hardened generator rules.
Recommended output root:
- `examples/scene_skill_102_runtime_semantics_rematerialization_2026-04-21`
## Required Outputs
1. Refreshed 102-skill materialization directory.
2. Refreshed materialization manifest.
3. Refreshed failures asset.
4. Refreshed human-readable scene index.
5. Rematerialization execution report.
## Guardrails
1. Do not manually edit generated skill files after generation.
2. Do not update official execution board.
3. Do not run production, browser, or intranet execution.
4. Do not run validation refresh in this plan.
5. Preserve old final materialization output as an audit artifact.
## Stop Statement
Stop after refreshed materialization assets and report are published.
Do not execute validation refresh inside this plan.