# Generated Scene Source-First Runtime Semantics Ledger Report

- Date: 2026-04-20
- Plan: docs/superpowers/plans/2026-04-20-generated-scene-source-first-runtime-semantics-ledger-plan.md
- Scope: 102-scene source-first runtime semantics ledger
- Mode: analysis-only

## Summary

- Total scenes represented: 102
- High risk: 76
- Medium risk: 26
- Low risk: 0
- Scenes with generator-level gaps: 102
- Scenes with runtime-only residuals: 34

## Gap Counts

- invocation_alias_gap: 84
- dictionary_recovery_gap: 102
- parameter_default_semantics_gap: 89
- resolver_to_request_mapping_gap: 102
- runtime_url_semantics_gap: 102

## Input Asset Status

- source cross-scan JSON parsed successfully
- deterministic invocation readiness JSON parsed successfully: False
- natural-language parameter readiness JSON parsed successfully: False
- parameter dictionary normalization JSON parsed successfully: False
- For malformed auxiliary assets, this stage fell back to direct `scene.toml` / `references` / script inspection rather than stopping the ledger.

## Interpretation

- The ledger now treats the `multi_mode_request` family and scenes with unresolved period-default semantics as the highest-risk route cluster rather than flattening the entire 102-scene set into one undifferentiated bucket.
- `runtime_url_semantics_gap` and `resolver_to_request_mapping_gap` are the broadest reusable gaps in the current 102-scene set because source-side evidence is widespread while generated manifests still do not encode explicit reusable role separation or mapping metadata.
- `dictionary_recovery_gap` remains large because generated `org-dictionary.json` assets are frequently absent or starter-sized relative to source-side dictionary/tree evidence.
- `invocation_alias_gap` is more selective than the other four gaps, which means alias hardening should be driven by scenes whose generated deterministic keywords remain narrow rather than by every scene equally.
- Host/runtime-heavy archetypes still carry `runtimeOnlyResidual` even where generator-level hardening is also indicated.

## Highest-Reuse Route Clusters

- resolver_request_mapping_hardening: 102
- runtime_url_classification_hardening: 102
- parameter_default_semantics_recovery_hardening: 89
- alias_generation_hardening: 84
- embedded_dictionary_extraction_hardening: 102

## High-Risk Examples

- sweep-002-scene 95598�?2398及配网设备监控情况周统计: gaps="invocation_alias_gap, dictionary_recovery_gap, parameter_default_semantics_gap, resolver_to_request_mapping_gap, runtime_url_semantics_gap" routes="alias_generation_hardening, embedded_dictionary_extraction_hardening, parameter_default_semantics_recovery_hardening, resolver_request_mapping_hardening, runtime_url_classification_hardening"
- sweep-003-scene 95598业务处理满意率统计日�?: gaps="invocation_alias_gap, dictionary_recovery_gap, parameter_default_semantics_gap, resolver_to_request_mapping_gap, runtime_url_semantics_gap" routes="alias_generation_hardening, embedded_dictionary_extraction_hardening, parameter_default_semantics_recovery_hardening, resolver_request_mapping_hardening, runtime_url_classification_hardening"
- sweep-004-scene 95598供电服务月报: gaps="invocation_alias_gap, dictionary_recovery_gap, parameter_default_semantics_gap, resolver_to_request_mapping_gap, runtime_url_semantics_gap" routes="alias_generation_hardening, embedded_dictionary_extraction_hardening, parameter_default_semantics_recovery_hardening, resolver_request_mapping_hardening, runtime_url_classification_hardening"
- sweep-005-scene 95598工单明细�?: gaps="invocation_alias_gap, dictionary_recovery_gap, parameter_default_semantics_gap, resolver_to_request_mapping_gap, runtime_url_semantics_gap" routes="alias_generation_hardening, embedded_dictionary_extraction_hardening, parameter_default_semantics_recovery_hardening, resolver_request_mapping_hardening, runtime_url_classification_hardening"
- sweep-006-scene 95598抢修回单分析报告: gaps="invocation_alias_gap, dictionary_recovery_gap, parameter_default_semantics_gap, resolver_to_request_mapping_gap, runtime_url_semantics_gap" routes="alias_generation_hardening, embedded_dictionary_extraction_hardening, parameter_default_semantics_recovery_hardening, resolver_request_mapping_hardening, runtime_url_classification_hardening"
- sweep-007-scene 95598报修工单日管�?: gaps="invocation_alias_gap, dictionary_recovery_gap, parameter_default_semantics_gap, resolver_to_request_mapping_gap, runtime_url_semantics_gap" routes="alias_generation_hardening, embedded_dictionary_extraction_hardening, parameter_default_semantics_recovery_hardening, resolver_request_mapping_hardening, runtime_url_classification_hardening, runtime_validation_followup"
- sweep-008-scene 95598服务风险清单: gaps="invocation_alias_gap, dictionary_recovery_gap, parameter_default_semantics_gap, resolver_to_request_mapping_gap, runtime_url_semantics_gap" routes="alias_generation_hardening, embedded_dictionary_extraction_hardening, parameter_default_semantics_recovery_hardening, resolver_request_mapping_hardening, runtime_url_classification_hardening"
- sweep-009-scene 95598重要服务事项报备统计�?: gaps="invocation_alias_gap, dictionary_recovery_gap, parameter_default_semantics_gap, resolver_to_request_mapping_gap, runtime_url_semantics_gap" routes="alias_generation_hardening, embedded_dictionary_extraction_hardening, parameter_default_semantics_recovery_hardening, resolver_request_mapping_hardening, runtime_url_classification_hardening, runtime_validation_followup"
- sweep-010-scene _代理购电、市场化用户电量分析: gaps="invocation_alias_gap, dictionary_recovery_gap, parameter_default_semantics_gap, resolver_to_request_mapping_gap, runtime_url_semantics_gap" routes="alias_generation_hardening, embedded_dictionary_extraction_hardening, parameter_default_semantics_recovery_hardening, resolver_request_mapping_hardening, runtime_url_classification_hardening, runtime_validation_followup"
- sweep-011-scene 下达项目数据汇总统�?: gaps="invocation_alias_gap, dictionary_recovery_gap, parameter_default_semantics_gap, resolver_to_request_mapping_gap, runtime_url_semantics_gap" routes="alias_generation_hardening, embedded_dictionary_extraction_hardening, parameter_default_semantics_recovery_hardening, resolver_request_mapping_hardening, runtime_url_classification_hardening"

## Next Step

- The next child stage should convert this ledger into bounded rule-hardening routes, prioritized by reusable coverage rather than by scene-by-scene debugging order.
- The immediate downstream artifact should be a route-design / route-sequencing plan driven by this ledger.