# Generated Scene Embedded Dictionary Extraction Hardening Plan

> Date: 2026-04-20
> Status: Draft
> Parent route:
> - `embedded_dictionary_extraction_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 source-side dictionary/tree extraction.

## Fixed Input Bucket

Use the bounded bucket:

1. scenes with declared `org` parameters
2. scenes with source-side dictionary evidence (`city.js`, `dict.js`, `enum.js`, tree/options files)
3. scenes whose current generated `org-dictionary.json` is absent or starter-sized

This first slice should center on the 10 parameterized scenes that most resemble `sweep-030-scene`.

## 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 edits to already materialized dictionaries under `examples/`
2. no runtime resolver implementation outside generation output needs
3. no board assets
4. no pseudo-production handoff assets

## Expected Coverage Delta

1. generated dictionaries move beyond starter subsets for the bucketed scenes
2. dictionary recovery becomes source-driven rather than hand-seeded

## Stop Statement

Stop after the first reusable dictionary-extraction slice is implemented and route-local follow-up assets are published.

Do not attempt complete organization-tree closure for every scene inside this route plan.