1.8 KiB
1.8 KiB
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
- Hardened generator implementation after these completed routes:
resolver_request_mapping_hardeningruntime_url_classification_hardeningembedded_dictionary_extraction_hardeningparameter_default_semantics_recovery_hardeningalias_generation_hardening
- Current source mapping from
generated_scene_source_evidence_cross_scan_2026-04-20.json. - 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
- Refreshed 102-skill materialization directory.
- Refreshed materialization manifest.
- Refreshed failures asset.
- Refreshed human-readable scene index.
- Rematerialization execution report.
Guardrails
- Do not manually edit generated skill files after generation.
- Do not update official execution board.
- Do not run production, browser, or intranet execution.
- Do not run validation refresh in this plan.
- 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.