48 lines
1.5 KiB
Markdown
48 lines
1.5 KiB
Markdown
# Generated Scene Invocation Alias Generation Hardening Plan
|
|
|
|
> Date: 2026-04-20
|
|
> Status: Draft
|
|
> Parent route:
|
|
> - `alias_generation_hardening`
|
|
> Parent ledger:
|
|
> - `tests/fixtures/generated_scene/generated_scene_source_first_runtime_semantics_ledger_2026-04-20.json`
|
|
|
|
## Plan Intent
|
|
|
|
Implement the first reusable slice for natural-language alias generation.
|
|
|
|
## Fixed Input Bucket
|
|
|
|
Use the bounded bucket:
|
|
|
|
1. scenes with source-side alias evidence
|
|
2. scenes whose current generated deterministic manifests still expose only narrow keyword coverage
|
|
3. high-risk browser-script report scenes where operator wording is likely to diverge from canonical scene names
|
|
|
|
This first slice should prefer the densest high-risk alias bucket rather than the full 84-scene route at once.
|
|
|
|
## Allowed Files
|
|
|
|
1. `src/generated_scene/analyzer.rs`
|
|
2. `src/generated_scene/generator.rs`
|
|
3. `src/generated_scene/ir.rs`
|
|
4. route-local generator tests
|
|
|
|
## Forbidden Files
|
|
|
|
1. no runtime scoring changes in sgClaw dispatch
|
|
2. no service-console changes
|
|
3. no direct edits to final materialized `scene.toml`
|
|
4. no board assets
|
|
|
|
## Expected Coverage Delta
|
|
|
|
1. generated `include_keywords` become less brittle for the bucketed scenes
|
|
2. deterministic invocation becomes less dependent on exact canonical wording
|
|
|
|
## Stop Statement
|
|
|
|
Stop after the first reusable alias-generation slice is implemented and route-local follow-up assets are published.
|
|
|
|
Do not attempt one-shot full alias closure for every scene inside this route plan.
|